How should you correctly manage the canonical relationship between AMP and standard pages?

Why does Google maintain this distinction between main pages and AMP pages?

Google's logic is based on a simple principle: the standard page is the canonical source, the one that accumulates ranking signals. AMP is merely a technical variation, a mobile-optimized display format that inherits the authority of the main page.

In this architecture, the rel=canonical tag of the AMP page points to the standard page. This is the opposite of most canonical cases where the alternative version points to the main one. Here, Google consolidates signals on the standard page while reserving the right to display the AMP in mobile results.

What really happens during the indexing of these two versions?

Google treats the two URLs as distinct but linked entities. The standard page receives the PageRank, and backlinks count towards it, and it is the one that appears in the index as the official reference. The AMP page exists in parallel but does not dilute the signals from the main page.

Specifically, when a mobile user performs a search, Google may choose to display the AMP URL in the results (with the little lightning icon), but the ranking is still determined by the performance of the standard page. It's a substitution on the display side, not the evaluation side.

In what situations does Google display the AMP version instead of the standard one?

Google decides based on criteria that are not publicly detailed. Generally, AMPs appear in Top Stories carousels and on mobile when the query has a timely or informational urgency. On desktop, it's almost always the standard page that displays.

What complicates matters: Google has significantly reduced the visibility of AMPs since it removed the mandatory AMP carousel for Top Stories. The relevance of maintaining an AMP architecture has become questionable for many sites, except those heavily focused on breaking news.

• The standard page retains indexing priority: it accumulates authority and backlinks.
• The AMP rel=canonical points to the standard page, not the other way around.
• Google displays the AMP on mobile when it deems relevant, without affecting the ranking of the main page.
• Both versions coexist in the index, but only one has authority for SEO signals.
• The AMP architecture remains optional: many sites perform well without it now.

Does this statement align with what is observed in the field?

Yes, broadly speaking. Tests indeed show that backlinks pointing to an AMP page are redirected to the standard page for PageRank calculation. Google effectively consolidates signals on the canonical version. Crawl audits confirm that Googlebot treats the standard page as the primary reference.

However, the phrase "when relevant" remains vague. Google provides no measurable criteria to predict when the AMP will be displayed. This is frustrating for an SEO looking to precisely guide their traffic. Some sites see their AMPs disappear from mobile SERPs without explanation, even though the technical setup is correct. [To be verified]: the exact criteria for displaying AMPs on mobile remain opaque.

What nuances should be added to this official guideline?

Google does not mention cases where the canonical setup is broken. If an AMP page does not correctly point to its standard version, Google may treat both as independent duplicates, creating a signal dilution. This is a common issue on sites that hastily implemented AMP.

Another missing point: the impact on crawl budget. Maintaining two versions of each page mechanically doubles the number of URLs to crawl. For a site with thousands of pages, this can slow the discovery of important new pages. Google suggests this is not a problem, but logs show that Googlebot spends time on AMPs, time it does not spend elsewhere.

In what cases does this rule not apply or become counterproductive?

If your site is not a news medium, the AMP architecture probably adds more complexity than benefits. Core Web Vitals have become the true lever of mobile performance: a well-optimized standard page on these metrics performs just as well, if not better than, a poorly designed AMP.

For e-commerce or B2B sites, maintaining two HTML templates per page is a maintenance nightmare. AMPs limit interactive functionalities, which can harm user engagement. If Google does not consistently display your AMPs in SERPs, you maintain a dual architecture for no reason.

How to correctly implement the canonical relationship between AMP and standard?

On the standard page side, add a <link rel="amphtml" href="AMP_PAGE_URL"> tag in the <head>. On the AMP page side, insert <link rel="canonical" href="STANDARD_PAGE_URL">. Both URLs must be absolute, in HTTPS, and point exactly to each other.

Ensure that these tags are present in the source HTML, not added by JavaScript after loading. Google crawls the raw initial HTML, and if the tags are absent at that moment, the canonical relationship will not be detected. Test with a curl or fetch as Google to be sure.

What configuration errors cause indexing issues?

The classic error: the AMP page points to itself as canonical instead of pointing to the standard page. As a result, Google treats both versions as independent, and you end up with a duplicate that dilutes your signals. Search Console will notify you of excluded or indexed AMP pages that should not be.

Another common pitfall: UTM parameters or URL variations that break the canonical relationship. If your standard page is example.com/article and the AMP points to example.com/article?source=amp, Google may not recognize the relationship. The URLs must match exactly, even in casing.

How to check that Google has understood the configuration properly?

Use the URL inspection tool in Search Console to examine the AMP page. In the "Page Analysis" section, Google should indicate "Canonical page selected by user: [Your standard page URL]". If this is the case, the relationship is well detected.

For standard pages, ensure they are indexed normally and that Google is not replacing them with their AMP version in the main index. Perform a site:yourdomain.com [exact page title] search: the URL that appears should be the standard page, even if the snippet displays the AMP logo on mobile.

• Check that each AMP page contains a rel=canonical pointing to its standard version.
• Check that each standard page contains a rel=amphtml pointing to its AMP version.
• Use absolute HTTPS URLs in both tags.
• Test the source HTML before JavaScript rendering to confirm the presence of the tags.
• Verify in Search Console that Google has properly selected the standard page as canonical.
• Monitor logs for any excessive crawling of AMP pages impacting the budget.