Should you really use rel-alternate to link your AMP pages to their canonical version?

Why does Google require this tag for AMP?

AMP technically creates a distinct URL from your standard page. Google crawls and indexes both versions as separate entities. The rel-alternate tag allows the engine to understand that these are two variants of the same content, not duplication.

This directive works in tandem: the standard canonical page points to the AMP via rel-amphtml, while the AMP page links back to the canonical via rel-canonical. This two-way double link is essential for Google to correctly consolidate signals.

What happens if this tag is absent?

Google treats the two versions as unrelated pages. You then fragment your ranking signals across two URLs. The engine might index one or the other randomly, with no guarantee on which will appear in the SERP.

Backlinks, load time, user engagement: all these signals disperse instead of concentrating on your main page. You essentially create self-inflicted cannibalization of your own content.

Does this requirement still apply with the decline of AMP?

AMP has lost its status as a preferred ranking criterion for news. Google has abandoned the lightning badge and no longer mandates AMP to appear in Top Stories. Many sites have removed their AMP versions with no measurable negative impact.

But if you still maintain AMP—due to technical inertia or specific mobile strategy—this directive remains mandatory. Google has never removed this technical requirement, even though the framework has lost its strategic importance.

• The rel-alternate tag is mandatory to establish the link between AMP and canonical pages
• Without it, Google treats the two versions as distinct pages without relation
• The two-way double link (rel-amphtml + rel-canonical) must be present on both pages
• This technical requirement remains valid despite the strategic decline of AMP
• The absence of this tag fragments your ranking signals between two URLs

Does this directive reflect what we observe in the field?

Yes, and it’s verifiable. Technical audits show that poorly linked AMP pages indeed create indexing issues. Search Console raises explicit alerts when the double link is absent or malformed.

It is also observed that Google favors the canonical version when the two-way link is clean. Without rel-alternate, the engine sometimes indexes the AMP version as primary, leading to inconsistencies in SERPs and fragmented Analytics reports.

What nuances should we consider regarding this statement from Mueller?

Mueller fails to mention a crucial point: many sites no longer need AMP. This directive is technical, but the real strategic question lies elsewhere. Since Google removed the AMP advantage for news, maintaining these dual versions creates more complexity than benefit.

Core Web Vitals and good responsiveness are now sufficient. If your standard site displays good mobile performance, AMP brings nothing. And if you maintain it solely for historical reasons, you are creating technical debt that requires ongoing maintenance and monitoring.

In what cases does this rule become obsolete?

If you completely remove AMP from your infrastructure, this directive is obviously no longer applicable. But the transition must be managed: do not leave old AMP URLs as 404, do not abruptly cut the link without redirects.

Some sites keep AMP for newsletters or specific syndicated feeds. In these niche cases, the tag remains necessary. But for 90% of standard sites, the real recommendation would be to get rid of AMP rather than struggle to properly maintain these tags.

What should you concretely do if you still maintain AMP?

Check that each AMP page has a link rel="canonical" tag pointing to the standard version. Conversely, ensure that the canonical page includes a link rel="amphtml" tag to the corresponding AMP. This double link must be present on 100% of pairs.

Use Search Console to identify AMP errors. Google explicitly highlights canonical linking issues in the AMP section of the Coverage report. If AMP URLs appear without a link to the canonical, correct it immediately.

How can you verify that your implementation is correct?

Crawl your site with Screaming Frog or Sitebulb while enabling AMP mode. The tool will detect AMP pages without rel-canonical or standard pages without rel-amphtml. Export the list and prioritize correcting high-traffic pages.

Manually test a few URLs using Google’s AMP test tool. It will alert you if the two-way link is broken. This is quick and avoids deploying a fix blindly without validation.

Is it true that you should keep AMP or migrate to a fully responsive site?

Let’s be honest: most sites no longer need AMP. If your mobile Core Web Vitals are good, and your responsive loads in under 2 seconds, you gain nothing by maintaining a dual infrastructure. Compare your actual metrics before deciding.

If you decide to abandon AMP, plan a clean migration: 301 redirects from all AMP URLs to the canonical ones, updating sitemaps, monitoring indexing for at least 3 months. It is a significant technical undertaking, but it sustainably simplifies your stack.

• Audit all standard page / AMP page pairs to verify the presence of the double link
• Monitor the Search Console AMP section for canonical linking errors
• Crawl the site with a tool that detects poorly linked AMPs
• Compare standard mobile Core Web Vitals vs real AMP benefits
• If migrating away from AMP: set up 301 redirects and monitor indexing for 6 months
• Manually test a few URLs using Google’s AMP test tool