Hreflang is valid but Google still ranks the US page in the UK. When do you conclude it’s a hreflang problem rather than a content or authority one?

1 reply

• 

  adminAdmin

  Original poster 3 hours ago

  The short answer is that you only have a hreflang problem when Google already treats your UK page as an indexed, valid alternate of the US page and still hands UK searchers the US URL. If the UK page is not part of the cluster as Google sees it, is not a true equivalent of the US page that ranks, or neither version deserves to rank in the UK, then valid markup cannot fix it, because hreflang decides which of your equivalent URLs is shown, not whether your content earns the position.

  The complication is that “valid” usually means a validator found reciprocal tags with correct codes. That is not the same as Google accepting the cluster. On top of that, for same-language pairs such as en-US and en-GB, Google often folds the two pages together and reports under one URL, which can make a working setup look broken in Search Console. So before blaming content or authority, I would first prove what UK users actually see.

  What hreflang can change, and what it cannot

  Think of hreflang as a translation table attached to a restaurant menu rather than a recommendation from the chef. Once a dish has been ordered, the table tells the waiter which version to bring to a UK diner. It has no say in whether the dish gets ordered in the first place.

  Technically, Google documents hreflang as a way to understand that pages “are localized variations of the same content” so it can point users to the most appropriate version. The same page states that if two pages do not both point to each other, the tags are ignored, and that Google does not use hreflang to detect a page’s language. Nothing in that documentation describes a ranking boost, which is why most international SEOs treat hreflang as a substitution mechanism layered on top of normal crawling, indexing and ranking.

  That gives you three separate questions, and only the first is really a hreflang question:

  1. Eligibility: is the UK page crawled, indexed and part of the cluster Google built?
  2. Equivalence: is the UK page a genuine alternate of the specific US URL that ranks, or just the “closest page” someone mapped it to?
  3. Competitiveness: does the cluster deserve to rank for UK searchers at all, given relevance, authority and market fit?

  Failures at step 2 are mapping and content problems. Failures at step 3 are content, authority or market problems. Hreflang only influences step 1, and only as a hint.

  The same-language trap: Google may be swapping the URL while reporting the US one

  This is the part that causes the most misdiagnosis. In May 2025 John Mueller said that when variants are the same (his example was fr-fr and fr-be), “it’s common that one is chosen as canonical”, and added: “Often hreflang will still swap out the URL, but reporting will be on the canonical URL”. He also noted that hreflang does not guarantee indexing.

  So if you filter Search Console by country = United Kingdom and see the US URL collecting impressions, that alone does not prove UK users saw the US URL. They may have seen the UK URL, with the data attributed to the canonical. Google’s canonicalisation documentation also says it prefers URLs that are part of hreflang clusters and asks you to specify a canonical in the same language, so canonical selection and hreflang are tightly linked for these pairs.

  Watch for this:

  Do not diagnose a hreflang failure from the Search Console Pages report alone. Check the live UK results for a sample of affected queries first. If the UK URL is what users see, you have a reporting quirk, not a ranking or hreflang problem.

  What I would check, in this order

  1. Confirm what UK users actually see. Use a rank tracker set to a UK location, plus spot checks from a clean browser session on a UK connection. Record the URL displayed, not just the position.
  2. Map the ranking US URL to its declared UK alternate. A common gap is hreflang on product and category templates only, while the URL ranking in the UK is a blog post, a US-only landing page or a URL variant with parameters that sits outside any cluster.
  3. Inspect the UK alternate in URL Inspection. Is it indexed? Compare the user-declared canonical with the Google-selected canonical. If Google selected the US URL, you are dealing with consolidation, not broken tags.
  4. Check the tags as Google sees them. Look at the rendered HTML in a live test. Confirm every hreflang target exactly matches the canonical URL (protocol, trailing slash, case, parameters), that no target redirects or carries noindex, that head tags and sitemap entries do not contradict each other, and that the region code is en-GB. Google’s documentation says it ignores the region part of an annotation that uses a reserved code such as UK, so en-uk does not target the United Kingdom even if a tool reports the tags as present and reciprocal.
  5. Check geo redirects and IP-based content. Google says it does not vary the crawler location used for a site to find possible variations of a page. If UK URLs redirect or change content based on IP, Googlebot may never see the UK version you think it sees.
  6. Check cross-locale signals you control. UK templates linking to US URLs in navigation, breadcrumbs, related products or blog modules, and canonicals pointing across locales, all send mixed messages about which URL represents the UK.
  7. Only then compare content and authority. Depth of localisation, links from UK sources, and what types of sites dominate the UK results for those queries.

  Reading the results: which problem you actually have

  What you find	Most likely problem	Confirm with	What to do
  UK users see the UK URL, but Search Console credits the US URL	Reporting on the canonical, not a user-facing problem	UK location rank checks, Google-selected canonical of the UK URL	Adjust reporting expectations; differentiate only if you need separate reporting or indexing
  UK users see the US URL; UK page is indexed, self-canonical and reciprocal tags appear in rendered HTML	Genuine hreflang or cluster processing problem	Exact URL matching across the cluster, sitemap and head conflicts, recrawl dates	Fix technically, request recrawl of both sides, re-check after both are recrawled
  Google-selected canonical of the UK URL is the US URL, and UK users see the US URL	Same-language consolidation: pages too similar for Google to keep apart	Compare main content; check currency, delivery, spelling, contact details	Localise the main content, not just the currency symbol; keep self-referencing canonicals
  The ranking US URL has no UK equivalent, or is paired with a loosely related UK page	Mapping or content gap	Pair audit of ranking US URLs against the hreflang map	Create a real UK equivalent, or accept that the US page serves that query
  Cluster is healthy, UK URL is shown, but it ranks poorly and local sites dominate	Content, authority or market fit	UK SERP composition, UK link profile, UK-specific intent	Hreflang cannot help; build UK relevance and demand signals

  Where content and authority genuinely enter the picture

  Google lists the signals it uses to work out a page’s intended audience: ccTLDs, hreflang, server location, and other signals such as local addresses and phone numbers, local language and currency, and links from other local sites. The Search Console country targeting setting is no longer supported, so a.com with a /uk/ folder has no manual override. It relies on hreflang plus those on-page and off-page signals.

  Market fit also matters in ranking, separately from which URL in your cluster gets shown. Aleyda Solis’s analysis of the May 2026 core update, using Sistrix visibility data, found that local-market (ccTLD) retail visibility rose about 20% in the UK while US.com marketplaces fell about 55% there, with those same.com domains roughly flat in the US. That is domain-level visibility across separate sites, not a hreflang study, so I would treat it as evidence that UK market relevance is weighed, not as proof about your subfolder. But it is a good reminder: if your UK folder is a thin copy of the US site, the question is not only “why is the wrong URL showing” but also “why would Google prefer either of our URLs over a local competitor”.

  Hypothetical example:

  A retailer runs example.com with /us/ and /uk/ folders and about 2,000 product pairs. The UK pages differ from the US pages only in the currency symbol and one delivery sentence. URL Inspection on a sample of UK products shows many with the US URL as the Google-selected canonical. UK rank checks show the UK URL for most of those, but the US URL for some. Here, the tags are mostly working and the reporting is misleading, while the remaining US URLs point to a consolidation problem. The fix is differentiation (GBP pricing in the main content, UK delivery and returns terms, UK sizing and terminology, a UK contact route), not another hreflang audit.

  How to test the diagnosis instead of arguing about it

  International problems are hard to test causally because Search Console attributes data to the canonical, and core updates keep moving the baseline (Google completed core updates in March and May 2026). A reasonable approach:

  • Hypothesis: the mis-served pairs fail because of X (a technical cluster issue, or consolidation from near-duplicate content).
  • Test and control: split affected pairs by template or category. Apply the fix to one group and leave a comparable group unchanged.
  • Primary metric: share of UK location rank checks that display the UK URL. Use this rather than Search Console URL attribution, for the reason above.
  • Secondary metrics: Google-selected canonical status of UK URLs, UK clicks to the /uk/ folder, and UK revenue or leads in local currency.
  • Duration: run until both sides of each pair show recrawl dates after the change, then allow several more weeks. Avoid windows around a core update where possible.
  • Seasonality: UK and US trading calendars differ, so compare test against control within the UK, not UK against US.

  What would change the decision: if the technical fix makes UK URLs their own canonicals and the swap becomes consistent, but UK traffic does not grow, the underlying issue was competitiveness all along. If differentiation shifts the Google-selected canonical and the displayed URL, the problem was consolidation. If neither moves, go back to step 2 and check whether the ranking US URLs were ever properly paired.

  Keep the commercial side in view. A UK visitor landing on a US page may see dollar pricing and US shipping, which usually hurts conversion more than it hurts rankings. Conversely, if UK users already see the UK URL and only the reporting is odd, spending engineering time to “fix” it has little return.

  The decision rule I would use

  I would call it a hreflang problem only when three things are true together: UK users demonstrably see the US URL, the UK alternate is indexed as its own canonical, and the pairing between the two exact URLs is complete as Google renders it. If the UK URL is canonicalised into the US one, treat it as a differentiation problem. If the ranking US URL has no true UK twin, treat it as a content gap. If the right UK URL is shown but simply does not compete, stop looking at hreflang and look at UK relevance, links and market fit.

  Need help with this on your own site?

  Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.

  See SEO services