You open the Page Indexing report in Search Console, see a few thousand URLs sitting under “Alternate page with proper canonical tag,” and immediately assume something is broken. It is filed under pages that are not indexed, after all. In the large majority of cases this status means the opposite of a problem — it means your canonical tags are being read and respected exactly as intended. But there is a specific set of circumstances where it does indicate something wrong, and telling the two apart takes about five minutes.
What the Status Actually Means
Google is telling you three things at once:
- It found this URL.
- The URL contains a canonical tag pointing at a different URL.
- Google agreed with that instruction and indexed the other URL instead.
That is canonicalisation working. You told Google which version of a set of duplicate or near-duplicate pages was authoritative, and Google indexed that one.
The confusion comes entirely from where the status appears. Search Console groups it under “Not indexed,” which reads as failure. A more accurate label would be “deliberately not indexed, as instructed” — these URLs were never meant to be in the index separately.
Why It Is Usually Fine
Almost every site generates alternate URLs as a normal consequence of how it works:
- Filter and sort parameters —
/shoes?sort=priceand/shoes?colour=blackcanonicalising to/shoes - Pagination — page two and beyond pointing at page one, if that is your chosen strategy
- Tracking parameters —
?utm_source=newsletterversions of pages shared in campaigns - Session or tracking IDs appended by a CMS or analytics setup
- Print or AMP variants of the main page
- Trailing slash and protocol variants where both resolve
- Tag and category archives that overlap with a main listing page
An ecommerce site with faceted navigation can legitimately produce tens of thousands of these. A blog will produce dozens. Seeing a large number is normal and proportional to how your URLs are generated.
When It Actually Signals a Problem
Four situations where this status is genuinely telling you something is wrong.
1. The Canonical Points to the Wrong Page
The classic version: a template hard-codes a canonical pointing at the homepage, so every page on the site declares the homepage as its canonical version. Google obediently indexes only the homepage, and your entire site vanishes from search.
This is more common than it sounds, usually introduced by a misconfigured plugin or a developer copying a template. Check a sample of pages across different templates and confirm each canonical points at itself unless you deliberately intended otherwise.
2. An Important Page Is Listed
If a page you actively want ranking appears under this status, its canonical is pointing somewhere else. That page will not rank independently, no matter how good it is or how many links it has.
Sort the report and scan for URLs that matter — money pages, key service pages, cornerstone content. Anything commercially important appearing here needs investigating immediately.
3. The Pages Are Not Actually Duplicates
Canonical tags are for genuinely equivalent content. If you have canonicalised two pages that serve meaningfully different search intents — say a product page and a comparison guide — you have merged two ranking opportunities into one, and lost the second.
Google may also disagree with you. Its documentation is explicit that canonicals are a hint rather than a directive, and when the content differs substantially Google will sometimes ignore your tag and index both. If that happens, the status changes to “Duplicate, Google chose different canonical than user” — which is a different and more actionable warning.
4. Redirect and Canonical Are Fighting
If a page canonicalises to a URL that then redirects somewhere else, you are giving contradictory instructions. Canonicals should point at a URL that returns a 200 OK — never at a redirect, a 404, or a noindexed page. Our guide to 301 vs 302 redirects covers when a redirect is the right tool instead of a canonical.
How to Diagnose It in Five Minutes
- Open the report. Search Console → Page Indexing → click the status. You get the list of affected URLs.
- Export and scan. Look for patterns. If every URL has
?in it, you are looking at parameters and it is almost certainly fine. If clean, meaningful URLs appear, investigate those specifically. - Inspect a sample. Use the URL Inspection tool on three or four. It shows both the canonical you declared and the one Google selected. When those match, the system is working.
- Check the destination. Confirm the canonical target is indexed, returns 200, and is not itself canonicalised somewhere else. Chained canonicals are a real and confusing failure mode.
- View source on the page itself. Confirm there is exactly one
<link rel="canonical">in the<head>. Multiple conflicting canonicals — usually a theme and a plugin both adding one — cause Google to ignore all of them.
Our Google Search Console tutorial covers navigating these reports more broadly if you are new to them.
Fixing the Real Problems
Wrong canonical target. Fix it at the template level rather than page by page. In WordPress this usually means correcting the SEO plugin’s settings; in a custom build it means fixing whatever generates the tag. In Astro and similar frameworks, check that the canonical is derived from the correct path — building it from a request-time value rather than the intended canonical form is a subtle source of exactly this bug.
Duplicate canonical tags. Disable canonical output in whichever component should not be producing it. Running two SEO plugins simultaneously is the usual cause and is worth resolving regardless.
Pages that should be independent. Remove the canonical, make the content genuinely distinct, and let both pages compete. If they are too similar to justify separate pages, the honest fix is merging them properly with a 301 rather than canonicalising and hoping.
Genuine near-duplicates you cannot merge. Leave the canonical in place. This status is the correct outcome.
Parameter noise at scale. If faceted navigation is generating enormous numbers of URLs, canonicals alone may not be enough. Combining canonicals with robots.txt rules or nofollow on filter links reduces the crawl waste — though be careful, because blocking a URL in robots.txt prevents Google from reading its canonical tag at all.
That last point catches people out regularly. If you disallow a URL, Googlebot cannot fetch it, cannot see the canonical, and cannot consolidate it. Blocking and canonicalising are alternative strategies, not complementary ones.
What Not to Do
Do not try to get the number to zero. It is not an error count. A healthy site with parameters will always have entries here, and chasing zero means removing canonicals that are doing useful work.
Do not noindex these URLs. A canonical already handles them. Adding noindex to a canonicalised page sends mixed signals, and Google may follow the noindex to the canonical target — deindexing the page you actually wanted.
Do not block them in robots.txt reflexively. As above, that stops Google reading the canonical.
Do not panic at large numbers. Compare against how many URLs your site legitimately generates. Twenty thousand entries on a filtered ecommerce catalogue is proportionate. Twenty thousand on a fifty-page brochure site is not.
Read It as Confirmation, Not an Error
For most sites, most of the time, “Alternate page with proper canonical tag” is Search Console confirming that duplicate URL handling is working. The word “proper” in the status is doing real work — Google is telling you the canonical tag was valid and it complied.
The five-minute check is worth running anyway, because the failure mode when this status is wrong tends to be severe: whole sections of a site quietly excluded from the index because a template points everything at the wrong URL. Scan for important pages, confirm a sample of canonicals point where you expect, and then leave the number alone.
If your Search Console reports are full of statuses you cannot interpret, or important pages are not being indexed and you cannot work out why, our SEO services include a full technical diagnosis. Get in touch with the team at blogthememachine.com, and subscribe to our newsletter below for more guides like this one.
