Alternate Page with Proper Canonical Tag (GSC): What It Means + How to Fix It

Before you change anything: this status is usually Google doing exactly what you asked. The page has a rel="canonical" pointing at a different URL, Google read it, agreed, and indexed the canonical instead of this one. That's the entire mechanism — and most of the time, it's the correct outcome.

So unlike most things in the Pages report, this one often needs no fix at all. The job here is narrower: confirm the canonicals are pointing where you meant them to, and catch the handful of pages that landed in this bucket by accident.

When this status is working perfectly

If you deliberately set canonicals to fold variant URLs into one clean page, seeing them here is the receipt that it worked. These all belong in this bucket:

• Tracking and parameter URLs — ?ref=ads, ?utm_source=…, ?fbclid=… all canonicalizing to the clean URL.
• Faceted and filtered pages — /shoes?color=black&sort=price pointing back to /shoes.
• Paginated pages — page 2, 3, 4 of a series canonicalizing to the main page (or to themselves, if you index each).
• Mobile or AMP variants — m.example.com or /amp/ pages pointing to the primary desktop URL.
• Trailing-slash, www, or http duplicates that resolve to one canonical form.

In every one of these, Google indexing the canonical and parking the variant here is the point. Don't touch it.

Spot the false alarm

The real work is finding pages that got swept in here by mistake. Two patterns cause almost all of them.

A page you wanted indexed is canonicalizing to a different page

Somewhere, a rel="canonical" is pointing this page at a URL that isn't itself. The page can't rank because you've quietly told Google not to index it. The usual culprits:

• A hardcoded canonical in a template that stamps every page with the same URL — often the homepage or one flagship post.
• A CMS or SEO plugin auto-generating canonicals and pointing a whole section at the wrong parent.
• A copy-pasted canonical left over from duplicating a page, still aimed at the original.

Tell: a page you'd expect to rank is sitting in this bucket, and the canonical URL it reports is not its own address.

The canonical points to a dead or blocked page

Even a deliberate canonical breaks if its target can't be indexed — pointing at a URL that's noindex, 404s, or redirects elsewhere. Google may honor the canonical and then fail to index anything useful, or fall back and pick its own.

Tell: the declared canonical resolves to a page that returns an error, redirects, or carries a noindex.

Confirm intent with URL Inspection

Don't guess from the URL alone — check what Google actually read. Open URL Inspection on the affected page and look at the Page indexing section. It shows two lines that settle it:

• User-declared canonical — the canonical you (or your platform) put on the page.
• Google-selected canonical — the URL Google chose to index.

Read it like this:

• User-declared canonical = the URL you intended → working as designed. Leave it.
• User-declared canonical = some other page you didn't mean → you found a misconfiguration. Fix the canonical (below).
• No user-declared canonical, and Google picked one anyway → you're really looking at Duplicate without user-selected canonical, not this status.
• You declared one, but Google ignored it and chose differently → that's Google chose a different canonical than the user — a credibility problem, not a tag problem.

Fixing the misconfigured cases

Only the false-alarm pages need this. For a variant that belongs here, skip it.

1. Make the page self-reference

   For a page you want indexed (the first false alarm), the canonical should point to its own URL:

   <link rel="canonical" href="https://example.com/this-exact-page" />
   

   Find where the wrong value comes from — a global template, a plugin setting, or a stray hardcoded tag — and fix it at the source, not page by page. One wrong template line can mislabel hundreds of URLs.

2. Repair a canonical that points to a dead target

   If the canonical aims at a noindex, 404, or redirected URL, repoint it to a page that actually returns 200 and is indexable — or remove the bad canonical so the page self-references. A canonical to an un-indexable page is worse than none.

3. Keep internal links on the canonical URL

   Link to the clean canonical, never the parameter or variant version. Mixed internal signals — half your links to /product, half to /product?ref=x — make Google second-guess which URL is primary, which is how deliberate canonicals start drifting.

4. Re-inspect, then request indexing

   Once the canonical is corrected, run URL Inspection again, confirm the user-declared canonical now reads as you intend, and click Request indexing. Re-evaluation takes days to weeks; submitting repeatedly does nothing.

Don't confuse it with these neighbors

The line that sets this apart: Google honored a canonical you (or your platform) declared. The only question worth asking is whether that canonical points where you meant it to.