Key takeaways
- The GSC status 'Alternate page with proper canonical tag' is usually a signal of successful consolidation: Google found a duplicate/variant and accepted your canonical target
- This guide explains what it means, why it appears, when it's normal, and when it reveals URL noise that wastes crawl and slows visibility
Table of Contents
In Google Search Console, the status “Alternate page with proper canonical tag” is often a success signal, not a rejection: Google found a URL variant and agreed it should not be the canonical version.
If you want the full map of GSC states first:
TL;DR
- The page is not indexed because it is a variant, not because it "failed SEO".
- The system is telling you: "I see this URL, but I will store/rank the canonical target."
- It becomes a problem when the count is high and the variants are accidental (URL noise).
What this status actually means (system level)
Google is making two decisions at the same time:
- Are these URLs the same intent? (duplicate/near-duplicate)
- If yes, which URL is the canonical representative?
When you see this status, the typical interpretation is:
- Google crawled the alternate URL.
- Google saw a canonical on it (or inferred the canonical via site signals).
- Google accepted that canonical target as the representative.
- The alternate stays out of the index (by design).
This is a priority and consolidation decision, not a quality judgment.
When this status is normal (do nothing)
Common normal cases:
- URLs with
?utm_*parameters - printer-friendly views
- minor variants you intentionally canonicalize
- pagination where canonicals point to the main page (depends on strategy)
In these cases, the "fix" is not to index the alternate.
When it's a problem (accidental duplication)
It's a problem when alternates exist because of bugs or inconsistent routing:
wwwvs apex- trailing slash vs no slash
- query variants like
?m=1 - old feed endpoints (
/feed,/rss.xml, etc.)
If you see lots of alternates, you'll also see:
- Duplicate without user-selected canonical
- "crawled/discovered not indexed" growing due to crawl debt
At scale, this status is a symptom of URL noise: the crawler keeps discovering variants, and the system keeps spending cycles deciding they are not the representative.
The only checks that matter
Don't "fix the status". Fix the pattern that creates alternates.
1) Confirm the canonical target is the one you actually want
The canonical URL should:
- return 200 OK
- not redirect
- be the URL you want to rank
2) Consolidate accidental alternates with redirects
If the alternate is accidental, 301 it to the canonical. Goal: one content page -> one indexable URL.
3) Reduce parameter noise
If parameters create duplicates, pick a strategy:
- strip params via redirects (best for junk params)
- keep params but canonicalize them to the clean URL
If you're unsure which mechanism to use (canonical vs redirect), use:
4) Validate in GSC
In URL Inspection, you want this pair to converge:
- user-declared canonical = your preferred URL
- google-selected canonical = the same URL
The alternate URL may remain "not indexed" — that's expected.
If you're fighting indexing at the same time
Ambiguous canonicals often create "priority" problems because Google wastes crawl on duplicates, so new or important URLs get less attention. These posts explain the broader dynamic:
- Crawled - currently not indexed: what actually fixes it
- Discovered - currently not indexed: why it happens
- Google indexing explained
- Google chose different canonical: what it means
FAQ
Should I force the alternate URL to be indexed?
Usually no. You want one URL per intent. If you need both, they must be meaningfully different.
Is this status bad for SEO?
Not by itself. It's only bad if you have too many alternates and you don't control the pattern.
Next in SEO & Search
Up next:
Google chose a different canonical meaning (GSC): what it means (and the fastest fix checklist)“Google chose a different canonical” means Google-selected canonical differs from your user-declared canonical in GSC URL Inspection. This is rarely a penalty; it’s deduplication + conflicting signals. Here is the meaning, root causes, a 10-minute fix checklist, and how to validate.