Alternate page with proper canonical tag sits in the “not indexed” column of Search Console, and that placement causes needless worry. A growing count looks like pages falling out of Google. In most cases it is the opposite: the report is confirming that duplicate URLs are being handled exactly as you asked. The work is not in clearing the status but in checking that the right pages are in it.
What alternate page with proper canonical tag means
Google’s Page indexing report describes the status in one sentence: “This page correctly points to the canonical page, which is indexed.” Three things are true at once. The URL has a canonical declared. That canonical points to a different URL. And Google accepted the declaration and indexed the target.
The Rank Math knowledge base explains the outcome: Google “will simply exclude the duplicate version and index the main version.” Its verdict on what to do is equally plain: “This ideally means Google recognizes these canonicalized URLs correctly, and there is nothing you need to do on your part.”
How it compares with the other page-indexing statuses
The report mixes success and failure in one list, so it helps to sort the statuses by whether they call for action. This one belongs with the redirect status: both describe a URL that is out of the index because you deliberately sent Google elsewhere.
| Status | Google’s description | Usually needs action? |
|---|---|---|
| Alternate page with proper canonical tag | “This page correctly points to the canonical page, which is indexed.” | No, check periodically |
| Page with redirect | “This is a non-canonical URL that redirects to another page. As such, this URL will not be indexed.” | No, unless the target is wrong |
| Duplicate without user-selected canonical | “Google has chosen the other page as the canonical for this page.” | Check Google’s choice |
| Duplicate, Google chose different canonical than user | “Google has indexed the page that we consider canonical rather than this one.” | Yes, signals disagree |
If your URLs are in either of the two duplicate statuses instead, read duplicate without user-selected canonical or Google chose a different canonical. Those are the canonical problems. This status is where those problems end up once they are fixed.
Where these URLs come from
Most sites accumulate alternate URLs without anyone deciding to create them. The usual sources are worth knowing because they tell you whether a given row is expected.
- Parameter URLs. Tracking tags, sort orders and session IDs, such as
https://example.com/guide/?utm_source=newsletter, canonicalised to the clean URL. - AMP and other alternate versions. A second rendering of the same article that points back at the main page.
- Filtered pages. Category pages with colour, size or price filters applied, canonicalised to the unfiltered category.
All three are cases where the duplicate has to keep working for visitors but should not compete in search. That is exactly what a canonical is for. Our guide to duplicate content sets out the wider pattern, and URL structure covers how to stop generating avoidable variants at the source.
A large count is not, on its own, a sign of a messy site. An online shop with a handful of filters can generate far more filtered URLs than it has products, and every one of them that is canonicalised to its parent will show here. The number reflects how many variant URLs Google has found, not how many problems you have. What matters is the mix: a list dominated by parameters and filters is the system working, while a list with your core articles or product pages in it is not.
The alternate page with proper canonical tag fix, when there is one
The common advice stops at “nothing to do”, and for most rows that is right. It is not the whole story. Rank Math recommends reviewing the list periodically to “validate if these pages are meant to be canonicalized. Else, you might lose the potential traffic from the valuable pages that could have been indexed.”
That is the real risk. A canonical that is technically correct can still be strategically wrong. A template that sets every paginated page, every filtered view, or every product variant to canonicalise to a parent can quietly take pages out of search that had their own demand. Google will honour the instruction. It has no way of knowing you did not mean it.
This is why the status deserves a periodic look even though it is labelled correct. The word “proper” in the label describes the syntax and Google’s acceptance of it. It says nothing about whether the page should have been canonicalised. Search Console has no way to flag a valid canonical that costs you traffic, because from Google’s side nothing has gone wrong. The check has to come from you, and it is quickest when done against a list of the pages you know have demand.
To check, go to Pages, then Not indexed, then this status, and export the list.
- Group by pattern. Sort by URL path. Parameter and AMP rows are almost always fine and can be skipped.
- Look for clean URLs. A URL with no parameters in this list is the one to question. Ask whether it has its own search demand.
- Inspect the source. Open the page and check the canonical in the head. Make sure it is the one you intended and not a plugin default.
- Fix the template, not the row. If one setting created the problem, change the setting so new pages stop inheriting it.
For a page that deserves its own place in search, replace the cross-page canonical with a self-referencing one:
Then give the page enough unique content to stand alone, link to it internally, and use Validate fix in the report. Our guide to the canonical tag covers where plugins and templates most often set the wrong value.
What the count does and does not mean
The limitation is that the status confirms mechanics, not intent. It tells you Google followed your canonical; it cannot tell you whether you should have set it. A rising count after a launch or a migration may be perfectly healthy, as new parameter URLs are found and handled, or it may be a template error spreading across a section. Only a look at which URLs are in the list separates the two. Treat a sudden jump as a prompt to sample the rows, not as a fault in itself.
Frequently asked questions
Is alternate page with proper canonical tag an error?
No. It means the page points to its canonical and Google has indexed that canonical. In most cases there is nothing to fix.
Why is it listed under not indexed?
Because the alternate URL itself is not indexed; the canonical it points to is. Keeping duplicates out of the index is the intended result.
When should I act on this status?
When a page with its own search value appears in the list. That usually means a template or plugin set the canonical to another page by mistake.
Should I request indexing for these URLs?
No, unless you have changed the canonical to a self-referencing one. Otherwise Google will keep following the canonical you declared.
The takeaway This status is usually a receipt, not a warning. Skim it for clean URLs with their own demand, fix the template that canonicalised them, and leave the rest alone.
