When you generate a UULE for a local SERP check, you're picking a granularity — city, ZIP code, or neighborhood — and that choice changes the data you get back. Each level surfaces different signals, exposes different competitive realities, and answers different strategic questions. Teams that default to one level for every audit miss what the other two would have shown them. Teams that switch granularities thoughtfully across a single audit see a richer picture in less time.
You can view localized search results for any market with our free tool — no API keys, no scraping, no sign-up.
This article breaks down the three primary UULE granularities used in local SEO testing, when to use each, and what each one reveals that the others miss. The framing comes from running multi-granularity audits across service-area businesses, multi-location brands, and franchise systems where the right granularity often makes the difference between insight and noise.
The Three Granularities at a Glance
A quick reference:
- City-level UULE. Encodes "City, Region, Country" — for example, "Houston, Texas, United States." Useful for portfolio-wide visibility, brand-level monitoring, and cross-market comparison.
- Neighborhood-level UULE. Encodes "Neighborhood, City, Region, Country" — for example, "Park Slope, Brooklyn, New York, United States." Useful for hyperlocal competition analysis, service-area mapping, and capturing proximity-driven Map Pack variance.
- ZIP-code-level UULE. Encodes the postcode plus city/region/country — for example, "77002, Houston, Texas, United States." Useful for territory analysis, service-area definition validation, and aligning audits to data Google itself uses internally for some signals.
Each level has its own strengths and trade-offs. Skilled local SEO teams use all three deliberately.
City-Level UULE: Best for Portfolio and Brand Views
City-level UULE produces a SERP that represents the broadest "average" customer for a market. It's the right tool when:
- You're auditing a multi-market brand and need a comparable view across many cities.
- You're tracking branded-query SERPs where neighborhood-level variance is minimal.
- You're building a fast monthly portfolio scan and need consistent baselines.
- You're presenting to executives who think in cities, not ZIP codes.
City-level audits also surface market-level competitive realities cleanly: who's winning the pack as you'd see it from the city center, what directories dominate, and what SERP features are typical for the metro.
Limitations. A city-level UULE returns one snapshot of a SERP that varies block by block. For a 200-square-mile metro, the city-centroid SERP is one of thousands of possible local pages. Decisions made purely from city-level checks miss the service-area variance that often matters more.
When to use it as your only level. Almost never alone for service-area businesses. Often sufficient for branded-query monitoring or for cross-market comparisons where consistency matters more than precision.
Neighborhood-Level UULE: Best for Hyperlocal Competition
Neighborhood-level UULE answers questions city-level can't:
- How does the Map Pack change across our service area? A neighborhood-by-neighborhood audit reveals proximity-driven variance directly.
- Which competitors dominate which sub-markets? Neighborhood UULEs expose competitors that don't show up at the city centroid but win specific corridors.
- Where are our coverage gaps? Neighborhoods where the brand drops out of visibility entirely are immediate optimization targets.
For service-area businesses — plumbers, HVAC contractors, dental practices serving multiple neighborhoods, restaurants drawing from a defined catchment — neighborhood-level UULE is the default granularity. It matches how customers actually experience the SERP and reveals the small-scale variance that drives most local SEO decisions.
Limitations. Neighborhood naming isn't always consistent. "SoMa" in San Francisco and "Mission Bay" overlap; "Downtown" exists in nearly every city and resolves differently depending on context. Geocoders sometimes return neighborhood names you've never heard of or fail to recognize names you'd expect. Validation matters more at this level than at city level.
When to use it. Default for any service-area business. Always include three to five neighborhoods spanning the realistic service radius — center, two adjacent neighborhoods, and one or two outer-edge areas.
ZIP-Code-Level UULE: Best for Territory and Data Alignment
ZIP codes occupy a special place in U.S. local SEO. They're administrative units with stable boundaries, they show up in many third-party datasets (Census, commercial demographics, customer CRM data), and Google often uses ZIP codes internally for various local signals. ZIP-level UULE produces SERPs that align cleanly with that data structure.
ZIP-level UULE is the right tool when:
- You're validating service-area definitions. GBP service areas can be defined by ZIP. Auditing the SERP from each ZIP in the service area confirms whether the business is visible where it's promising to serve.
- You're correlating SERP performance with demographic or revenue data. ZIP-level revenue data plus ZIP-level rank data is a clean join.
- You're working with a CRM that segments customers by ZIP. Audits aligned to those ZIPs feed directly into reporting.
- You're testing across a regular grid. ZIPs aren't perfectly regular, but they're more regular than neighborhoods.
ZIP-level UULE in canonical form usually looks like "ZIP, City, Region, Country" — for example, "10001, New York, New York, United States." Some teams use just "ZIP, Country" — "10001, United States" — which can work but loses disambiguation when ZIPs are similar across regions. The verbose form is more reliable.
Limitations. ZIPs vary wildly in size. Urban ZIPs may cover a few city blocks; rural ZIPs cover hundreds of square miles. A "ZIP-level audit" in Wyoming is much coarser than the same in Manhattan. The granularity is real but uneven.
When to use it. Whenever your reporting framework, service area, or analytics setup is organized around ZIPs. Also useful for U.S. franchise systems where territories are commonly defined by ZIP assignment.
Mapping Granularities to Common Questions
A short reference table from how we use each in client work:
- "How are we doing in Phoenix overall?" → City-level UULE for Phoenix. Then drill into neighborhood if the answer is concerning.
- "Why are we losing pack visibility in our southern service area?" → Neighborhood-level UULEs across southern neighborhoods. Identify the specific places where ranking drops.
- "Does our GBP service area still match our actual coverage?" → ZIP-level UULEs for each ZIP in the service area. Spot any ZIP where visibility has collapsed.
- "Where should we open the next location?" → Combination: city-level for the market overview, neighborhood-level for competitive density, ZIP-level for demographic and revenue alignment.
- "Are we showing up in customer-rich corridors?" → Neighborhood-level on the named corridors, validated against ZIP-level when corridor names are ambiguous.
The pattern: city-level for portfolio context, neighborhood-level for hyperlocal competitive reads, ZIP-level for territory and data alignment.
A Multi-Granularity Audit Pattern
For an important market, a single audit cycle benefits from all three granularities:
- One city-level check for the market-wide baseline. Establishes who's winning the pack from the city centroid and what SERP features dominate.
- Five to eight neighborhood-level checks across the realistic service area. Reveals proximity-driven variance, hyperlocal competitors, and coverage gaps.
- Three to five ZIP-level checks for ZIPs where the business has explicit service-area commitments or where commercial value concentrates. Validates the territory-level read.
That's roughly 10 to 15 UULE generations per market. With a well-built local SERP checker, that's 30 to 45 minutes of structured work — short enough to repeat monthly, deep enough to inform real strategy.
Pitfalls Specific to Each Granularity
A few errors to avoid by level:
City-level pitfalls: - Drawing service-area conclusions from a single city-centroid SERP. The centroid is one point; the service area is many. - Assuming the city-level pack is representative when the actual competitive picture varies block by block.
Neighborhood-level pitfalls: - Trusting neighborhood names without validating with the geocoder. "Downtown" resolves to different geographies in different cities. - Cherry-picking favorable neighborhoods. If only the wealthiest, closest-to-the-office neighborhoods get audited, the picture looks great and the business misses real coverage problems.
ZIP-level pitfalls: - Equating ZIPs across geographies. A ZIP in Manhattan represents a different scale of customer base than a ZIP in rural Texas. - Using only the ZIP in the canonical name without the city or country, which can cause Google to default to a less precise interpretation.
How Google Treats Each Granularity
A useful intuition: Google's local search uses location as a continuous signal, not a discrete one. The Map Pack uses precise coordinates and proximity scoring; the "intended" UULE granularity is whatever produces a clean canonical name. From Google's perspective, a city-level UULE and a neighborhood-level UULE both resolve to a point on the map (or a small region), and the SERP that loads is calibrated to that point.
This means the granularity you choose doesn't fundamentally change Google's algorithm — it changes where on the map you're asking Google to render the SERP from. City-level asks from the city's geometric center; neighborhood-level asks from a more specific point within that city; ZIP-level asks from somewhere within the ZIP's footprint. All three are valid; each one shows you a different vantage point.
When to Switch Between Granularities Mid-Audit
In practice, you'll often switch granularities while investigating a single question:
- Start city-level. Get the market baseline.
- Notice anomaly. A specific corridor seems weaker than the city-level pack suggests it should be.
- Switch to neighborhood-level. Run three to five neighborhood checks across the corridor.
- Confirm with ZIP-level. Validate the neighborhood read with a ZIP-level check in the corridor's center ZIP.
That cascade — broad to narrow — turns a city-level anomaly into a diagnosed and located problem in under an hour. It also produces a coherent story you can take to a client: "City-level pack looked strong overall, but here are three neighborhoods where the brand isn't visible, confirmed by ZIP-level checks. Our recommendation is to expand the GBP service area and add a neighborhood-specific page for the corridor."
Mapping the Three Granularities to Reporting
Each granularity also pairs cleanly with a different reporting layer. City-level data fits well at the top of an executive summary — a map of cities colored by visibility, one row per market. Neighborhood-level data fits the operational layer of a report — what's happening inside each market, where the gaps are, what to do next. ZIP-level data fits territory-management views — service-area validation, sales-territory alignment, and CRM-integrated dashboards. When the granularity of the data matches the granularity of the audience, the report lands.
Choosing Granularity by Vertical
Different verticals favor different default granularities. Restaurants, salons, and retail — businesses customers travel short dista