Why does Google require a canonical on ALL AMP pages, including standalone ones?

Why is a canonical necessary on a standalone AMP page?

The logic behind this requirement is based on a simple technical principle: Google treats AMP pages as distinct entities, even if they are standalone. Without a canonical, the engine cannot definitively determine which URL should be regarded as the reference version.

For AMP pages connected to a traditional HTML version, the canonical points to the HTML. For standalone AMPs, the canonical must point to the page itself. This mechanism prevents Google from hesitating between multiple candidate URLs and diluting ranking signals.

Does this rule apply to all types of AMP?

Yes, without distinction. Whether you are working on news articles, e-commerce product sheets in AMP, or standalone landing pages, the canonical is mandatory. Google makes no exceptions based on industry or content type.

The confusion often comes from associating AMP with news. However, Google has extended the use of AMP far beyond news articles — the canonical rule follows this expansion, regardless of the context of use.

What technically happens if the canonical is missing?

Google can refuse to index the AMP page or create an unintentional duplicate. In the best-case scenario, the page will be indexed but may compete with other URLs on your site. In the worst, it will simply be ignored.

The AMP diagnostic tools actually flag the absence of a canonical as a blocking error. Search Console will highlight this type of issue in the section dedicated to AMP pages, with an explicit mention: “missing canonical tag”.

• Mandatory for all AMP pages, whether connected to an HTML version or standalone.
• For a standalone AMP page, the canonical points to itself (self-referencing).
• Absence of a canonical = risk of partial indexing or internal duplicate content.
• Verifiable through Search Console, AMP section, and via AMP validation tools.
• This Google directive tolerates no exceptions based on industry or content type.

Is this statement consistent with observed practices in the field?

Completely. The technical audits I conduct regularly show that the absence of a canonical on standalone AMPs triggers error signals in Search Console. Google does not joke around with this rule — it is applied systematically.

Some developers still believe that a standalone AMP does not need a canonical because there is only one version. This is a logical error: Google wants explicit confirmation, even if it seems redundant. The engine does not “guess” — it expects a clear tag.

Are there cases where this rule is problematic?

Yes, particularly on sites that dynamically generate thousands of AMP pages. Forgetting to template the self-referencing canonical can cause massive indexing issues. I’ve seen sites lose 30% of their indexed AMP pages due to this type of oversight after a migration.

Another common case: multilingual or multi-domain sites. If you have AMP versions in multiple languages, each version must have its own canonical pointing to itself — not to a “master” version in another language. Google demands strict self-referencing, no shortcuts.

What nuance should be applied to this directive?

Google does not always clarify what happens in the case of a conflicting canonical. For example, if your standalone AMP page points to a non-existent HTML URL, Google may ignore it or treat it as a deferred 404 error. [To be verified] in each specific context.

Another point: Mueller says nothing about the performance impacts of a misconfigured canonical. We know that a canonical pointing to a slow or poorly optimized page can degrade overall signals — but Google remains vague on the exact weighting of these signals in AMP ranking.

What practical steps should be taken on an AMP site?

Start by auditing all your AMP pages to check for the presence of a canonical. Use a crawler like Screaming Frog or OnCrawl with a filter on AMP URLs, and export the “canonical” column. Each row should have a value — no empty fields.

For standalone AMPs, ensure that the canonical points to the AMP URL itself. If you have AMP pages connected to HTML, make sure the canonical correctly points to the corresponding HTML version. No approximations allowed.

What errors to avoid during implementation?

Do not confuse canonical with amphtml. The `` tag in the HTML version points to the AMP, while the canonical in the AMP points to HTML (or to itself if standalone). These two tags must coexist symmetrically.

Another common pitfall: using a relative canonical instead of an absolute one. Google recommends absolute URLs to avoid any ambiguity. A canonical of the type `/article-amp/` instead of `https://example.com/article-amp/` can create interpretation issues.

How to verify my site is compliant after implementation?

Run all your AMP pages through the official AMP validator from Google. A valid page without a canonical will not pass validation — it’s a clear signal. Then, monitor Search Console to ensure there are no issues flagged as “missing canonical”.

Also, run real-time indexing tests using the URL Inspection tool from Search Console. If Google correctly indexes the page with the right canonical, you’ll see the detected canonical URL match your implementation. If not, correct it immediately.

• Audit all AMP pages with a crawler to detect missing canonical tags.
• Check that standalone AMPs have a self-referencing canonical (pointing to themselves).
• Ensure that connected AMPs point to the HTML version via canonical.
• Use absolute URLs in canonical tags, never relative paths.
• Validate each AMP page with Google’s official validator.
• Monitor Search Console for AMP canonical errors.