Google's 'Alternate Names' Explains Why Hreflang Routes, Not Ranks

In 2018, SEO consultant Glenn Gabe documented a case that broke the rules: UK and Indian URLs, wrongly canonicalized to a U.S. page, still appeared in the correct country results while Search Console listed them as not indexed. Google's John Mueller confirmed the behavior in a webmaster hangout at the time. Google could swap the right country or language URL into the SERP even when only one page in the hreflang cluster was indexed. Gabe called it a "magic trick" because Google never explained the mechanism.

Eight years later, it got a name. In August 2026, Google's Gary Illyes responded to a LinkedIn question and described these URLs as alternate names. His wording gives international SEOs a mental model many had reverse-engineered for years: discovery, canonicalization, indexing, scoring, and serving are separate steps, and a URL does not have to pass through all of them independently to appear in search. Google can retain knowledge of a URL and its relationships even without independently indexing it.

Does hreflang create rankings?

No. The article's author, drawing on "tens of thousands of hreflang implementations," says he has never seen the annotation itself lift a ranking. Hreflang works like a cross-reference table. It tells Google this URL is the Italian equivalent of that one, or this page targets English speakers in Australia rather than the UK.

If a U.S. page ranks in the UK before hreflang is added, the UK alternate doesn't gain a new ranking score. What changes is which URL Google serves for the ranking it already computed. In Illyes' model, indexing and scoring can sit on one member of a duplicate cluster while the serving layer picks the right alternate. Hreflang routes rather than ranks.

What does the 38-market problem look like?

One global shoe brand illustrates the cost of duplication at scale:

• Roughly 98 market websites total
• About 38 of them in English, nearly identical to each other
• 22 shared the same dollar-sign currency symbol

The company saw 38 distinct market sites. A machine saw essentially one resource. Google can cluster near-duplicates, pick a canonical, and keep just enough information about the alternates to serve the right URL by country or language — which explains Gabe's "magic trick" without any bug or loophole.

Why does AI retrieval change the stakes?

AI systems don't have to return one blue link. They retrieve information, extract evidence from multiple sources, and assemble answers. The unit of value shifts from the URL to the information it contains. Motoko Hunt recently drew the same line: hreflang can declare the intended market relationship, but it cannot make an AI system treat the content as the best evidence for that market.

Microsoft offered a window into this with Web IQ, the retrieval and grounding infrastructure behind its AI experiences. Two details matter:

• Multilingual models represent semantically equivalent information as close together as possible, even across languages, with or without declared annotations.
• Retrieval works at the passage level, not the URL level.

The practical consequence: 20 near-identical market pages don't create 20 pieces of knowledge. They create one piece of knowledge with 20 addresses.

Can hreflang make content local?

It can't. If 20 market pages carry the same descriptions, specs, FAQs and claims, perfect hreflang doesn't make them meaningfully different. The author argues localization must move past translation plus currency swaps. Real differentiation includes:

• Market-specific products, regulations, certifications and warranties
• Different delivery options, pricing models and availability
• Different terminology, use cases, competitors and buying criteria
• Local team knowledge: customer examples and regulatory expertise

Those differences give a page a reason to exist — and give both search engines and AI systems something unique to retrieve.

What should international teams monitor next?

The "alternate names" explanation doesn't weaken hreflang's role. It clarifies it: the technical layer establishes relationships; the content establishes difference. As semantic retrieval improves, machines will increasingly recognize equivalence across URLs, languages and hreflang annotations regardless of how many folders or domains surround it.

Teams that combine international SEO, localization, content, product, legal and local market knowledge will spot where markets genuinely differ. Watch how AI systems like those built on Web IQ handle passage-level retrieval across markets — because serving the right URL is no longer the whole game.