How gl and hl Influence Localized SERP Results

UULE gets most of the attention in local SEO conversations because it pinpoints location. But UULE rarely works alone. The two companion parameters — gl (country) and hl (host language) — shape the SERP just as much, sometimes more, depending on the query and the market. Understanding what each one does and how they interact with UULE is essential for any local SEO operator running international audits, bilingual market work, or even single-language U.S. work with non-English customer segments.

See it in practice with this free local SERP checker — it builds a UULE-encoded Google URL and opens the live results in a new tab.

This article unpacks gl and hl: what each controls, how they interact with UULE, where they affect rankings and SERP layout, and how to set them deliberately for accurate audits. The framing comes from running multi-locale localized SERP audits across U.S. English, U.S. Spanish, and several international markets.

What gl Controls

gl is the geographic location parameter. It accepts a two-letter ISO 3166-1 alpha-2 country code (us, gb, ca, de, fr, etc.) and tells Google's search backend which country the search originates from. The parameter influences several aspects of the response:

• Domain bias. Setting gl=fr biases results toward French domains; gl=de toward German. The bias isn't absolute — international authoritative sources still rank — but it shifts the mix.
• Currency and units. Some answer boxes (prices, conversions, weather) render in the country's expected currency and units.
• Local business eligibility. Businesses must generally have presence in the gl country to appear in the Local Pack. A U.S. business doesn't rank in a gl=gb SERP unless it has UK presence.
• Default location fallback. If UULE is absent or malformed, gl acts as the localization signal of last resort — Google defaults to a country-level interpretation.

gl is necessary for any cross-country audit. It's also necessary for single-country audits where the searcher's IP doesn't match the audit's target country — for example, an agency in India auditing a U.S. client's SERPs. Without gl=us, the SERP would skew Indian; with it, the SERP renders as a U.S. SERP.

What hl Controls

hl (host language) accepts a language code (en, es, fr, de, pt-BR, zh-CN, etc.) and tells Google what language to render the interface in and what language preferences to apply to results. The effects:

• Interface chrome. "All," "Maps," "News," and other UI labels render in the chosen language.
• Language preference in results. A search with hl=es pushes Spanish-language content higher in the organic listings, even when gl is set to a country that's primarily another language. A search with hl=en and gl=mx (Mexico) produces a SERP that's biased toward English content but still calibrated to Mexico.
• Snippet generation. Featured snippets and AI Overviews use the hl language for output text.
• NLP-driven features. PAA blocks, "Things to know," and other NLP-generated features render in the hl language.

hl matters even within a single-country audit if the target audience includes non-default-language speakers. A U.S. business serving Spanish-speaking customers in Los Angeles should audit with both hl=en (to see the English experience) and hl=es (to see the Spanish experience). The two SERPs will differ — sometimes significantly — and both reflect real customers.

How gl, hl, and UULE Interact

Think of the three parameters as forming a triangle of localization signals:

• gl sets the country context.
• hl sets the language context.
• uule sets the precise location context.

Google's edge synthesizes all three to render a SERP. When they're internally consistent — gl=de, hl=de, UULE pointing to "Berlin, Germany" — the result is a clean, predictable SERP. When they conflict — gl=us, hl=en, UULE pointing to "Berlin, Germany" — the result is a confused hybrid that doesn't represent any real searcher.

The rule: align all three to match the searcher you're trying to simulate.

A few alignment patterns:

• U.S. English searcher in Houston: gl=us, hl=en, UULE = "Houston, Texas, United States."
• U.S. Spanish searcher in Houston: gl=us, hl=es, UULE = "Houston, Texas, United States."
• Mexican Spanish searcher in Monterrey: gl=mx, hl=es, UULE = "Monterrey, Nuevo León, México."
• Quebec French searcher in Montréal: gl=ca, hl=fr-CA (or hl=fr), UULE = "Montréal, Québec, Canada."

The combinations multiply with international work. A standardized table of preferred (gl, hl) pairs for the markets your team works in saves time and prevents mistakes.

Where gl Shows Up in SERP Differences

When you flip gl while holding hl and UULE constant, observable changes include:

• Map Pack composition. Pack listings filter to businesses with presence in the new country.
• Domain mix in organic. Country-specific TLDs become more or less prominent.
• Currency in shopping results, prices, and answers.
• Knowledge Panel content. Some panels pull country-specific data.
• Local-news box selection. News sources skew toward the country's outlets.

For audits targeting a specific country, set gl to that country every time. Even when the auditor is physically in the same country, explicitly setting gl prevents IP-detection edge cases.

Where hl Shows Up in SERP Differences

Flipping hl while holding gl and UULE constant produces these changes:

• Interface labels. Filters, panels, and UI elements translate.
• Organic ranking shifts. Content in the chosen language ranks higher; content in other languages drops.
• Snippet text. Featured snippets and AI Overviews render in the new language.
• PAA blocks. Questions surface in the language of hl.
• Local justifications. GBP-attached labels like "Open now" or "Provides services" appear in the hl language.

The biggest practical implication: hl affects what content competes. A page in English may rank #1 with hl=en and drop to page two with hl=es, even if everything else is identical. For bilingual or multilingual markets, the language of the audit is a primary variable.

Common Mistakes With gl and hl

Three patterns show up in client audits regularly:

• Defaulting gl and hl based on the auditor's location. An agency in the U.S. auditing a UK client's SERP without setting gl=gb produces a U.S.-biased SERP. Always set explicitly.
• Mismatching gl and UULE country. gl=us with a UULE for a Canadian city produces a confused SERP. Always confirm country alignment.
• Ignoring hl entirely. Many audits leave hl defaulted, missing the experience of non-default-language customers entirely. For any market with significant multilingual demand, run audits in both relevant languages.

The fixes are mechanical — set both parameters deliberately, every time — but the discipline is what separates reliable audits from variable ones.

How to Test the Effect of Each Parameter

A useful exercise for any analyst new to local SEO: run the same query four times.

1. Baseline: gl=us, hl=en, UULE for a U.S. city.
2. Flip gl: gl=gb, hl=en, UULE for a UK city. Note how the pack and organic results shift.
3. Flip hl: gl=us, hl=es, UULE for a U.S. city with significant Spanish-speaking population (Miami, Los Angeles, San Antonio). Note how organic shifts and which content surfaces.
4. Flip both: gl=mx, hl=es, UULE for a Mexican city. Note the full international shift.

Walking through that exercise builds intuition for what each parameter does. Many analysts who've been doing local SEO for years still default settings without understanding the impact; this experiment makes the impact concrete.

Recommended Standard for Multilingual U.S. Local SEO

For U.S.-focused local SEO teams serving clients with bilingual customer bases, a standard worth adopting:

• Always set gl=us explicitly, even when auditing from inside the U.S.
• Always run audits in hl=en as the baseline.
• Add hl=es audits for any market with >15% Hispanic population (Census or commercial demographic data; cities like Miami, Los Angeles, San Antonio, Houston, Phoenix, McAllen).
• For Spanish-language audits, use Spanish-language queries — translating "plumber" to "plomero" returns a meaningfully different SERP than searching "plumber" with hl=es.
• Report English and Spanish SERP findings side by side when both apply.

That standard ensures the full customer experience is audited, not just the default-language slice.

International Audits: A Few Considerations

For agencies expanding into international local SEO, a few cross-border realities:

• Some hl codes are region-specific. hl=pt-BR (Brazilian Portuguese) and hl=pt-PT (European Portuguese) produce different SERPs. The same holds for hl=en-GB vs. hl=en-US and hl=es-MX vs. hl=es-ES. Pick the precise variant when it matters.
• Right-to-left languages. Arabic (hl=ar) and Hebrew (hl=he) render the SERP RTL. The data is the same; the layout is mirrored.
• CJK languages. Chinese (hl=zh-CN or hl=zh-TW), Japanese (hl=ja), and Korean (hl=ko) localize cleanly but may surface SERP features (Knowledge Panels, vertical-specific modules) you don't see in Latin-script markets. Document them so cross-market comparisons account for the difference.
• Country-specific Google domains. Some countries see Google redirect to google.de, google.co.uk, google.com.br, etc. URL construction works fine with google.com/search and the right gl, but a redirect to a local domain is normal and harmless.

Debugging When Results Don't Match Expectations

When a SERP audit returns unexpected results, work through the parameters in order:

1. Verify gl. Is it set explicitly? Does it match the country the audit is targeting?
2. Verify hl. Is it set to the language the targeted searcher would actually use?
3. Verify the UULE canonical name. Was it produced by a geocoder, or does it come from raw input?
4. Confirm internal consistency. Does the country in the canonical name match gl? Does the language in the canonical name (when relevant) match hl?
5. Re-encode and reload. Stale UULE is a common silent failure.
6. **Open in i