Is it true that Google indexes canonical AMP pages just like classic HTML?

What exactly is a standalone AMP page?

A standalone AMP page is a page that exists only in AMP format, with no equivalent classic HTML version. It points to itself via the rel="canonical" tag. This is different from a classic configuration where an HTML page points to an AMP variant via rel="amphtml".

In this case, Google has only one version to index: the AMP. Illyes' statement confirms that this page will be treated like any other HTML page for indexing. No special treatment, neither good nor bad.

Why is this clarification from Google important?

For years, the SEO ecosystem debated the potential ranking advantage of AMP pages. Google has always claimed that AMP is not a direct ranking factor, but the correlation between AMP and positions in Top Stories raised doubts.

This statement clears up any ambiguity for canonical AMPs: they are indexed as standard HTML. If your standalone AMP performs well, it's due to its speed, UX, and structure — not because it's AMP.

What’s the difference with a dual AMP configuration?

In a classic setup — HTML page + AMP variant — Google generally indexes the HTML version and uses AMP for accelerated display (especially in Top Stories until recently). The rel="amphtml" tag indicates the existence of the fast variant.

With a standalone AMP, there is no variant. The AMP page is the master page. Google indexes it directly, without following an alternative version logic. This is confirmed by Illyes: treatment identical to a normal HTML page.

• Standalone AMP = self-proclaimed canonical AMP page via rel="canonical" pointing to itself
• Identical indexing to a classic HTML page, with no bonus or penalty
• No intrinsic advantage linked to the AMP format for organic ranking
• Dual configuration (HTML + AMP) works differently: HTML is indexed, AMP serves as the fast variant
• Speed and UX remain factors — if the AMP performs, it's for these reasons, not for the format

Is this statement consistent with real-world observations?

Yes, overall. Sites that have migrated to standalone AMP (like some pure AMP media) do not show miraculous boosts in the classic SERPs. Their performance depends on standard criteria: authority, content, backlinks, Core Web Vitals.

However, the nuance missing here: Google does not specify if this equivalence also applies to indirect ranking signals. A fast AMP generates better user signals (bounce, dwell time), which can influence ranking. The indexing is identical, certainly — but the final impact may differ. [To be verified] on broad datasets with real performance data.

What pitfalls does this simplification hide?

Illyes talks about indexing, not crawl budget or prioritization. A poorly configured standalone AMP (validation errors, blocked resources) may be crawled less effectively than well-structured HTML. Indexing equivalence does not mean complete technical treatment equivalence.

Another point: this statement dates back to a time when AMP still had a privileged role in mobile Top Stories. Since Google opened Top Stories to non-AMP pages (if they meet Core Web Vitals), the strategic importance of standalone AMPs has diminished. Many sites have reversed course. The statement remains true, but its context of application has shrunk.

In what cases does this rule not apply?

If you have a dual setup (HTML + AMP), this statement does not directly concern you. Google indexes your HTML, not your AMP. The AMP serves as a fast variant, but it does not carry the canonical indexing.

If your standalone AMP contains critical validation errors, Google may refuse to index it correctly — exactly as it would with a broken HTML page. The equivalence of treatment is valid for technically sound pages. An invalid AMP will not receive leniency on the grounds that "it is treated like HTML."

What should you concretely do if you are using standalone AMP?

Make sure that your rel="canonical" tag points correctly to the AMP page itself, not to a non-existent HTML version. Check in Search Console that Google recognizes this page as canonical and that there are no conflicts with other URLs.

Regularly validate your AMP pages with the official tool. An invalid AMP page loses its AMP status and will be treated as a broken HTML page — potentially leading to poorer indexing. Treatment equivalence assumes strict technical compliance.

What mistakes should you absolutely avoid?

Do not create cannibalization between an HTML version and a standalone AMP version. If both exist without the correct rel markup, Google will not know which one to index and you risk authority dilution or mixed signals.

Avoid believing that standalone AMP exempts you from standard SEO best practices. Illyes says it is treated like normal HTML — so apply the same requirements: optimized title tags, coherent Hn structure, internal linking, structured data.

How can you check if your setup is correct?

Inspect the URL in the Search Console and check the "Coverage" tab to see which URL Google has retained as canonical. If it is not your AMP, there is a markup issue.

Use a Screaming Frog or Oncrawl crawl to identify AMP pages that point to an external canonical or that do not have a canonical tag at all. Prioritize fixing these anomalies.

• Ensure that rel="canonical" points to the AMP URL itself
• Validate all AMP pages with the official Google AMP tool
• Check in Search Console that the recognized canonical URL is indeed the AMP
• Apply classic SEO best practices: title tags, meta description, Hn, structured data
• Monitor Core Web Vitals: a slow AMP loses its main advantage
• Avoid any HTML/AMP duplication without correct rel markup