“Alternate page with proper canonical tag” is the one status in the Page indexing report that usually means everything is working. The page was excluded because it declares a canonical pointing elsewhere, and Google honoured that declaration.
In other words, you told Google to index a different URL instead, and it did. Most of the time no action is needed, and acting anyway causes harm.
Why this appears
Any setup that legitimately produces several URLs for one piece of content will generate this status in volume.
- Product variant URLs canonicalising to the main product.
- Filtered or sorted category URLs canonicalising to the base category.
- Tracking or campaign parameters on otherwise identical pages.
- Printer-friendly or AMP versions pointing at the standard page.
- Products reachable through several category paths, all canonicalising to one.
- Paginated pages canonicalising to page one, though that is not always correct.
Large counts here are normal on ecommerce sites and are not in themselves a problem.
When it is actually a problem
The status is only worth investigating when the canonical points somewhere it should not. That happens more often than people expect.
- A page you want indexed is canonicalising to something else, so it can never rank.
- Canonicals point at the homepage, a common template fault that removes whole sections from the index.
- Every page in a section canonicalises to that section’s landing page, collapsing genuinely distinct pages.
- Paginated pages canonicalise to page one, which can leave deeper items unreachable.
- The canonical target redirects or is itself excluded, which breaks the chain.
How to check
- Export the affected URLs and look at which target they declare, not just how many there are.
- Group by canonical target. One target receiving thousands of canonicals is a template fault.
- Use URL Inspection to compare the declared canonical with the one Google selected. They can differ.
- Spot-check pages you expect to rank, and confirm they are self-canonical.
- Verify canonical targets return 200 rather than redirecting.
The most useful single check is grouping by target. Correct canonicalisation produces many targets with few pages each; a fault produces one target with an implausible number.
Fixing genuine faults
- Make pages that should rank self-canonical.
- Correct templates that hardcode a canonical rather than generating it per page.
- Point canonicals at final URLs, never at URLs that redirect.
- Ensure internal links use the canonical form, since conflicting links weaken the declaration.
- Leave correct canonicalisation alone, even where the count is large.
Frequently asked questions
Should I worry about thousands of these?
Not by itself. On an ecommerce site with variants and filters it is expected. What matters is whether the canonical targets are correct, which you check by grouping rather than by counting.
Why is Google ignoring my canonical?
Canonicals are a signal, not an instruction. Google may select a different URL where internal links, sitemaps or redirects contradict the declaration. Make every signal agree and it will usually be honoured.
Should paginated pages canonicalise to page one?
Generally not. Each paginated page is genuinely different content and should be self-canonical, so items on deeper pages remain discoverable. See pagination SEO issues.
Does this status affect rankings?
Not when it is correct, which is most of the time. It is consolidating signals onto the canonical URL, which is the intended behaviour. It only harms you when the target is wrong.
Consulting CTA
If pages you expect to rank are being excluded by canonical declarations, book an SEO consultation for a canonical and indexation review.