Alternate Page With Proper Canonical Tag

What 'alternate page with proper canonical tag' means

Google's own definition of this Page indexing report status reads: "This page is marked as an alternate of another page and correctly points to the canonical page." In plain terms, the flagged page carries a rel=canonical tag that points to a different URL, Google has accepted that declaration, and that other URL is the one being indexed. Google deliberately does not index the alternate page itself, because the alternate has told Google, correctly, that it is not the version meant to appear in search results.

This status is informational rather than an error classification. It exists to tell you that Google understood and honored your canonicalization signal, not that something is broken. That distinction matters, because in a list of Page indexing statuses it sits alongside labels that do describe real problems, and it is easy to assume every entry in that report needs action.

Why this status is usually good news, not an error

When a page is correctly marked as an alternate with a proper canonical tag, the mechanism is working exactly as intended: the alternate page exists for a legitimate reason, its rel=canonical tag names the right target, Google reads that tag, and Google keeps only the canonical version in its index rather than showing duplicate content twice. That is the entire point of the canonical tag.

Large numbers under this status are normal, and often a sign of healthy site architecture rather than a warning sign. A site with faceted navigation, print-friendly pages, or many language variants can easily accumulate thousands of alternate URLs, each correctly canonicalizing to the page it should. Seeing that count grow is not, by itself, evidence of a problem; it is evidence that a lot of duplicate or near-duplicate URLs exist and that they are all pointing where they should.

The normal cases that land here

Several everyday patterns generate this status without indicating any issue.

• Parameter and faceted URLs. Sort orders, filters, and tracking parameters create additional URLs for what is effectively the same content; each correctly canonicalizes back to the clean version of the page.
• Print and mobile variants. Print-friendly versions, along with AMP or separate m. mobile URLs, exist as alternates of a primary page and correctly point their canonical tag at it.
• Hreflang alternates. In an international setup, language and regional variants of a page are legitimate alternates within an hreflang cluster; when they carry proper canonical tags, this status simply confirms the relationship is set up correctly.
• Cross-domain syndicated copies. When content is syndicated to another domain and that copy correctly canonicalizes back to the original, it shows here rather than being indexed as a separate duplicate.

When it actually IS a problem

The status stops being good news in a few specific situations, and all of them share the same shape: a page that should be indexed on its own is instead deferring, via its canonical tag, to a different URL.

• A page you want indexed independently is wrongly grouped as an alternate. This happens when a canonical tag is misconfigured, pointing at a similar but distinct page rather than at itself, so a page with content worth ranking never gets indexed.
• A template bug canonicalizes many unique pages to one URL. If a shared template or content management system default writes the same canonical target into every page that uses it, dozens or hundreds of genuinely different pages can end up pointing at a single URL, none of them getting indexed under their own address.
• All paginated pages canonicalize to page one. When every page in a paginated series points its canonical tag at the first page, the unique content on pages two, three, and beyond is effectively removed from the index, even though it differs from what is on page one.

How to check the flagged pages

Two habits separate genuine mistakes from normal, healthy alternates.

Use the URL Inspection tool on individual flagged URLs to confirm what canonical target each one declares and whether that target makes sense for that specific page. A page whose canonical points to a URL with substantially different content is the clearest sign something is wrong.

Just as important, look for patterns rather than treating each flagged URL as an isolated case. If the pages showing this status all belong to one template, one content type, or one section of the site, and they all canonicalize to the same target, that pattern points to a systemic template bug rather than individually mistaken pages. Spotting the pattern is usually faster than inspecting URLs one at a time, and it is the difference between fixing one page and fixing an entire class of pages.

What to do (usually nothing — and how to fix genuine mistakes)

If the pages under review are legitimate parameter variants, print or mobile alternates, hreflang alternates, or syndicated copies, and each canonical tag points where it should, no action is needed. This is the report confirming your canonicalization is working.

A correct self-referencing canonical, for comparison, on the canonical page itself looks like this:

<link rel="canonical" href="https://www.example.com/page.html">

For a genuine alternate, the tag instead points away from itself, at the canonical page it defers to.

Where a page has been wrongly grouped as an alternate, the fix is to correct its rel=canonical tag: either make it self-referencing, if the page should be indexed independently, or repoint it at the correct canonical target if it was pointing at the wrong URL. For a template-level bug, the fix belongs in the template or the system generating the tag, not on individual pages, since correcting one page at a time will not resolve a default that is being applied sitewide. For paginated series wrongly collapsing to page one, each page in the series should carry its own self-referencing canonical rather than deferring to the first page, since Google has stated that canonicalizing all paginated pages to page one is a mistake to avoid.

Frequently Asked Questions