Alternate Page With Proper Canonical Tag: Fine, or a Warning?

Alternate page with proper canonical tag is a Page Indexing status in Google Search Console meaning the URL points to another page as its canonical, Google agreed, and the canonical page is indexed. Google’s own guidance is that there is nothing to do. That is true for each URL in the bucket. It is not always true of the bucket as a whole, and three quick checks tell you which situation you are in.

What Google actually says

From the Page Indexing report help page, checked on 2 October 2026:

This page is marked as an alternate of another page (that is, an AMP page with a desktop canonical, or a mobile version of a desktop canonical, or the desktop version of a mobile canonical). This page correctly points to the canonical page, which is indexed, so there is nothing you need to do.
Google Search Console Help, Page Indexing report

The examples in that definition are all format variants: AMP, mobile and desktop. On most sites today the bucket is filled by something else, because any URL that declares a different canonical and has that declaration accepted can be reported this way. Parameter variants, tracking URLs, sort orders and print versions are the usual residents. The status still means the same thing, a working canonical, but the reason those URLs exist is a different question.

The help page also files the whole “Why pages aren’t indexed” section as pages that “have not been indexed, but not necessarily because of an error”. This status is the clearest case of that. It is Google confirming that your canonical tags are being honoured, which is the opposite of the problem described in why Google ignores your canonical.

How it differs from the two duplicate statuses

Status	Did you declare a canonical?	Did Google agree?	Which URL is indexed
Alternate page with proper canonical tag	Yes, pointing elsewhere	Yes	The canonical you declared
Duplicate, Google chose different canonical than user	Yes, pointing at itself	No	Another URL Google preferred
Duplicate without user-selected canonical	No	Google chose for you	Another URL Google preferred, see the duplicate triage

Google’s definitions for the other two, from the same page: a duplicate without a user-selected canonical “doesn’t indicate a preferred canonical page. Google has chosen the other page as the canonical for this page, and so will not serve this page in Search.” And when Google chose a different canonical than you, “Google thinks another URL makes a better canonical. Google has indexed the page that we consider canonical rather than this one.” Only the alternate status means you and Google are in agreement.

Three checks that decide whether to act

For a sample of URLs in the bucket, ask three yes or no questions. The answers combine into eight cases. Only one of them is the “nothing to do” that the help page describes, and one more is harmless but wasteful. The other six need work.

Check 1: is the declared canonical indexed and returning 200? The definition assumes it is. If the canonical target is itself redirected, noindexed or blocked, the agreement is pointing at a page that cannot rank.
Check 2: was this URL meant to rank on its own? A distinct product, a distinct article or a separate language version should not be an alternate of anything.
Check 3: is this URL linked from your own pages? A canonical tag consolidates signals, but every internal link to an alternate still sends crawlers and users to the wrong address.

Canonical target indexed?	Meant to rank alone?	Linked internally?	Verdict	Action
Yes	No	No	Working as intended	Nothing
Yes	No	Yes	Working, but wasteful	Point internal links at the canonical URL
Yes	Yes	No	Wrong canonical	Make the page self-canonical and link to it
Yes	Yes	Yes	Wrong canonical, and visible	Fix the canonical first; this is the case most likely to be costing traffic
No	No	No	Broken target	Fix the canonical target, or point the tag at a live equivalent
No	No	Yes	Broken target, linked	Fix the target, then repoint links
No	Yes	No	Two faults	Make the page self-canonical; fix or retire the target
No	Yes	Yes	Highest priority	Self-canonical, then audit why the template declared it

Check 1 sounds redundant given the definition says the canonical “is indexed”. It is worth running anyway, because the report is a snapshot and canonical targets change: a product gets discontinued and redirected, a page gets noindexed in a cleanup, and the alternates keep pointing at it until the template is updated.

What a canonical does and does not do

Google’s guide to consolidating duplicate URLs ranks the methods by strength. Redirects are “a strong signal that the target of the redirect should become canonical”. A rel=”canonical” link annotation is “a strong signal that the specified URL should become canonical”. Sitemap inclusion is “a weak signal”. Two warnings sit alongside that list: “Don’t use the robots.txt file for canonicalization purposes”, and don’t use the URL removal tool either, because it “hides all versions of a URL from Search.”

What a canonical does not do is stop the alternate being crawled. Google has to fetch the alternate to read the tag on it. So a site generating ten alternates for every canonical page is asking Googlebot to fetch ten URLs to learn one thing. That is harmless on a small site and a measurable cost on a large one, which is why the second row of the table above matters and why faceted navigation is where this bucket usually explodes. The arithmetic of what that costs is in index bloat.

Language versions are not alternates in this sense

One case belongs to row three of the table more often than teams expect. Translated or regional versions of a page are not duplicates, and Google’s consolidation guide says that when using hreflang you should “specify a canonical page in the same language, or the best possible substitute language if a canonical page doesn’t exist.” A French page that declares the English page as its canonical is telling Google the English page is the one to index, so it is likely to be reported as an alternate rather than indexed in its own right. If your localised URLs appear in this bucket, that is a fault, covered in international SEO.

The audit, in order

Export the status and group the example URLs by pattern: parameters, tracking codes, paths, subdomains, language folders.
For each pattern, inspect three to five URLs with URL Inspection and confirm the declared canonical and the Google-selected canonical match.
Run Check 1 on the canonical targets: 200 status, indexable, not blocked.
Run Check 2: flag any pattern that contains pages meant to rank, especially language versions.
Run Check 3 with a crawl of your own site: count internal links pointing at alternate URLs.
Fix in order of the table: highest priority rows first, wasteful links last.

If this status is growing at the same time as traffic is falling, the canonical tags are probably not the cause, since they are working. Look at what is generating the new URLs, and start with the diagnosis in Google penalty recovery.

Alternate Page With Proper Canonical Tag: When Google’s “Nothing to Do” Is True, and the Three Checks That Say Otherwise