How to Fix “Alternate Page with Proper Canonical Tag” in GSC
On this page
This status isn’t an error, and for deliberate duplicates there is nothing to fix. Google’s help for the Page indexing report describes it as a page marked as an alternate of another page, such as an AMP page with a desktop canonical or a mobile version of a desktop canonical, that correctly points to the canonical page, which is indexed, “so there is nothing you need to do.” Two real problems can hide in this report: a page you want indexed has landed here because its canonical points the wrong way, or the size of the report is distracting you from a separate decline elsewhere. The work is auditing the architecture behind a sample of these URLs, not “fixing” the status.
What the status means
The report lists these URLs as not indexed, and that label can trigger unnecessary panic. Read it as not indexed by design. Google crawled the alternate URL, found your rel="canonical" pointing to a different URL, and the canonical target is the one in the index. That is duplicate handling working as intended: parameter and tracking variants, print versions, AMP and mobile alternates, and any deliberate duplicate where you nominated one preferred URL.
It is also the counterpart of “Duplicate without user-selected canonical.” There, the page doesn’t indicate a preferred canonical, and Google chose another page as the canonical itself. Here, you declared a canonical and the declared page is the indexed one. Anchor on that difference: declared and followed, versus undeclared and chosen by Google.
The check that matters
Pull a representative sample of the listed URLs and inspect them, rather than scrolling a count in the thousands. For each one, use URL Inspection to confirm that the Google-selected canonical matches the URL you intended to consolidate onto. Where it does, leave the page alone. A large number here on a big catalog with extensive parameter variants is not in itself a problem.
You act only when inspection shows that a page with unique content you wanted indexed is being consolidated into something else. That is a misrouted canonical, and the fix is to correct the tag so the page either points to itself or to the right target. The skill is separating deliberate duplicates (leave them) from accidental casualties (fix them).
Sampling works when these URLs come in batches by cause. Parameter and tracking URLs share a pattern, and one misconfigured template produces a consistent batch of identically wrong canonicals. So you don’t need to inspect ten thousand rows. Inspect a handful from each apparent group and name the pattern behind it. Once you know a group is, say, tracking-parameter copies pointing to the clean URL, you can set the whole group aside. One group to fix rather than set aside is paginated pages that point their canonical at page one. Google’s guide to pagination says not to use the first page of a paginated sequence as the canonical, and to give each page its own canonical URL. Once you find a group of real content pages pointing somewhere unexpected, you may have found a template bug, and fixing it at the source corrects every page it affects at once.
When the count masks a real problem
A large entry in this report can sit alongside a traffic decline that has nothing to do with canonicals. If organic traffic is sliding, don’t assume this report is the cause. Investigate the decline on its own terms: which money or content pages lost rankings, and why. Treat this report as a separate, mostly benign stream of data. The two can coexist, and blaming an expected status wastes the time you have to find the real cause.
Canonical or noindex: one decision
Use a canonical when a true duplicate has a clear preferred equivalent: two URLs serving the same content, where you want signals consolidated onto one. Use noindex when a page is thin and has no equivalent to fold into, such as a thin author archive that isn’t a copy of anything you want indexed. A canonical consolidates; noindex removes. Equivalent duplicate gets a canonical, standalone thin page gets noindex.
Localized pages don’t belong here
The same help page adds a detail that changes how to read this report for international sites: alternate language pages are not detected by Search Console. So if a UK page or a regional variant shows up in this list, look at its canonical: it may be pointing to another market’s page, for example because a CMS default or a migration script set every regional variant to canonicalize to one master. The status looks healthy, and the UK version stays out of the index it was supposed to rank in.
The correct pattern is for each market variant to point its canonical at itself and to reference the other versions with reciprocal hreflang annotations. Google’s guide to consolidating duplicate URLs says that when you use hreflang, the canonical should be a page in the same language, or the best substitute language if none exists. A site crawler makes the audit quick: export the canonical and hreflang values for every localized URL and flag any market page whose canonical points to a different country.
How long fixes take
When you correct a misrouted canonical, or replace a cross-market canonical with a self-canonical plus hreflang, the change waits on recrawling. Google has to fetch the affected URLs again, read the new canonical and decide which version to index. Google’s guide to asking Google to recrawl says “Crawling can take anywhere from a few days to a few weeks.” Request indexing for high-priority pages, fix the template-level cause so the pattern stops, and let normal crawling carry the rest.
Set expectations for what “fixed” looks like. Corrected pages leave this list only when Google recrawls each one and reclassifies it, URL by URL, on Google’s schedule. Judge success by spot-checking the corrected pages in URL Inspection and confirming their Google-selected canonical now matches your intent. The aggregate count lags, and it includes plenty of pages that are supposed to stay there.
Frequently asked questions
Is “Alternate page with proper canonical tag” hurting my SEO?
By itself, no. Google’s help says a page in this state points correctly to an indexed canonical and there is nothing you need to do. It signals a problem only when a page you wanted indexed is here because its canonical points the wrong way. Inspect a sample; if the canonical targets are right, leave them.
Why are thousands of my pages in this report?
Large counts can be normal on sites with extensive parameter variants or deliberate duplicates. Volume isn’t severity. Inspect a sample from each group, and investigate further only if pages with unique content are being consolidated away.
Why is one of my country pages listed here?
Check its canonical. Google’s help says alternate language pages aren’t detected by Search Console, so a regional page in this list may be canonicalized to another market’s page. Give each market page a self-referencing canonical and reciprocal hreflang.