How to check Google search results by location with UULE

Local rankings change by city — sometimes by neighborhood. If you only check Google from your desk, you miss what a customer across town sees. A Google UULE generator encodes a location into a search URL so you can spot-check local SERPs without hopping on a plane. This is a research habit, not a GPS spoof: you are asking Google to treat a query more like a search from a named place.

What a Google UULE parameter does

UULE is a Google Search parameter that carries a geographic hint. The common SEO format encodes a canonical place name (from Google’s geotarget-style naming) into a string that starts with w+CAIQICI. Append it as &uule=… and Google treats the query more like a search from that place.

The encoding is not mysterious once you see it in parts: a fixed prefix, a length token, then a base64 form of the place name. GenShelf’s free Google UULE generator builds that string in your browser and can also decode a w+CAIQICI… value back to the name. If decode fails, you probably pasted a coordinate-style UULE or a truncated copy — not a canonical-name value.

A worked example: the same keyword, two cities

Suppose you write local pages for a plumber. You search emergency plumber from a laptop in downtown Chicago and see a map pack full of Loop and Near North shops. That is not what someone in Naperville sees. Encode Chicago,Illinois,United States and Naperville,Illinois,United States as two UULEs, keep the keyword identical, and open both URLs in private windows.

Compare three things, not just the #1 blue link:

• Map pack: which businesses appear, in what order, and whether your GBP listing is in the three-pack at all.
• Local organic: city landing pages vs directory sites vs your homepage.
• Intent mix: ads, “near me” refinements, and People Also Ask — those shift with location even when the typed query does not.

If Chicago shows you and Naperville does not, the fix is rarely “add UULE to the site.” UULE is a diagnostic. The page and the Google Business Profile still have to earn the local pack in that city.

A clean local SERP checklist

1. Generate a UULE for the city you care about with the free Google UULE generator.
2. Pair it with gl (country) and hl (language) and the right Google domain when possible. A UK query on google.com with gl=us is a messy experiment.
3. Open the URL in a private/incognito window, signed out, with location sharing off for the browser if you can. Logged-in personalization still leaks through sometimes.
4. Compare map pack, organic positions, and local pack businesses — not just the #1 blue link. Screenshot both SERPs so you are not relying on memory.
5. Repeat for a second nearby city or a suburb. One location is an anecdote; two locations show whether the gap is real.

Canonical names matter

Prefer geotarget-style names such as Chicago,Illinois,United States over casual labels like “Chi-town.” Wrong names can produce a UULE that encodes, but does not match the location you intended. City presets on the generator use common canonical forms.

Practical naming habits that save reruns:

• Use the full administrative name Google expects (England,United Kingdom, not just “UK” jammed onto a city).
• Do not mix neighborhood nicknames into the canonical string. If you need a finer grid, that is a different UULE family (coordinates), not a creative city label.
• Decode after you encode. If the recovered name is not what you typed, stop and fix the input before you trust the SERP.

gl, hl, and the Google domain

UULE is one lever. Country and language are others. A useful default for US English research is google.com + gl=us + hl=en + a US city UULE. For Manila research, prefer google.com.ph with a Philippines canonical name rather than forcing everything through google.com. The generator’s URL builder exists so you do not hand-edit query strings and drop a parameter.

When results look “off,” change one variable at a time. If you swap city, domain, and language in one click, you will not know which change moved the map pack.

Limits to keep in mind

• UULE is a strong signal, not a perfect GPS spoof. Personalization, device, and login state can still shift results.
• Coordinate-based UULE values (different prefix/encoding) are used for finer grids; this workflow focuses on city-level canonical names.
• Mobile SERPs and desktop SERPs differ. A laptop incognito check will not perfectly match a phone in that city.
• Use checks for research and QA — not as a substitute for Search Console, rank trackers, or real local customer feedback.

Rank trackers still earn their keep for history and many locations at once. UULE is for the moment you need to see the page a person in that city would see: ads, pack, sitelinks, and all.

What to do with the findings

If a suburb never shows your business, check NAP consistency, service area settings, and whether the landing page actually names that city in a way a human would recognize — not a footer list of 40 towns. If the pack shows you but organic does not, the GBP and the website are telling different stories. If ads crowd the top, note it; organic opportunity is still the rest of the page.

After you confirm what ranks locally, tighten page copy against length and clarity with the word counter and word count targets for SEO. Padding a thin city page to a word count will not fix a missing citation or a GBP in the wrong category — but it will show you when a draft is still a stub.