AMP Canonical Points to a Canonicalized URL: How to Fix It

What this check flags

An AMP document is required to declare a canonical. Normally that canonical points back to the standard (non-AMP) version of the same page, and that standard page carries a self-referencing canonical. The chain ends in one hop, and search engines know which URL to index.

This audit issue fires when the URL your AMP page names as canonical is not the end of the line. The AMP page points at URL B, but URL B has its own canonical pointing to URL C. So you have a chain: AMP to B, B to C. The AMP page is canonicalizing to an intermediate URL rather than the true, final canonical.

The canonical-chain problem in an AMP context

A canonical chain is already a known headache on standard pages. Google treats rel=canonical as a strong hint, not a command, and when one canonical points to another it has to decide how far to follow the trail and which URL deserves indexing. Chains dilute that signal.

AMP makes it worse because the AMP URL is not the page you want indexed in the first place. The AMP document is a mobile-fast alternate; the canonical is the mechanism that tells Google "do not index me, index that page instead." If "that page" then says "actually, index this other page," you have stacked two redirections of indexing intent on top of each other. That is a confused and conflicting message, and it raises the odds the AMP pairing is ignored or the wrong URL is surfaced.

Why the AMP canonical must point to the final canonical

Google's guidance is that the AMP canonical should point to the non-AMP version, and that target must be indexable. "Indexable" is the operative word. A URL that is itself canonicalized to somewhere else is, in practical terms, not the indexable destination, because its own markup is telling Google to prefer a different URL. So your AMP page is canonicalizing to a non-indexable target, which is the same family of problem as pointing at a noindex or a redirected URL.

The rule is simple: the AMP canonical should land on the URL that has a self-referencing canonical. That URL is the one Google intends to index, and it is where the pairing is supposed to terminate. One hop, no chain.

How to fix it

First, find the true final canonical. Open the URL your AMP page currently points to and read its canonical tag. Whatever that resolves to (after following any further hops) is your real target. Then update the AMP page so its canonical points there directly.

In the AMP document head you want:

<!-- On the AMP page (e.g. /article/amp/) -->
<link rel="canonical" href="https://seoprocheck.com/article/">

And on that standard page, confirm it canonicalizes to itself and links back to the AMP version:

<!-- On the standard page (/article/) -->
<link rel="canonical" href="https://seoprocheck.com/article/">
<link rel="amphtml" href="https://seoprocheck.com/article/amp/">

The two pages now reference each other cleanly, and the canonical chain ends in one hop. On WordPress, this pairing is usually generated by your AMP plugin and your SEO plugin together, so the chain almost always comes from a misconfiguration in one of them rather than hand-coded tags. Check that both plugins agree on the same final URL.

How to diagnose it

Walk the chain by hand. Request the AMP URL and note its canonical. Request that canonical and note its canonical. If the second canonical differs from its own URL, you have found the chain. Keep following until you reach a URL whose canonical equals itself; that is your final target.

You can pull canonical and amphtml tags quickly from the command line:

curl -sL https://seoprocheck.com/article/amp/ \
  | grep -iE 'rel="(canonical|amphtml)"'

In Search Console, the URL Inspection tool reports the Google-selected canonical for a given URL, which tells you where Google actually thinks the chain ends. Compare that against your declared tags to confirm the fix landed.

Common mistakes

Pointing the AMP canonical at a paginated or tracking-parameter version that then canonicalizes to the clean one. Mixing http and https or www and non-www, so the first canonical is a different host that canonicalizes onward. Letting two plugins each inject a canonical, so the AMP page and the standard page disagree on the final URL. And the classic: pointing at a trailing-slash variant when your site canonicalizes to the non-slash form (or the reverse).

FAQ