Why Does Google AI Overviews Show UK Pages to US Users Despite Hreflang?
Google AI Overviews most likely show UK pages to US users because the UK and US pages are near-duplicates. Google's documentation says localized versions of a page are only considered duplicates if the main content remains untranslated. English pages for the UK and US usually fit that description. Google then groups them and chooses one as the canonical version, and uses hreflang to swap in the right regional URL in ordinary search results. Google has not said that AI Overview citations make the same swap. So an overview may cite the version Google chose as canonical, which can be the UK one. The fix is to make the US page a clearly distinct, self-canonical page, with complete hreflang, US-specific content and no location-based redirects that confuse crawlers.
Why does hreflang work in organic results but not in AI Overviews?
Hreflang is a hint about alternate versions, not a rule. In organic results, Google uses it to show the version that matches the searcher's language and region, even when the pages are duplicates. AI Overviews are generated from retrieved content and link to the sources the system used. When the regional pages are near-identical, the system has little reason to prefer the US version and may cite whichever page it treats as the representative. Organic results then show the US URL while the overview links to the UK one.
What else can cause the wrong regional page to appear?
- Canonical tags pointing to the UK page, often set up years ago to consolidate duplicates.
- Missing return links. Google says each language version must list itself and all other versions. One-way hreflang is often ignored.
- Location-based redirects. Google notes that Googlebot's default crawl IP addresses appear to be in the US, and its requests do not set a language preference. Redirecting by IP can stop Googlebot seeing the UK page properly, or the US page, depending on the setup.
- A stronger UK page, with more links and more content, which search systems prefer as the main version.
- Thin US pages that differ only in currency or spelling.
- Shared structured data, such as prices in pounds on both versions.
How do you check what is happening?
- Use URL Inspection in Search Console on the US page and read the Google-selected canonical. If it shows the UK page, Google treats them as one.
- Validate hreflang on both pages: each lists itself and the other, with correct codes such as en-US and en-GB, and an x-default.
- Check canonical tags: each regional page should point to itself.
- Check redirects by requesting both pages from US and UK locations and without a language header.
- Compare content: how much of the US page differs from the UK page in prices, spelling, products, regulations and contact details.
- Check the overview from the US several times, since overviews vary, and note which URL it cites.
How do you fix it?
- Make each regional page self-canonical and keep hreflang complete and reciprocal, with an x-default.
- Differentiate the US page: US prices in dollars, US shipping and returns, US-specific products or plans, US regulations, US contact details and US spelling. The more genuinely different, the less likely Google treats them as duplicates.
- Avoid automatic IP redirects. Offer a region selector or banner instead, so crawlers and users can reach every version.
- Align structured data with each page: currency, availability and seller details for that market.
- Use separate product feeds for each country in Merchant Center, so shopping-related answers draw on the right market.
- Link internally within each region, so US pages link to US pages.
- Report persistent wrong citations with the feedback option on the overview.
How AI Overview availability varies by region is covered in where Google AI Overviews are available and why they might not appear in your region. Why a ranking page may not appear in AI answers at all is covered in why a page can rank in Google but still not appear in AI answers.
Does this affect other AI assistants too?
Often, and more so. ChatGPT, Perplexity and Claude do not use Google's hreflang handling. They retrieve pages through their own search sources and may cite whichever regional page ranks in those systems. Clear regional differences in content, prices and contact details help every assistant choose correctly. Explicit statements, such as "This page is for customers in the United States", also help, and so does a clear route to other regions.
What might an illustrative case look like?
Consider an illustrative online retailer of outdoor gear with UK and US sites in subfolders. US shoppers asking about waterproof jackets see AI Overviews citing the UK page with prices in pounds, while organic results show the US page. URL Inspection shows Google selected the UK page as canonical for the US version. The two pages were identical except for currency, and both carried Product markup with prices in pounds. The retailer adds US prices and US returns information to the US pages, and US-specific sizing notes. It fixes the structured data and makes each page self-canonical. It also removes an IP redirect that sent US visitors, including Googlebot, away from UK pages. Over the following weeks, overviews for US searches begin citing the US pages.
What do people ask about hreflang and AI Overviews?
Is hreflang ignored by AI Overviews?
Google has not said so directly, but overviews can cite a different regional version than organic results show, especially when pages are near-duplicates.
Should we merge UK and US pages?
Only if the offer is truly the same. If prices, products or rules differ, keep separate pages and make the differences clear.
Does a ccTLD help?
Country domains signal the market strongly, but they do not remove the need for distinct content and correct hreflang.
How long do fixes take?
Usually weeks, once Google recrawls both versions and reprocesses the canonical choice.
Published by The Kovmere Team · updated Sep 29, 2026 · More resources