Hreflang
Language Switchers, Geo Redirects and What Googlebot Sees
Google advises against redirecting visitors by guessed language or IP address. Gambling licenses sometimes require exactly that. The answer is to separate what the law restricts from what search engines need to read.
In brief
- Google says to avoid redirecting users based on what you think their language is, and not to use IP analysis to adapt content.
- Googlebot usually crawls from the USA without an Accept-Language header.
- Spain's gambling law requires licensed operators to redirect connections from Spain to their .es site, so some redirects are legal duties.
- Google's spam policies define cloaking as showing users and search engines different content with the intent to manipulate rankings and mislead users. Avoid even the appearance of it: restrict functions, not the information.
Most multilingual sites can follow Google's advice to the letter: show a language selector, link every version to every other, and never force a redirect. Licensed gambling sites cannot always do that, because licenses tie the offer to a territory. This guide sets out Google's position, the legal exceptions in the four markets we cover, and a structure that respects both.
What Google recommends
- Let users switch. Google suggests adding hyperlinks to the other language versions of a page so visitors can change language themselves.
- Avoid automatic redirects by language. Google's wording is to avoid redirecting based on what you think the user's language may be, because it can stop users and search engines from reaching every version.
- Do not adapt content by IP address. Google calls IP location analysis difficult and generally not reliable.
- Use x-default for the selector. Google says x-default was designed for language selector pages.
The reason behind all four is crawling. Google's guidance says Googlebot usually originates from the USA and sends requests without setting Accept-Language. A site that picks the version from the visitor's IP or browser language will show Googlebot one version, usually the US or default one, and Google may never see the rest.
Where the law requires a redirect or a block
Gambling regulation works by territory, and some rules require the site to act on where the visitor is:
- Spain. Ley 13/2011, art. 10.4, requires licensed operators to run a dedicated website under .es and to redirect to it all connections made from Spanish territory or using Spanish user accounts. That is a legal geo redirect.
- Great Britain. A Gambling Commission license is needed to provide remote gambling facilities to consumers in Great Britain. An operator without one has to keep its gambling offer away from British consumers.
- Germany. Only operators on the GGL whitelist may offer the licensed products, and players face cross-operator deposit limits. Unlicensed offers must not reach German players.
- Canada. Each province sets its own rules; Ontario's market is open to operators registered with the AGCO and under agreement with iGaming Ontario, while other provinces rely on their lottery corporations.
Where a rule like these applies, it comes first. The task is to meet it in a way that leaves search engines able to read the pages they are allowed to read.
A structure that serves both
- Split information from function. Editorial and information pages (rules, help, responsible gambling, the brand's license details) can usually be read from anywhere. Registration, deposits and play are the functions a license restricts. Apply geo controls to the functions, and confirm with counsel which pages your license allows to be viewed from outside the market.
- Give each market its own URL. A separate URL per locale, linked by hreflang, lets Googlebot reach each version directly. Never serve different languages on one URL by IP or browser setting.
- Use a banner, not a forced redirect, where the law allows a choice. If a visitor from Canada lands on the GB page, a banner that offers the Canadian version keeps the page reachable for everyone, including crawlers.
- Where a redirect is mandatory, make it exact and documented. Spain is the clear case: redirect Spanish connections to the matching page on the .es site, page to page, not to the .es home page. Point the
es-ESalternate at the .es page so the annotation and the redirect agree. - Treat Googlebot like any US visitor. Do not create a special path for crawlers. Google's spam policies define cloaking as presenting different content to users and search engines with the intent to manipulate search rankings and mislead users. If US visitors see an information page with the gambling functions disabled, Googlebot should see the same.
- Keep the selector crawlable. Use plain links in the HTML, not a form or a script-only menu, and give each option the language's own name ("Deutsch", "Español", "Français").
Legal note. Whether an information page may be shown to visitors outside the licensed territory depends on the license and the regulator's view of marketing. This guide describes search-engine behavior; it is not legal advice. Get the license position confirmed before you change any geo rule.
Designing the selector
- Label languages in their own language and countries in the visitor's language. Flags stand for countries, not languages, so avoid using a single flag for "English" or "Spanish".
- Remember the choice with a first-party cookie only if your privacy notice and consent setup cover it, and never use it to block crawlers.
- Link the selector to the equivalent page in each language, not to each language's home page, so the switch keeps the visitor in context.
- Show only the markets where the brand is licensed. A selector option is a promise that the version is meant for that country.
Questions
Is a geo redirect ever acceptable for SEO?
Google recommends against redirecting by guessed language or IP address, but a legal duty such as Spain's .es redirect rule takes priority. Make the redirect page to page, keep each version on its own URL and keep the annotations consistent with it.
Can I let Googlebot past a geo block?
Do not treat Googlebot differently from users. Google's spam policies define cloaking as presenting different content to users and search engines with the intent to manipulate search rankings and mislead users. Restrict the gambling functions for everyone outside the market and keep the information pages the same for all visitors.
Should the language selector use flags?
Flags represent countries. Use them for country choices if you like, but label languages with their own names, because one language is spoken in several of the markets you may serve.
Sources
- Google Search Central, Managing multi-regional and multilingual sites, last updated December 10, 2025.
- Google Search Central, Tell Google about localized versions of your page, last updated September 21, 2026.
- Google Search Central, Spam policies for Google web search (cloaking).
- BOE, Ley 13/2011, de regulación del juego (consolidated text), art. 10.4.d and 10.4.e.
- Gambling Commission, Remote sector guidance, no date shown.
- GGL, FAQ Einzahlungslimit und Höchsteinsatz, updated August 25, 2026.
- AGCO, One-year anniversary of Ontario's internet gaming market, April 4, 2023.
Spotted an error? Tell the editors and include a link to the source. Corrections are noted on the page they change (corrections policy).