Hreflang vs IP redirection: why forcing a user's location can hurt global indexation

What are hreflang and IP redirection, and how do they differ?

Hreflang is a markup system that labels each version of a page with its language and, optionally, its region. IP redirection is a server behavior that looks at a visitor's network address, estimates their location and sends them to a country version automatically. One informs, and the other forces.

How does hreflang work?

Each version of a page lists all its alternates, with codes such as en-us, en-gb or de, and each alternate links back to the others. Google reads these annotations and, when a searcher's language and location match, shows the appropriate version in results. The versions stay reachable by anyone, through any link.

Where can you place hreflang?

You can add hreflang annotations in the HTML head, in HTTP headers for non-HTML files or in an XML sitemap. Choose one method and apply it consistently, because mixing methods without discipline invites conflicts.

How does IP redirection work?

The server checks the requester's IP address against a location database and, if it decides that the visitor belongs to another country version, responds with a redirect to that version. Some implementations also look at the browser's language setting. The visitor lands on a page they did not request.

Why do businesses use it?

It seems helpful: shoppers arrive on a version with the right currency, delivery information and language without any effort. It can also be used to meet legal or commercial restrictions in certain regions. The intention is good, but the side effects can be serious.

What is the core difference for SEO?

Hreflang leaves every version accessible and lets search engines choose. IP redirection removes that accessibility for any client that the server routes elsewhere, including crawlers. For search, accessibility of every version is the more important property, which is why the two approaches lead to very different risks.

How does Googlebot crawl international sites?

Google's documentation explains that Googlebot crawls mostly from IP addresses in the United States, and that its requests usually do not include an Accept-Language header. A site that serves different content depending on location or language settings may therefore show Googlebot only one version.

What is locale-adaptive content?

Locale-adaptive pages change what they show depending on the visitor's apparent country or language, at the same URL. Google's guidance warns that Googlebot may not see all versions of such pages, because its requests come from limited locations and do not carry typical language preferences. Pages at separate URLs for each locale avoid this problem.

Why is a separate URL per version safer?

Each version can be requested directly, linked, indexed and annotated with hreflang. Nothing depends on the crawler's location, so all versions are visible to every system.

What happens if all US traffic is redirected?

Imagine that visitors from the United States are redirected from the global home page to a US version. Googlebot, arriving from a US address, is redirected too, and never sees the pages that are meant for other countries unless it finds them through other links. Even with hreflang present, the crawler may follow a redirect before reading it on the original page.

What if the redirect only applies on the home page?

Deep pages may still be crawled, but the home page is the main hub for discovery, so redirect problems there can reduce the crawl and the link flow to other versions.

Does Googlebot use other locations?

Google has said that it may also crawl with other locale settings in some cases, but it does not guarantee this, and you cannot depend on it. Design the site so that all versions are reachable by ordinary links and do not depend on a crawler's location.

What are the indexation risks of forced IP redirects?

Forced redirects can cause missing versions in the index, wrong versions in results, confused signals and poor experiences for real visitors. The risks appear in several forms, and the table summarizes the main ones.

Why is the "hidden version" risk so serious?

A version that crawlers cannot reach cannot rank, whatever its quality. If the German version of a store is only reachable after an IP check that sends crawlers elsewhere, it will not appear for German searches. The investment in translation and localization yields nothing.

How would you notice?

You would see a version missing from the index in Search Console, impressions from the wrong countries and URL Inspection results that show a different page from the one you expected.

Why does the wrong version appear in results?

If Google indexes only the version it saw, it may show that version to searchers everywhere. A shopper in the United Kingdom might see the US page, with the wrong currency and delivery terms, and bounce. Hreflang is meant to prevent this, but it only works when the alternates are crawlable.

What about caches?

Content delivery networks and proxies may cache the first response they see. If that response was a redirect for one country, later visitors from other countries may receive it too, unless the cache varies correctly by location, which is complex to configure.

What do real visitors lose?

People who travel, expats, cross-border shoppers and those using privacy tools may be forced to a version that does not match their needs. They may find it impossible to buy in their own currency or to read in their own language, and some will leave.

What does Google recommend instead of forced redirects?

Google recommends giving each locale its own URL, annotating the versions with hreflang, and letting users choose, with a notice that suggests the version that appears best. The suggestion can use location or language, but it should not prevent access to the rest of the site.

How should the suggestion work?

Show a banner or a modal that says, in the visitor's likely language, that a version for their country exists and offer a link to it, with a clear option to stay. Do not redirect automatically. Remember the choice with a cookie, so returning visitors are not asked again.

What should the banner say?

Keep it short and friendly, such as "It looks like you are in the United Kingdom. View our UK store?" with two buttons. Make the text accessible and the dismiss option easy to find.

What if you need to restrict content for legal reasons?

If you must block access in certain regions, use an appropriate response and keep the rest of the site reachable. Take legal advice on the exact method, and consult Google's documentation on blocking content. Do not confuse legal restriction with a convenience redirect, because they have different consequences.

What about pricing and currency?

You can adjust prices and currency according to the selected market, with an explicit selector, while leaving every market's pages reachable by URL. Make sure that the content in structured data matches what shoppers see in each market.

How does this connect to site structure?

Your choice of subfolders, subdomains or country domains shapes how versions are addressed. Our guide to Shopify international structure compares the options, and the same principles apply on other platforms.

What rules must hreflang annotations follow?

Hreflang must be reciprocal, use valid language and region codes, point to canonical, indexable pages that return a 200 status and include a self-reference. Errors in any of these cause Google to ignore the annotations.

What does reciprocity mean?

If page A lists page B as an alternate, page B must list page A. Without return links, Google may treat the annotation as unreliable. A complete cluster has every page listing every other page in the set, including itself.

How do you check reciprocity at scale?

Use a crawler that validates hreflang, or a script that reads the annotations from all versions and checks for missing returns. Fix mismatches by generating annotations from a single source of truth.

Which codes are valid?

Language codes use the ISO 639-1 standard, such as en, fr or de, and optional region codes use ISO 3166-1 alpha-2, such as US, GB or CA. A region alone is not valid, and some commonly seen mistakes include using uk for the United Kingdom instead of gb, or using unsupported combinations.

What is x-default?

The x-default value marks the page that should be used when no version matches the visitor's language or region, such as a global selector page or the main language version. It is optional but useful.

Which pages should hreflang point to?

Canonical URLs that are indexable and return a 200 status. Alternates that redirect, return errors or carry noindex break the cluster. Each page should also have a self-referencing canonical, so the signals agree.

What if some versions do not exist?

List only the versions that exist for that page. If a product is sold only in some markets, its annotations should reflect that.

Is hreflang a ranking factor?

Google has said that it is not. Hreflang helps Google choose the most appropriate version among equivalent pages, so the right one is shown to the right audience, but it does not boost a page's ranking.

How should hreflang and a suggestion banner work together?

Use hreflang to guide search engines and a banner to guide people. Hreflang sends searchers to the right version from the results page, and the banner helps visitors who arrive on a different version by following a link, an advertisement or a direct address.

What is the best user flow?

A searcher in Germany sees the German page in results, thanks to hreflang, and lands on it directly. A visitor from Germany who lands on the US page through a shared link sees a banner offering the German version, and can switch with one click. The choice is remembered. At no point is anyone forced.

How do you handle returning visitors?

Store the chosen country or language in a cookie or local storage, respecting privacy rules, and use it to preselect the right market on later visits, without redirecting away from a requested URL.

How do you keep the banner from harming performance?

Load it without blocking the main content, reserve space or overlay it so that it does not shift the layout and keep its script small. A banner that causes layout shift or delays the main content harms Core Web Vitals, which we cover in our Core Web Vitals guide.

Should the banner be indexed?

The banner text is part of the page, and it should not dominate the content. Keep it short, and make sure that the page's main content, not the banner, is what search engines read first.

What about interstitials?

Google has guidance on intrusive interstitials that block content on mobile, and a full-screen country prompt can fall into that category. Use a compact banner, not a full-page overlay.

How do common platforms support this approach?

Many platforms offer market features that generate hreflang and a country selector. Check what yours does by default, and configure it to suggest, not force.

What about Shopify Markets?

Shopify's international features can output hreflang tags for configured markets and languages and offer geolocation tools that suggest a market to visitors. Configure the suggestion behavior, test the output on real URLs and confirm that no app adds automatic redirects of its own. Our guide to Shopify meta tags shows where hreflang is printed in the head.

What should Shopify merchants check?

Verify the hreflang cluster on sample pages in each market, make sure country selectors are real links and test that a request from a different location is not redirected away from the requested URL.

What about WooCommerce, Magento and others?

Multilingual and multi-currency plugins differ widely. Some redirect by default and others do not. Read the settings carefully, turn off automatic redirects if they exist and test with a VPN and different browser language settings.

What about content delivery networks and edge rules?

Edge rules that redirect by country are easy to add and easy to forget. Review the configuration of your CDN and any web application firewall, because they can create IP-based redirects outside the platform.

How do you test for IP redirect problems?

Test by requesting pages from different locations and language settings and by checking what Googlebot sees. A set of simple tests reveals most problems.

Which manual tests help?

Use a VPN to browse from several countries, change the browser's preferred language and request the same URL each time. Note whether you are redirected or whether the page stays put. Repeat for the home page, a category page and a product page.

What does a good result look like?

The requested URL stays the same, the page loads, and at most a banner suggests another version. Any automatic redirect that moves you away from a URL you asked for is a warning sign.

How do you check what Googlebot sees?

Use the URL Inspection tool's live test in Google Search Console for each version and compare the rendered page with what you expect. If the tested page differs from the requested version, something is changing the response for Google's location.

What about server logs?

Logs show the responses given to Googlebot. A large share of 301 or 302 responses on international URLs suggests redirect rules at work. Our guide to log file analysis shows how to verify Googlebot and group the results.

How do you test hreflang itself?

Use a crawler with hreflang validation, review the international reports and indexing status in Search Console and sample pages in each market. Look for missing return links, invalid codes and alternates that are not indexable.

How do sitemaps and canonicals fit with hreflang?

Canonical tags, sitemaps and hreflang must tell one consistent story. Each version is its own canonical, each version appears in the sitemap and the hreflang cluster links them together. Conflicts between the three are a leading reason that international setups fail.

Should each version have a self-referencing canonical?

Yes. A page in the German version should canonicalize to itself, not to the English page, because a canonical to another language version tells Google to treat the German page as a duplicate and drop it. Hreflang is the correct way to relate the versions, and the canonical is how each version identifies itself.

What if two regional versions are almost identical?

If the US and Canadian pages are nearly identical, Google may fold them together despite hreflang. Differences in currency, spelling, availability and delivery information help justify the separation. If there is no real difference, consider whether a single version would serve better.

How should sitemaps present international URLs?

You can list hreflang alternates inside the XML sitemap, which is convenient for large sites, because it keeps the annotations out of the HTML. Each URL entry lists all its alternates, including itself. Keep the sitemap in step with the pages, listing only canonical, indexable URLs.

What are the trade-offs between methods?

HTML tags are easy to inspect on each page but add weight to every response. Sitemaps keep pages lighter and are easier to generate in bulk, but they are harder to check by eye. HTTP headers suit non-HTML files. Choose one method and use it consistently.

How do you keep annotations accurate as the catalog changes?

Generate them from the same data that creates the pages, so that when a product is added to or removed from a market, the annotations change at the same time. Manual maintenance does not scale and creates mismatches.

How should you handle currency, language and availability without redirects?

You can serve the right commercial details by letting visitors select a market and remembering the choice, while keeping each market's pages at their own URL. This gives people a tailored experience without hiding any version from search engines.

How do you handle currency?

Offer a clear currency and country selector, apply the selection to prices throughout the session and show the currency code on product pages. If you convert prices automatically from a base currency, explain how and when rates are applied. Make sure that structured data reflects the price in the selected market.

What about shoppers who select a different currency from their location?

Let them. A traveler or a gift buyer may want a different currency from the one their location suggests. A suggestion, not a rule, respects that.

How do you handle language?

Offer languages as links on the page, not just as a drop-down that depends on script. Each language should have its own URL, translated content and hreflang annotations. Avoid choosing the language only from the browser's setting, because crawlers do not send one.

What if a page is not translated?

Either translate it, hide the link in that language or show the original language clearly and keep it out of the translated cluster. Half-translated pages confuse both visitors and search engines.

How do you handle availability and shipping?

Show delivery information for the selected market, and make clear if a product cannot be shipped there. If a product is unavailable in a market, avoid promoting it there, and do not list it in that market's sitemap.

How do you make restrictions clear?

Use plain messages such as "This item is not available in your country" with links to alternatives, so that shoppers are helped, not blocked without explanation.

How do you monitor international indexation over time?

Monitor indexing and performance for each version, with a Search Console property or filter per market, and watch for versions that disappear or for traffic arriving from unexpected countries. International setups break easily during releases.

Which reports matter most?

The Pages report for each version shows how many URLs are indexed and why others are not. The Performance report, filtered by country and page, shows whether each version is reaching its audience. Together they reveal both indexing gaps and targeting problems.

How often should you check?

Monthly for stable setups, weekly in the weeks after a launch or a platform change, and always after a release that touches templates, redirects or the CDN configuration.

What alerts are useful?

Set alerts for a drop in indexed pages for any version, a rise in redirect responses to Googlebot and a sudden change in the share of traffic by country. These are early signs that a rule has changed.

How do you document the setup?

Keep a record of the URL structure, hreflang method, banner behavior and any edge rules that touch international traffic. It helps teams avoid accidentally reintroducing forced redirects.

What does fixing an IP redirect problem look like in practice?

The following example is fictional and illustrates the method. Its outcomes are invented for demonstration and are not benchmarks.

What was the situation?

A fictional cookware brand sells in the United States, the United Kingdom and Germany from three subfolders. A rule at the CDN redirects every request to the version that matches the visitor's country. Search Console shows the UK and German versions with very few indexed pages, and impressions for UK queries land on the US pages.

What did the investigation find?

URL Inspection tests for the UK pages show that Google was redirected to the US version. Logs show that almost all Googlebot requests to /en-gb/ receive a 302 to the US home page. The hreflang annotations in the HTML are correct, but crawlers rarely read them because they never reach the pages.

What did the team change?

They removed the country-based redirect rule, kept every version reachable by its own URL, added a compact banner that suggests the local market and remembers the choice, and made the country selector a set of real links. They kept the hreflang annotations and validated them with a crawler.

How did they measure the result?

Over several weeks, the Pages report showed the UK and German versions being crawled and indexed, impressions for UK and German queries moved to the matching versions and the share of visitors landing on the wrong market fell. The team noted that rankings still depended on content and competition, and that the fix removed a barrier and did not guarantee growth.

What are the common mistakes with hreflang and redirects?

The common mistakes are forcing redirects by location, serving different content at one URL, leaving hreflang annotations non-reciprocal, using invalid codes and pointing alternates to redirected or noindexed pages. Each can hide or confuse versions.

Which mistakes hide content?

IP-based redirects, content that changes by location at the same address, blocking crawlers from some versions and alternates that return errors all prevent versions from being crawled or indexed.

Which mistakes confuse signals?

Missing return links, canonicals that point to a different version, mixed hreflang methods and inconsistent codes cause Google to ignore or misread the annotations.

How do you avoid them?

Give every locale its own URL, generate hreflang from one source, validate regularly and use a suggestion banner instead of redirects.

What checklist should you follow when launching or fixing international versions?

Use a repeatable checklist for every market launch and every fix. A short list catches the most expensive mistakes before they reach search engines or customers.

Which structure and crawl items should it include?

Each locale has its own URL, reachable by an ordinary link from the selector and the sitemap. No rule redirects visitors or crawlers automatically by location or language. Robots.txt does not block any version. The CDN and firewall have no country-based redirect rules.

Which annotation items should it include?

Hreflang annotations are present in one chosen method, reciprocal, self-referencing, valid in code format and pointing to canonical, indexable pages with a 200 status. Each version has a self-referencing canonical. The x-default value is set where appropriate. Sitemaps list the right URLs.

Who verifies it?

A technical SEO reviews the markup and crawl results, a developer confirms the server and CDN rules and a native speaker or regional manager checks the content and commercial details for each market.

How does AH SEO Agency help with international indexation?

We review your URL structure, redirect rules, hreflang and banner behavior, test from several locations and in the URL Inspection tool and give your developers clear changes. We then monitor indexing and performance for each market after the fix.

Where can you learn more?

See our international SEO service, read the subfolders versus subdomains guide or request a free SEO audit.

Summary: should you use hreflang or IP redirection?

Use hreflang with separate URLs for each locale, and suggest the right version with a banner instead of redirecting by IP address. This keeps every version crawlable and lets visitors choose.

• Hreflang labels equivalent pages, and it is not a ranking factor.
• Googlebot mostly crawls from US addresses and without language preferences, so forced redirects can hide versions.
• Every locale needs its own URL and a reciprocal, valid hreflang cluster.
• Suggest, never force, and remember the visitor's choice.
• Test with a VPN, language settings, URL Inspection and logs, and monitor each market.