What determines the specific meaning of a rel="alternate" link?

The attribute paired with it, such as hreflang, type, or media

The page's position in the sitemap

Whether the page is served over HTTPS

The order it appears in the head

Which use of rel="alternate" is the most important and current in 2026?

The hreflang language/region variant

The mobile-alternate media annotation

Does adding a rel="alternate" RSS feed link boost your rankings?

No — John Mueller said there's no direct ranking boost; its value is discovery

Yes, it's a direct ranking factor

Only for news sites in Top Stories

Only if the feed is in Atom format

How does rel="amphtml" relate to rel="alternate"?

rel="amphtml" is a different rel value that points to an AMP page — a cousin, not the same tag

They are the same tag and fully interchangeable

rel="amphtml" replaced rel="alternate" entirely in 2021

rel="amphtml" is only valid inside an XML sitemap

What is the single most common implementation bug across the uses of rel="alternate"?

A missing reciprocal link — the relationship declared from only one end

Placing the tag in the body instead of the head

rel="alternate": What It Does and When to Use It

TL;DR — rel="alternate" is a line of HTML that says “here’s another version of this page.” It doesn’t do just one thing — what it means depends on what’s next to it. Next to hreflang, it points to a page in another language. Next to a feed type, it points to your RSS feedAn RSS or Atom feed is an XML file listing a site's most recently published or updated URLs. Search engines accept it as a sitemap-style discovery signal for fresh content — not a replacement for a full XML sitemap.. Next to media, it points to a separate mobile page. None of these makes you rank higher — they just tell search engines these URLs are intentional relatives, not accidental duplicates.

What `rel="alternate"` is

If you’ve ever opened a page’s source code or run an SEO auditAn SEO audit checklist is the structured set of things you review across a site's technical health, on-page elements, content quality, and off-page authority — used to produce a short, prioritized action plan, not an exhaustive 100–200 item inventory. and seen something like <link rel="alternate" ...> in the <head>, you’ve met this tag. It’s a way of telling browsers and search engines: “there is another version of this document somewhere.”

The confusing part — and the reason it trips people up — is that it doesn’t have one meaning. It’s more like a fill-in-the-blank. The same rel="alternate" can mean completely different things depending on which other attribute sits next to it:

Next to hreflang → “here’s the same page in another language or for another country.”
Next to type="application/rss+xml" → “here’s this page’s RSS feed.”
Next to media → “here’s a separate mobile version of this page” (an old pattern you’ll mostly see on legacy sites).

So rel="alternate" is one tag doing several unrelated jobs. Knowing which job you’re looking at is the whole skill.

The one you’ll actually use: hreflang

For most sites, the only version of rel="alternate" that matters is the hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. one — used to connect the English, Spanish, French, etc. versions of a page so Google shows the right one to the right searcher. That has its own full guide on this site (it’s a big topic with strict rules), so this article stays at the “what is this tag and what are all its jobs” level and points you there for the deep dive.

The thing to understand

rel="alternate" is not a ranking booster. Adding an RSS feed link won’t lift your positions. Adding hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. won’t either — it just routes the right language version to the right person. None of these tags guarantee that a page gets crawled, indexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed., or treated as one consolidated entity, either — they’re hints for search engines, not commands. The whole point of the tag is to say “these similar URLs are on purpose — treat them as relatives, not as duplicate spam.”

And most of these uses ask you to declare the relationship from both ends — the main page points to the alternate, and the alternate points back. A one-way link usually gets ignored.

Want the full map — all the uses, which ones still matter in 2026, and the exact markup for each? Switch to the Advanced tab.

TL;DR — rel="alternate" is the WHATWG-defined “alternate” link relation, and its meaning is set entirely by the attribute paired with it: hreflang → language/region variant (current, high-value — full rules in the hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. guide); type="application/rss+xml" / "application/atom+xml" → feed autodiscovery (current, niche, discovery-only); media → separate-mobile-URL variant (legacy — responsive designA mobile configuration that serves the same HTML on the same URL to every device and uses CSS media queries to adapt the layout to the viewport. It's Google's recommended setup and requires a correct viewport meta tag to work. is Google’s default now). A related but distinct tag, rel="amphtml", points a canonical page at its AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories. version. The throughline is that each alternate relationship has its own syntax and validation rules — three of the four (hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others., mobile-alternate, AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories.) require reciprocal pairing from both ends; RSSAn RSS or Atom feed is an XML file listing a site's most recently published or updated URLs. Search engines accept it as a sitemap-style discovery signal for fresh content — not a replacement for a full XML sitemap./Atom feed autodiscovery does not. None of these is a ranking lever, and none guarantees crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor., indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed., or consolidation; rel="alternate" is fundamentally a routing or discovery hint, not a directive.

What `rel="alternate"` actually is

It’s a value of the HTML link element’s rel (relationship) attribute, defined in the WHATWG HTML Living Standard’s link-type list. On its own, “alternate” just means “an alternate representation of the current document.” The specific meaning comes from the other attribute you pair it with. That’s why one tag ends up doing several unrelated SEO jobs — and why generalist “rel=alternate explained” posts tend to blur them together.

I’ve long framed this tag through the lens of duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling.. In my Search Engine Land piece The myth of the duplicate content penalty, I listed it as one of the tools that “consolidate alternate versions of a page, such as mobile or various country/language pages.” That’s the unifying thesis worth holding onto: every use of rel="alternate" exists to tell search engines these different URLs are intentional relatives, handle them as one entity — the opposite of accidental duplication. (For how engines actually pick and consolidate a representative URL, see the sibling topic on canonicalizationHow search engines pick one canonical URL among duplicates and consolidate signals onto it..) None of these annotations guarantees an outcome — not crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor., not indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed., not consolidation, not rankings or traffic, not feed subscriptions, and not citation by an AI answer engine. They’re hints search engines can act on, not directives they must follow.

The four SEO uses (and one close cousin)

1. Hreflang — language/region alternates (current, most important)

This is the one that matters most in 2026. Paired with hreflang, rel="alternate" declares a language or regional variant:

<link rel="alternate" hreflang="es" href="https://example.com/es/page/" />

Google’s framing: “If you have multiple versions of a page for different languages or regions, tell Google about these different variations,” using hreflang “so that we can understand that these pages are localized variations of the same content.” The load-bearing rule is reciprocity — Google: “Each language version must list itself as well as all other language versions.” Break that and Google ignores the pair (it’s a hint, not a directive — wrong hreflang is ignored, not penalized).

That’s the mental model. I’m deliberately not re-deriving ISO language/region codes, x-default, or the three implementation methods here — that all lives in the dedicated hreflang deep dive on this site. Go there for implementation; stay here for the mechanism-level view.

2. RSS/Atom feed autodiscovery (current, niche)

Paired with a feed type, rel="alternate" tells browsers and feed readers where your syndication feed lives:

<link rel="alternate" type="application/rss+xml" title="Example Feed"
      href="https://example.com/feed.xml" />

Swap application/atom+xml for an Atom feed. This is the use almost every generalist article forgets, even though “rel alternate rss” is a real query cluster. What it does not do is boost rankings — John Mueller has been explicit that “if you are looking for a ranking boost by having an RSS feed, that’s not going to happen” and that “there’s no direct ranking boost for the website itself” (Search Engine Roundtable coverage). The real value is discovery: feeds work like a lightweight sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., helping Google find new and updated URLs faster (Lumar’s office-hours summary of Mueller’s comments). Discovery, not ranking.

3. Mobile-alternate (separate mobile URLs) — legacy

Paired with media, rel="alternate" points a desktop URL at a separate mobile (m-dot) URL:

<link rel="alternate" media="only screen and (max-width: 640px)"
      href="https://m.example.com/" />

…reciprocated by a rel="canonical" on the mobile page pointing back to the desktop URL. This still appears in Google’s mobile-first indexing best-practices docs (updated December 2025), but it’s explicitly the non-preferred option: Google “recommends Responsive Web DesignA mobile configuration that serves the same HTML on the same URL to every device and uses CSS media queries to adapt the layout to the viewport. It's Google's recommended setup and requires a correct viewport meta tag to work. because it’s the easiest design pattern to implement and maintain,” and files the separate-URLs annotation under “additional best practices” — i.e., legacy support. With mobile-first indexingGoogle's practice of using the mobile version of a page's content — crawled by Googlebot smartphone — for indexing and ranking. It is not a separate index and not a ranking boost. complete for all sites since July 2024, Google evaluates the mobile version of a page regardless of your setup. Don’t build new mobile-alternate setups in 2026; only maintain one if you’re still stuck on m-dot URLs and can’t migrate to responsive yet.

4. AMP’s `rel="amphtml"` — a related but distinct tag

Here’s a disambiguation almost nobody makes cleanly: rel="amphtml" is not rel="alternate". It’s a different rel value in the same “here’s another version of this page” family, and the two get conflated constantly. It points a canonical non-AMP page at its AMP version:

<link rel="amphtml" href="https://example.com/page.amp.html" />

…reciprocated by rel="canonical" on the AMP page pointing back. The markup still works exactly as documented for any site that keeps AMP, but AMP-the-strategy lost its reason to exist years ago (see the 2026-status section below). They’re cousins, not the same tag.

Which of these still matter in 2026

Use	Attribute pairing	Status in 2026
Hreflang	`hreflang`	Current, high-value — the one that matters
RSS/Atom feed	`type="application/rss+xml"`	Current, niche — discovery only, no ranking effect
Mobile-alternate	`media`	Legacy — maintain, don’t newly adopt
AMP (`rel="amphtml"`)	(different rel value)	Optional since 2021; infra wound down

AMP specifically: Google removed the requirement that pages be AMP to appear in Top Stories in 2021 and retired the lightning-bolt badge that July, making Core Web Vitals / page experience the operative signal instead of the AMP format itself (Google’s page-experience update post; Search Engine Land). Google now “indexes AMP pages just like other web pages, and applies the same standard to all pages, regardless of the technology used.” Then on July 1, 2026, Google ended cache-served AMP pages in Search entirely — clicks now route straight to the publisher’s own AMP-hosted page instead of a google.com AMP viewer URL, and Google removed references to “the AMP viewer, AMP Cache, and signed exchanges” from its docs (Search Engine Journal; Search Engine Roundtable). If you still run AMP, keep the rel="amphtml" markup correct; nobody should be adopting AMP anew for SEO reasons.

The throughline: reciprocal pairing

Three of the four uses want the relationship declared from both ends — RSS/Atom feed autodiscovery is the exception; it’s a one-way discovery link with no return-tag requirement, and Google’s own hreflang docs scope the reciprocity rule to localized-version clusters, not to every rel="alternate" use:

hreflang — every version lists itself and every other version.
mobile — rel="alternate" on desktop, rel="canonical" back on mobile.
AMP — rel="amphtml" on the canonical page, rel="canonical" back on the AMP page.

Broken reciprocity is the single most common implementation bug across these three. If a relationship that’s supposed to be reciprocal is one-way, expect it to be ignored or half-declared — RSS/Atom needs no return link at all.

Each alternate system has its own return signal; RSS and Atom are discovery links, not reciprocal page pairs. Source: Patrick Stox

For hreflang, the English and Spanish pages list themselves and one another. For legacy separate mobile URLs, the desktop page uses rel alternate with media and the mobile page points back with rel canonical. AMP is a related but distinct pattern: the canonical page uses rel amphtml and the AMP page points back with rel canonical. RSS and Atom feed autodiscovery is one-way and is not a reciprocal page pairing.

Common mistakes

Missing the reciprocal link. The number-one bug. A one-way rel="alternate" relationship usually gets ignored (hreflang) or leaves the pairing half-declared (mobile/AMP).
Confusing rel="alternate" with rel="amphtml". Different rel values, different jobs. AMP uses rel="amphtml", not rel="alternate".
Expecting a ranking boost. None of these lift positions. hreflang routes; feed links aid discovery; AMP hasn’t carried ranking weight since 2021.
Building new mobile-alternate or AMP setups in 2026. Responsive design is the default; AMP has no SEO upside. These are maintenance patterns, not build patterns.
Running separate mobile URLs and responsive design at once. Mueller has warned this can confuse Google’s processing (Search Engine Roundtable) — pick one.

Bing and other engines

Bing supports hreflang via rel="alternate" but treats it as comparatively weak. Microsoft’s Fabrice Canel has said “hreflang is indeed a far weaker signal than content-language at Bing” (via Search Engine Roundtable) — so at Bing, rel="alternate"/hreflang is one input among several (the content-language header/meta, <html lang>, inbound links, and visitor geography) rather than authoritative. Full Bing/hreflang treatment lives in the hreflang guide.

Where this sits

rel="alternate" is a link-level signal that lives in your <head> alongside the rest of the meta tags that matter for SEOMeta tags are HTML elements in a page's head that pass metadata about the page to search engines and browsers. For SEO only a few matter — the title element, the meta description, and the robots meta tag — while meta keywords and most others are ignored. — it’s a sibling of the robots meta tagThe robots meta tag is an HTML element in a page's head — <meta name=\"robots\" content=\"noindex\"> — that tells search engines how to index and serve that page. It's crawl-then-obey: a page blocked in robots.txt is never fetched, so the tag is never seen., the title element, and the meta descriptionThe meta description is an HTML head tag — `<meta name=\"description\" content=\"…\">` — that suggests a short summary of the page for the search snippet. It's not a Google ranking factor, and Google rewrites it the majority of the time, but a good one can still lift click-through. in that on-page cluster, even though it’s technically a link element rather than a meta one. Its closest conceptual relative is canonicalizationHow search engines pick one canonical URL among duplicates and consolidate signals onto it.: canonical says “these duplicates are the same page, pick one,” while rel="alternate" says “these are intentionally different versions, keep them all but understand they’re related.” For the hreflang-specific rules — codes, x-default, the three implementation methods, auditing clusters at scale — see the dedicated hreflang guide.

AI summary

A condensed take on the Advanced version:

rel="alternate" is a family, not a feature. It’s the WHATWG “alternate” link relation, and the attribute paired with it sets the meaning: hreflang → language/region variant; type="application/rss+xml"/"application/atom+xml" → feed autodiscovery; media → separate mobile URL (legacy).
rel="amphtml" is a close cousin, not the same tag — a different rel value that points a canonical page at its AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories. version.
2026 status: hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. is current and high-value; RSSAn RSS or Atom feed is an XML file listing a site's most recently published or updated URLs. Search engines accept it as a sitemap-style discovery signal for fresh content — not a replacement for a full XML sitemap./Atom is current but niche and discovery-only; mobile-alternate is legacy (responsive is Google’s default; mobile-first indexingGoogle's practice of using the mobile version of a page's content — crawled by Googlebot smartphone — for indexing and ranking. It is not a separate index and not a ranking boost. completed July 2024); AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories. lost special treatment in 2021 and Google ended cache-served AMP pages in Search on July 1, 2026.
The throughline is reciprocal pairing for three of the four — declare the relationship from both ends for hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. (lists all versions), mobile, and AMP (pair alternate/amphtml with a canonical back); RSS/Atom feed autodiscovery is one-way and needs no return link. Broken reciprocity is the most common bug among the three that require it.
None of these is a ranking lever, and none guarantees an outcome. hreflang routes the right variant to the right searcher; RSS feed links aid discovery, not rankings (Mueller: “no direct ranking boost”); AMP carries no ranking weight. None of it guarantees crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor., indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed., consolidation, traffic, feed subscriptions, or AI citationsAn AI citation is the visible source link an AI answer engine shows next to its generated text — the clickable reference that credits the web page it used. A citation's presence is a separate thing from whether the cited page actually supports the statement, and from being retrieved (read behind the scenes) or merely mentioned (named without a link); citation is driven more by brand mentions and being retrievable than by traditional ranking. — these are hints, not directives. It’s a routing/consolidation signal — Patrick’s framing: these are intentional relatives, not accidental duplicates.
Bing treats hreflang via rel="alternate" as weak (Canel: “far weaker signal than content-language at Bing”).
Full hreflang implementation lives in the dedicated hreflang guide — this hub is the mechanism-level view and routes there.

Official documentation

Primary-source documentation and specs.

Google

Localized versions of your pages (hreflang) — the rel="alternate" hreflang mechanism and the reciprocal-linking rule.
Consolidate duplicate URLs — where Google describes rel="alternate" as one of the link annotation methods for specifying alternate versions of a page.
Mobile sites and mobile-first indexing best practices — the rel="alternate" media=… separate-mobile-URL annotation and the responsive-design recommendation.
About AMP on Google Search — rel="amphtml" markup and AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories.’s current (non-special) indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. treatment.
More time, tools, and details on the page experience update (April 2021) — where AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories. stopped being required for Top Stories.
Best practices for XML sitemaps and RSS/Atom feeds (2014) — feeds as a discovery input.

Spec / reference

WHATWG HTML Living Standard — link types — the canonical definition of the “alternate” relation.
MDN — the rel attribute — developer-facing reference for every rel value.
Microformats wiki — rel-alternate — the HTML-spec-purist reference cited by many practitioner pages.

Quotes from the source

On-the-record statements from Google, Bing, and Patrick. Where a link is a deep link, it jumps to the quoted passage on the source page.

Google — hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. via rel="alternate"

“If you have multiple versions of a page for different languages or regions, tell Google about these different variations.” — Google Search Central docs. Jump to quote
“Each language version must list itself as well as all other language versions.” — the reciprocity rule that applies to every hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. rel="alternate" cluster. Jump to quote

Google — AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories.’s non-special status

“Google Search indexes AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories. pages just like other web pages, and applies the same standard to all pages, regardless of the technology used to build the page.” — Google Search Central docs, About AMP. Jump to quote

Google — responsive over separate mobile URLs

“Google recommends Responsive Web DesignA mobile configuration that serves the same HTML on the same URL to every device and uses CSS media queries to adapt the layout to the viewport. It's Google's recommended setup and requires a correct viewport meta tag to work. because it’s the easiest design pattern to implement and maintain.” — Google Search Central docs, mobile-first indexingGoogle's practice of using the mobile version of a page's content — crawled by Googlebot smartphone — for indexing and ranking. It is not a separate index and not a ranking boost. best practices. Jump to quote

John Mueller, Google — RSS feedsAn RSS or Atom feed is an XML file listing a site's most recently published or updated URLs. Search engines accept it as a sitemap-style discovery signal for fresh content — not a replacement for a full XML sitemap. and ranking (via Search Engine Roundtable)

“If you are looking for a ranking boost by having an RSS feed, that’s not going to happen” — and “there’s no direct ranking boost for the website itself.” Read the coverage

Fabrice Canel, Microsoft Bing — hreflang as a weak signal (via Search Engine Roundtable)

“hreflang is indeed a far weaker signal than content-language at Bing.” Read the coverage

Patrick Stox — rel="alternate" as a consolidation tool

“Rel=‘alternate’. Used to consolidate alternate versions of a page, such as mobile or various country/language pages.” — from my Search Engine Land piece on the duplicate-content penalty myth. Read the article

Note: the Mueller RSS lines and the Canel Bing line are relayed through Search Engine Roundtable’s reporting of Google/Microsoft statements, not primary source pages — confirm against the originals before treating them as final. The hreflang reciprocity and responsive-design quotes are verbatim from Google’s live Search Central docs.

Which `rel="alternate"` do I need — or do I need one at all?

Work top-down; stop at the first branch that fits.

1. Are you connecting the same content in different languages or for different regions? → Use rel="alternate" hreflang="…". Every version must list itself and all the others (reciprocal). This is the high-value, current use — follow the dedicated hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. guide for the full rules. Done.

2. Do you publish a blog/news feed and want browsers and readers to discover it? → Use rel="alternate" type="application/rss+xml" (or application/atom+xml) in your <head>. Good for discovery and UX; expect no ranking effect. Done.

3. Do you run a separate mobile URL (an m. / m-dot site)? → Can you migrate to responsive designA mobile configuration that serves the same HTML on the same URL to every device and uses CSS media queries to adapt the layout to the viewport. It's Google's recommended setup and requires a correct viewport meta tag to work.? Yes → do that; you won’t need any rel="alternate" media=… at all (Google’s default recommendation). No, stuck on m-dot for now → maintain the full pairing: rel="alternate" media=… on desktop + rel="canonical" back on mobile. Don’t also run responsive on the same URLs. Done.

4. Do you still run AMP pagesAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories.? → This is rel="amphtml", not rel="alternate". Keep rel="amphtml" on the canonical page + rel="canonical" back on the AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories. page. But note: AMP carries no ranking benefit (since 2021) and Google ended cache-served AMP pages in Search on July 1, 2026 — don’t adopt AMP anew. Done.

5. None of the above? → You probably don’t need rel="alternate" at all. It’s a routing/consolidation signal for genuine alternate versions — not something to add “for SEO.” Done.

`rel="alternate"` cheat sheet

The tag by the attribute next to it

Markup	Job	Status 2026	Reciprocal link needed?
`rel="alternate" hreflang="es"`	Language/region variant	Current, high-value	Yes — every version lists all others
`rel="alternate" type="application/rss+xml"`	RSS feedAn RSS or Atom feed is an XML file listing a site's most recently published or updated URLs. Search engines accept it as a sitemap-style discovery signal for fresh content — not a replacement for a full XML sitemap. autodiscovery	Current, niche	No
`rel="alternate" type="application/atom+xml"`	Atom feed autodiscovery	Current, niche	No
`rel="alternate" media="only screen and (max-width: 640px)"`	Separate mobile URL	Legacy	Yes — `rel="canonical"` back on mobile
`rel="amphtml"` (different rel value)	AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories. page pointer	Optional; infra wound down	Yes — `rel="canonical"` back on AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories.

Fast facts

Not a ranking factor — any of these. hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. routes; RSS aids discovery; AMP lost special treatment in 2021.
Reciprocity is the #1 bug. One-way relationships get ignored (hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others.) or half-declared (mobile/AMP).
rel="alternate" ≠ rel="amphtml" — different values, commonly conflated.
Mobile-alternate is legacy — responsive is Google’s default; mobile-first indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. completed July 2024.
AMP cache/viewer ended July 1, 2026 — clicks now go straight to the publisher’s AMP-hosted page.
Bing treats hreflang via rel="alternate" as weak vs. content-language.

The mental model: rel="alternate" says “these different URLs are intentional relatives, not accidental duplicates.” Its cousin rel="canonical" says “these duplicates are the same page — pick one.”

What not to do with `rel="alternate"`

Concrete mistakes people actually make with this tag, drawn straight from the Advanced walkthrough above.

Declaring the relationship from only one end. This is the number-one bug across every use of rel="alternate" that requires reciprocity — hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others., mobile-alternate, and AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories. (RSSAn RSS or Atom feed is an XML file listing a site's most recently published or updated URLs. Search engines accept it as a sitemap-style discovery signal for fresh content — not a replacement for a full XML sitemap./Atom feed autodiscovery is one-way by design and doesn’t apply here). Why it’s wrong: a one-way hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. relationship usually gets ignored outright, and a one-way mobile/AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories. pairing leaves the relationship half-declared. Do instead: for hreflang, make every language version list itself and all other versions; for mobile and AMP, pair rel="alternate" (or rel="amphtml") on the primary page with a rel="canonical" pointing back on the alternate page.
Confusing rel="alternate" with rel="amphtml". Why it’s wrong: they’re different rel values doing different jobs, and treating them as interchangeable leads to malformed markup or missed AMP annotations. Do instead: use rel="amphtml" specifically for AMP pointers, and reserve rel="alternate" for hreflang, feed, and mobile-alternate uses.

Advertisement
Expecting a ranking boost from any of these. Why it’s wrong: hreflang routes the right language variant to the right searcher, RSS/Atom links aid discovery (Mueller: no direct ranking boost), and AMP hasn’t carried ranking weight since 2021 — none of it lifts positions. Do instead: add these tags for the routing/discovery job they actually do, not as an SEO lever.
Building new mobile-alternate or AMP setups in 2026. Why it’s wrong: responsive designA mobile configuration that serves the same HTML on the same URL to every device and uses CSS media queries to adapt the layout to the viewport. It's Google's recommended setup and requires a correct viewport meta tag to work. is Google’s default recommendation, and mobile-first indexingGoogle's practice of using the mobile version of a page's content — crawled by Googlebot smartphone — for indexing and ranking. It is not a separate index and not a ranking boost. has been complete for all sites since July 2024 — new m-dot or AMP builds add maintenance burden with no upside. Do instead: only maintain an existing mobile-alternate or AMP setup if you’re not yet migrated; don’t adopt either pattern fresh.
Running separate mobile URLs and responsive design on the same pages. Why it’s wrong: Google’s John Mueller has warned this combination can confuse Google’s processing of the page. Do instead: pick one pattern — responsive design, or a fully reciprocated separate-mobile-URL setup — not both at once.

Reciprocal-pairing checklist

Whatever job your rel="alternate" tag is doing, use this checklist to confirm the relationship is declared correctly from both ends.

Before you add anything

Identify which job this tag is doing — hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. (language/region), feed autodiscovery, or mobile-alternate — since the required attribute and pairing rule differ for each.
Confirm you actually need it. If none of the three jobs applies, you probably don’t need rel="alternate" at all.

If it’s hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others.

Add <link rel="alternate" hreflang="…" href="…"> for every language/region variant, on every version of the page.
Confirm each version lists itself as well as all other versions — reciprocity across the whole cluster, not just a pair.
If you need a language-code deep dive or a cluster-scale audit, follow through to the dedicated hreflang guide.

If it’s a feed

Add <link rel="alternate" type="application/rss+xml" href="…"> (or application/atom+xml for AtomAn RSS or Atom feed is an XML file listing a site's most recently published or updated URLs. Search engines accept it as a sitemap-style discovery signal for fresh content — not a replacement for a full XML sitemap.) once per feed.
Treat it as a discovery aid, not a ranking lever — no reciprocal link is required for this one.

If it’s mobile-alternate

Decide whether you can migrate to responsive designA mobile configuration that serves the same HTML on the same URL to every device and uses CSS media queries to adapt the layout to the viewport. It's Google's recommended setup and requires a correct viewport meta tag to work. instead — if yes, skip this pattern entirely.
If you’re stuck on a separate mobile URL, add rel="alternate" media="…" on the desktop page.
Add rel="canonical" back on the mobile page pointing to the desktop URL.
Confirm you are not also running responsive design on the same URLs at the same time.

If it’s AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories.

Add rel="amphtml" (not rel="alternate") on the canonical page pointing to the AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories. version.
Add rel="canonical" back on the AMP page pointing to the canonical page.
Don’t build a new AMP setup — only maintain what already exists.

Final check

If you implemented hreflang, mobile-alternate, or AMP, verify reciprocity end to end — a one-way relationship is the most common bug in those three and usually gets ignored. Feed autodiscovery is one-way by design; skip this check for RSS/Atom.

Confirm your `rel="alternate"` change actually took effect

Pass/fail checks for the reciprocity rule this article keeps coming back to: declare the relationship from both ends, then verify it landed correctly.

Hreflang reciprocity after adding tags

Test to run: Run the affected URL (or its sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing.) through the returntag - hreflang checker to crawl the whole hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. cluster and flag missing return tagsIf page A lists page B as an alternate, B must list A back — or Google ignores the pair., broken targets, and self-reference issues. Expected result: every language version in the cluster lists itself and all other versions, with no missing-return-tag or broken-target flags. Failure interpretation: a flagged missing return tag means at least one version isn’t listing another — the pairing is one-way and Google will likely ignore it. Monitoring window: re-check immediately after deploy, then again after your next crawl (hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. recognition depends on Google recrawling all versions in the cluster, which can take days to weeks). Rollback trigger: if return tags are still missing after a full recrawlCrawl frequency is how often a search engine comes back to re-fetch a page it already knows about. Popular pages that change often get refreshed many times a day; stable pages can go weeks or months between crawls — and you influence it indirectly, not by setting a dial. cycle, revert to the last known-good markup and regenerate it rather than patching by hand.

Hreflang markup generation before you ship it

Test to run: Build your URL × locale matrix in the hreflang Generator + Linter (/tools/hreflang-generator/) before you ship any hreflang change. Expected result: the linter reports no wrong region codes, no duplicates, and no missing fallbacks for the locale set you entered. Failure interpretation: any flagged region code or duplicate means the markup you’re about to ship already has the exact bug this article calls out as the most common one. Monitoring window: this is a pre-deploy check — run it once per markup change, before publishing. Rollback trigger: don’t ship until the linter is clean; there’s nothing to roll back if you catch it here first.

Mobile-alternate or AMP reciprocal canonical

Test to run: curl -I (or view-source) both the primary page and its alternate (mobile or AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories.) version, and manually confirm the rel="alternate" / rel="amphtml" tag on the primary page and the rel="canonical" tag pointing back on the alternate page. Expected result: each page’s markup correctly references the other — primary points to alternate, alternate canonicals back to primary. Failure interpretation: if the alternate page’s canonical is missing or points somewhere else, the pairing is broken and the alternate may get treated as an accidental duplicate instead of an intentional one. Monitoring window: check immediately after deploy; these are static tags, so there’s no propagation delay to wait out. Rollback trigger: a missing or wrong reciprocal canonical means fixing the markup immediately — don’t wait for a ranking or traffic signal to notice.

Test yourself: rel=“alternate”

Five quick questions on what rel="alternate" does and when to use it. Pick an answer for each, then check.

Resources worth your time

My related writing

The myth of the duplicate content penalty (Search Engine Land) — where I frame rel="alternate" as a tool to “consolidate alternate versions of a page, such as mobile or various country/language pages.”
Hreflang: The Easy Guide for Beginners (Ahrefs) — the full hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. implementation walkthrough, the most important rel="alternate" use.

My speaking

How Search Works (SlideShare) — my walkthrough of crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor., renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM., indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed., and serving, where consolidation signals like rel="alternate" fit. (My standing disclaimer applies: “This is my understanding of systems… not going to be 100% complete or accurate.”)

Official

From around the industry

Google Ends Cache-Served AMP Pages In Search (Search Engine Journal) — the July 1, 2026 shutdown of the AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories. viewer/cache serving path.
Google Search Now Sends Searchers To Publisher-Hosted AMP Pages (Search Engine Roundtable) — companion coverage of the same change.
AMP won’t be required for Google’s Top Stories section (Search Engine Land) — the 2021 inflection point that ended AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories.’s special treatment.
Google: RSS Feeds Won’t Boost Rankings (Search Engine Roundtable) — Mueller on feeds as discovery, not ranking.
Bing: hreflang Is A Weak Signal (Search Engine Roundtable) — Fabrice Canel on content-language vs. hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. at Bing.
Mobile-First Indexing Goes Mobile-Only (Ahrefs) — why separate-mobile-URL setups are legacy territory now.
WHATWG HTML Living Standard — link types and MDN — the rel attribute — the spec-level definitions for developers.

rel="alternate"

rel="alternate" is a value of the HTML link rel attribute that declares another version of the current document. Its exact meaning depends on the attribute paired with it: hreflang for a language/region variant, type for an RSS/Atom feed, or media for a separate mobile URL. It's a routing and consolidation signal, not a ranking lever.

rel="alternate"

rel="alternate" is a value of the HTML link rel attribute — used in the <link> element in a page’s <head> — that tells a browser or search engine “here is another version of this document.” It’s defined in the WHATWG HTML Living Standard as one of the standard link relation types, and it isn’t a single feature: its meaning is set entirely by whichever attribute rides alongside it.

Paired with hreflang, it declares a language or region variant of the page — the hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. mechanism, and by far the most common and important SEO use today. Paired with type="application/rss+xml" or type="application/atom+xml", it’s feed autodiscovery, pointing browsers and readers to the page’s syndication feed. Paired with media, it historically pointed from a desktop URL to a separate mobile (m-dot) URL — a legacy pattern now that responsive designA mobile configuration that serves the same HTML on the same URL to every device and uses CSS media queries to adapt the layout to the viewport. It's Google's recommended setup and requires a correct viewport meta tag to work. is Google’s default recommendation. A closely related but technically distinct tag, rel="amphtml", points a canonical page at its AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories. version.

The thread across every use is the same: rel="alternate" tells search engines that similar-but-intentionally-different URLs are deliberate relatives of one another, not accidental duplicates. Three of the four uses — hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others., mobile-alternate, and AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories. — need that relationship declared with a reciprocal link from the other end; RSSAn RSS or Atom feed is an XML file listing a site's most recently published or updated URLs. Search engines accept it as a sitemap-style discovery signal for fresh content — not a replacement for a full XML sitemap./Atom feed autodiscovery is one-way. None of these uses is a ranking factor by itself, and none guarantees crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor., indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed., or consolidation.

Build-time retrieval analysis plus live signals for this exact article. The automatic chunk report includes a deterministic readiness score and is ready without a model download.

How this article chunks build baseline · local controls

A structure-aware retrieval preview using the shared Chunk Tester engine. The default lens is shown immediately; switch scopes to see what happens when every authored lens is treated as one source document.

Target size 300 tokens Overlap 15% Retrieval query

96readiness score / 100

9chunks

~355median tokens

100%standalone

1flagged chunks

Advanced lens only — the version readers see when this page opens.

Baseline generated at build time with a 300-token target and 15% overlap. Controls re-run the same deterministic engine in this browser.

Matching retrieval chunks

Ranked lexically for the page title, Trends, and Ngram terms. Enter a short query to test a different retrieval intent.

chunk 1 ~369 tok Default visible lens

rel="alternate": What It Does and When to Use It **TL;DR —** `rel="alternate"` is the WHATWG-defined "alternate" link relation, and its meaning is set entirely by the attribute paired with it: **`hreflang`** → language/r…

chunk 4 ~251 tok 2. RSS/Atom feed autodiscovery *(current, niche)*

chunk 2 ~408 tok What `rel="alternate"` actually is

It's a value of the HTML `link` element's `rel` (relationship) attribute, defined in the WHATWG HTML Living Standard's link-type list. On its own, "alternate" just means "an alternate representation of the current docume…

chunk 8 ~359 tok The throughline: reciprocal pairing

Three of the four uses want the relationship declared from **both ends** — RSS/Atom feed autodiscovery is the exception; it's a one-way discovery link with no return-tag requirement, and Google's own hreflang docs scope …

chunk 7 ~355 tok Which of these still matter in 2026

Methodology and limits

The readiness score starts with the percentage of standalone chunks and subtracts up to 35 points for the share carrying structural warnings. Structure-aware Markdown blocks use the selected 100–800-token target and 0–40% overlap. Tokens are estimated at roughly four English characters each. “Standalone” means a chunk has heading context and does not open with a context-dependent continuation.

Matching uses the shared lexical BM25 and term-cosine ranker. It is not an embedding or a replica of Google, an answer engine, or any vendor retriever. These chunk controls keep the article text in this browser and make no network request. The build-time baseline remains the reproducible report for this page.

Test your own content in Chunk Tester →

84readiness score / 100

27chunks

~337median tokens

96%standalone

9flagged chunks

All 12 authored lenses in this article source, with lens boundaries retained as headings.

Baseline generated at build time with a 300-token target and 15% overlap. Controls re-run the same deterministic engine in this browser.

Matching retrieval chunks

Ranked lexically for the page title, Trends, and Ngram terms. Enter a short query to test a different retrieval intent.

chunk 26 ~321 tok Resources worth your time

Five quick questions on what `rel="alternate"` does and when to use it. Pick an answer for each, then check. All lens Resources worth your time **My related writing** • The myth of the duplicate content penalty (Search E…

chunk 1 ~285 tok Whole article

rel="alternate": What It Does and When to Use It Beginner lens **TL;DR —** `rel="alternate"` is a line of HTML that says "here's another version of this page." It doesn't do just one thing — what it means depends on what…

chunk 25 ~457 tok Hreflang markup generation before you ship it

**Test to run:** Build your URL × locale matrix in the **hreflang Generator + Linter** (`/tools/hreflang-generator/`) before you ship any hreflang change. **Expected result:** the linter reports no wrong region codes, no…

chunk 7 ~251 tok 2. RSS/Atom feed autodiscovery *(current, niche)*

chunk 4 ~357 tok Advanced lens

**TL;DR —** `rel="alternate"` is the WHATWG-defined "alternate" link relation, and its meaning is set entirely by the attribute paired with it: **`hreflang`** → language/region variant (current, high-value — full rules i…

Methodology and limits

The readiness score starts with the percentage of standalone chunks and subtracts up to 35 points for the share carrying structural warnings. Structure-aware Markdown blocks use the selected 100–800-token target and 0–40% overlap. Tokens are estimated at roughly four English characters each. “Standalone” means a chunk has heading context and does not open with a context-dependent continuation.

Matching uses the shared lexical BM25 and term-cosine ranker. It is not an embedding or a replica of Google, an answer engine, or any vendor retriever. These chunk controls keep the article text in this browser and make no network request. The build-time baseline remains the reproducible report for this page.

Test your own content in Chunk Tester →

Search Console

Loading…

GA4 traffic (28d)

Loading…

Cloudflare traffic (7d)

Loading…

CrUX field data (28d, phone)

Loading…

Google NLP entities

Loading…

Changelog

Updated Jul 25, 2026.

Editorial summary and recorded change details.

Summary

Aligned legacy tool display names with returntag - hreflang checker and Scout Site Audit Free.

Change details

Updated the linked tool names to match their current public labels.

Full comparison unavailable — no prior snapshot was archived for this revision.

Updated Jul 18, 2026.

Editorial summary and recorded change details.

Summary

Corrected an internal overgeneralization: reciprocal pairing applies to hreflang, mobile-alternate, and AMP, not to RSS/Atom feed autodiscovery, which is one-way — and added that none of these annotations guarantee crawling, indexing, consolidation, traffic, feed subscriptions, or AI citations.

Change details

Scoped the reciprocal-pairing throughline to the three uses that require it (hreflang, mobile-alternate, AMP) and explicitly excluded RSS/Atom feed autodiscovery, which is one-way by design — fixed in the frontmatter tldr, the Advanced TL;DR, the throughline section, the ai-summary, the anti-patterns entry, and the checklist's final check.
Added that rel="alternate" annotations don't guarantee crawling, indexing, consolidation, rankings, traffic, feed subscriptions, or AI citations — they're hints, not directives.

Full comparison unavailable — no prior snapshot was archived for this revision.

rel="alternate": What It Does and When to Use It

What rel="alternate" is

The one you’ll actually use: hreflang

The thing to understand

What rel="alternate" actually is

The four SEO uses (and one close cousin)

1. Hreflang — language/region alternates (current, most important)

2. RSS/Atom feed autodiscovery (current, niche)

3. Mobile-alternate (separate mobile URLs) — legacy

4. AMP’s rel="amphtml" — a related but distinct tag

Which of these still matter in 2026

The throughline: reciprocal pairing

Common mistakes

Bing and other engines

Where this sits

AI summary

Official documentation

Quotes from the source

Which rel="alternate" do I need — or do I need one at all?

rel="alternate" cheat sheet

What not to do with rel="alternate"

Reciprocal-pairing checklist

Confirm your rel="alternate" change actually took effect

Hreflang reciprocity after adding tags

Hreflang markup generation before you ship it

Mobile-alternate or AMP reciprocal canonical

Test yourself: rel=“alternate”

Resources worth your time

rel="alternate"

rel="alternate"

How this article chunks build baseline · local controls

Matching retrieval chunks

Flagged retrieval chunks

Matching retrieval chunks

Flagged retrieval chunks

Google Trends rel alternate

Books Ngram rel alternate · link rel alternate

Changelog

Updated Jul 25, 2026.

Summary

Change details

Updated Jul 18, 2026.

Summary

Change details

People also ask

What `rel="alternate"` is

What `rel="alternate"` actually is

4. AMP’s `rel="amphtml"` — a related but distinct tag

Which `rel="alternate"` do I need — or do I need one at all?

`rel="alternate"` cheat sheet

What not to do with `rel="alternate"`

Confirm your `rel="alternate"` change actually took effect