How to Fix “Alternate Page with Proper Canonical Tag” in GSC

This status is not an error and most of the time there is nothing to fix. “Alternate page with proper canonical tag” means Google found a duplicate, read the canonical tag you placed on it, and correctly obeyed it by consolidating onto the URL you designated as preferred. Google is doing exactly what you told it to do. The only real problems are two: a page you actually want indexed has landed here because its canonical points the wrong way, or the report’s volume is distracting you from a separate quality decline happening elsewhere. The work is auditing the architecture behind a sample of these URLs, not “fixing” the status line.

What the status actually means

Search Console files this under “Excluded,” and that word triggers a lot of unnecessary panic. Read it as excluded-as-intended. Google crawled the alternate URL, saw a rel="canonical" pointing to a different URL, and chose to index the canonical target instead. That is the duplicate-handling system working. It is the expected outcome for pagination, parameter and tracking variants, print and AMP versions, and any deliberate duplicate where you nominated a single preferred URL.

It is also the precise inverse of “Duplicate without user-selected canonical.” There, you specified no canonical and Google had to guess which version to keep. Here, you supplied a canonical and Google is following it. If you conflate the two reports you will chase the wrong fix, so anchor on the difference: declared-and-obeyed versus undeclared-and-guessed.

The check that matters

Pull a representative sample of the flagged URLs and inspect them rather than scrolling a count in the thousands. For each one, use URL Inspection to confirm the Google-selected canonical matches the URL you intended to consolidate onto. In the overwhelming majority of cases it will, and the correct action is to leave those pages alone. The report is informational; a large number here on a big catalog or paginated archive is normal.

You only act when the inspection reveals that a page carrying genuine, unique content you wanted indexed is being canonicalized away to something else. That is a misrouted canonical, and the fix is to correct the tag so the page either self-canonicalizes or points to the right target. The skill is separating the deliberate duplicates (ignore) from the accidental casualties (fix), and a sampled URL Inspection pass is how you do it.

The reason sampling works is that this report tends to cluster by cause. Pagination variants land here together, parameter and tracking URLs land here together, and a single misconfigured template produces a consistent batch of identically-wrong canonicals. So you do not need to inspect ten thousand rows; you need to inspect a few from each apparent group and identify the pattern behind each cluster. Once you know a cluster is “page-two-and-beyond canonicalizing to page one as designed,” you can dismiss the whole group. Once you find a cluster of real content pages canonicalizing somewhere unexpected, you have found a template bug worth fixing at the source, which corrects every page it affects at once.

When the count masks a real problem

A large entry in this report can sit alongside a genuine traffic decline that has nothing to do with canonicals. The common case is thin aggregation: category, tag, author, and date-archive pages that hold no unique value and get correctly consolidated or judged low-quality. Those pages appearing here is fine. But if your organic traffic is sliding, do not assume this report is the cause. Investigate the decline on its own terms, looking at which money or content pages lost rankings and why, and treat the canonical report as a separate, mostly-benign data stream. The two can coexist, and treating an expected status as the culprit wastes the diagnostic window.

Canonical versus noindex, in one decision

Choose canonical when a true duplicate has a clear preferred equivalent: two URLs serving the same content where you want signals consolidated onto one. Choose noindex when a page is thin and has no canonical equivalent to fold into, such as an internal search results page or a low-value filter view that is not a duplicate of anything you want indexed. Canonical consolidates; noindex removes. The mechanics of the resulting noindex GSC status are their own topic, but the decision rule is that simple: equivalent duplicate gets a canonical, standalone thin page gets a noindex.

The expensive misuse: localized pages

The most damaging pattern that produces a legitimate “alternate page with proper canonical tag” entry is canonicalizing localized pages to one another. A site canonicalizes its UK page to its US page, or every regional variant to a single master, often because a CMS default or a migration script did it silently. Google obeys, the status looks perfectly healthy, and the UK version quietly disappears from the index it was supposed to rank in. Your international rankings die while every report reads green.

The correct pattern is the opposite. Each market variant should self-canonicalize and the pages should reference each other with reciprocal hreflang annotations, so Google understands they are equivalents for different audiences rather than duplicates to collapse. If you run multi-region or multi-language pages, this is the first thing to audit when you see them in this report, because it is the case where “proper canonical tag” is technically true and strategically catastrophic. A crawler such as Screaming Frog makes the audit fast: pull canonical and hreflang for every localized URL and flag any market page whose canonical points to a different country.

How long fixes take

When you do correct a misrouted canonical or replace a cross-language canonical with self-canonical plus hreflang, the change is recrawl-dependent. Google has to refetch the affected URLs, re-read the new canonical relationship, and re-evaluate which version to index. On a large site that plays out over weeks rather than days, and there is no button to force it. Submit corrected pages for inspection if they are high priority, fix the template-level cause so the pattern stops recurring, and let natural recrawl propagate the rest.

It is worth setting expectations on what “fixed” looks like in the report. The corrected pages will not vanish from the alternate-page list the moment you ship the change. They move when Google recrawls each one, reads the new canonical, and reclassifies it, and that happens URL by URL on Google’s schedule, not yours. So judge success by spot-checking individual corrected pages with URL Inspection and confirming their Google-selected canonical now matches what you intended, rather than watching the aggregate count, which lags and includes plenty of legitimately consolidated pages that are supposed to stay there. The count going down is a slow side effect; the canonical pointing correctly on the pages you cared about is the real result.

Frequently Asked Questions

Is “Alternate page with proper canonical tag” hurting my SEO?

By itself, no. It confirms Google is consolidating duplicates onto the URLs you chose, which is the intended behavior. It only signals harm if a page you wanted indexed appears here because of a misrouted canonical, most often a localized page canonicalized to another country. Audit a sample; if the canonical targets are correct, leave them.

Why are thousands of my pages in this report?

Large counts are normal on sites with heavy pagination, parameter variants, or many deliberate duplicates. Volume is not severity. Inspect a sample to confirm the canonicals point where you intended, and only investigate further if genuinely unique pages are being consolidated away.

Sources

Page Indexing report, Google Search Central: https://support.google.com/webmasters/answer/7440203

Consolidate duplicate URLs (canonicalization), Google Search Central: https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls