Alternate Page With Proper Canonical Tag Explained
- Harold Bell
- 11 hours ago
- 7 min read
Key takeaways
|
You open the Page Indexing report, and there it is. Alternate page with proper canonical tag, sitting under Not indexed, with a few hundred URLs behind it.
The word "not indexed" does the damage. Somebody on the team screenshots it, drops it in Slack, and now you're spending a Thursday afternoon explaining a Search Console status instead of shipping content. I've watched this exact fire drill happen at companies with real SEO budgets and people who know what they're doing.
What does alternate page with proper canonical tag mean?
Alternate page with proper canonical tag means Google found a URL, saw a canonical tag pointing to a different URL, and honored it. The page isn't indexed because you told Google not to index it. It's a confirmation that your canonical worked, not an error, and it usually needs no action. |
Break the status into its three parts and it explains itself.
Alternate page means Google considers this URL a variant of another URL rather than a page in its own right. Proper canonical tag means Google found a rel="canonical" element and could parse it. And the placement under Not indexed means Google followed that instruction and indexed the target instead.
So the status is a receipt. You made a request, Google granted it, and the report is confirming that. Compare it to crawled currently not indexed, where Google read the page, formed an opinion, and decided against you. That one is a judgment. This one is compliance.
The distinction matters because most audit tools treat them identically, sorting by volume and surfacing whatever bucket is biggest. Your canonical bucket will almost always be big. On an ecommerce site with faceted navigation it can run to tens of thousands of URLs. On a B2B site with UTM parameters flying around from paid campaigns, it climbs fast too.
Why do I have so many alternate page with proper canonical tag URLs?
Four sources generate most of the volume. Tracking parameters like UTM tags, paginated archive pages, localized or syndicated duplicates, and faceted ecommerce URLs for filters and sort order. All four are normal. A high count reflects site structure, not a problem to solve. |
Tracking parameters are the biggest source for most B2B teams. Every ?utm_source=linkedin variant of a page is a separate URL to Google. Your canonical points them all back to the clean version, Google honors it, and each variant lands in this bucket. One campaign with six channel tags across twelve landing pages produces 72 rows.
Pagination is second. Page 2 through page 40 of your blog archive canonicalize to page 1 on a lot of setups, including default Wix and WordPress configurations. Same for tag and category archives that overlap.
Then there's syndication and localization. If you publish the same piece at two paths, or run /en-us/ and /en-gb/ versions, the non-canonical version reports here. And on ecommerce, faceted URLs for color, size, and sort order can produce thousands of rows off a few hundred products.
Look at the URLs before you look at the count. Export the report, sort by pattern, and 90% of the volume usually collapses into two or three parameter types. The number is scary. The patterns behind it usually aren't.
When should you worry about alternate page with proper canonical tag?
Two cases. A canonical pointing at the wrong page, which happens after migrations or from a hardcoded template rule. And a canonical chain, where page A points to B and B points to C. Everything else in the report is expected behavior and safe to leave alone. |
The first case shows up when a template hardcodes a canonical, when a migration rewrites them in bulk, or when a CMS plugin applies a sitewide rule that fits most pages and breaks a few. The symptom is a page you want indexed showing up in this bucket. If a piece you commissioned, promoted, and linked internally is sitting under alternate page with proper canonical tag, something is pointing it away from itself.
The second case is chains. Google follows them but doesn't guarantee it will follow them far, and every hop is a chance to lose the signal. Chains usually appear after a 301 redirect project where the redirects got updated and the canonicals didn't.
Everything else is noise. Parameter variants, pagination, faceted URLs, and archive pages belong in this bucket. Leave them there. Chasing the count to zero is a way to spend a quarter making no difference to traffic, and I've seen teams do exactly that because the number looked bad in a board deck.
How do you fix alternate page with proper canonical tag?
Run the URL through Google's URL Inspection tool and compare the user-declared canonical against the Google-selected canonical. If they match, nothing is broken. If they don't, correct the canonical in your CMS, then request indexing on the fixed URL. Never remove canonical tags to lower the count. |
Start with the URL Inspection tool. Paste in a URL from the affected list and read the two canonical fields against each other. If they match, Google did what you asked and there's nothing to fix.
If they don't match, or the declared canonical points at a page you didn't intend, the fix is in your CMS, not in Search Console. Correct it at the source. Then check for conflicting signals, because a canonical tag is a hint rather than a directive, and Google weighs it against internal links, sitemap inclusion, and redirects. A page that canonicalizes to itself but is excluded from your sitemap and linked from nowhere is sending a mixed message.
For genuine fixes, use request indexing on the corrected URL to speed up recrawl, and submit through IndexNow if you want Bing to pick it up in hours rather than weeks. That second part matters more than most teams realize, since Bing feeds retrieval for several AI assistants.
What you should not do is strip canonical tags to make the report cleaner. Every URL you stop canonicalizing becomes a duplicate content candidate, and you'll trade a status that means nothing for one that means something.
How is this different from duplicate without user selected canonical?
Alternate page with proper canonical tag means you declared a canonical and Google agreed. Duplicate without user-selected canonical means Google found duplicates, found no canonical tag, and chose one for you. The first is you steering. The second is Google steering because you didn't, and it deserves attention. |
When Google chooses, it doesn't always choose the version you'd want ranking, and it won't tell you why. Two adjacent statuses, one a receipt and one a warning, is a genuinely bad piece of interface design on Google's part, and it's why the confusion is so common.
What should B2B marketing teams do about it?
Set a threshold and stop looking at the raw number.
Once a quarter, export the affected URLs and sort them by pattern. If everything falls into parameters, pagination, or known variants, close the tab. If a page you invested in shows up, that's your list, and it's usually short enough to fix in an afternoon.
The version of this that actually costs you money is subtler than a report count. When a canonical points the wrong way, the page you're promoting isn't the page accumulating authority, and your internal linking is pushing equity into a URL that doesn't rank. That's a real loss, and it doesn't announce itself. It shows up as a piece that never took off for reasons nobody can explain.
There's an AI retrieval angle too. Assistants pulling citations rely on the indexed version of a page, so a canonical pointing at a thin variant means the substantive version is the one that doesn't get cited. If you're working on AI visibility, canonical hygiene sits upstream of everything else you're doing, because a page that isn't the indexed canonical isn't in the retrieval pool.
Pull the export, sort by pattern, and find out whether anything you actually care about is in that list. It takes twenty minutes and it's the only part of this status worth your time.
If canonical confusion is one symptom of a bigger structural problem across your content, book time with me and we'll look at it together.
Frequently asked questions
Is alternate page with proper canonical tag an error?
No. It appears under Not indexed in the Page Indexing report, which is why teams read it as a problem, but it's a receipt rather than a warning. Google is confirming it followed the canonical instruction you gave it and indexed the target URL instead.
How do I check which canonical Google selected?
Paste the URL into the URL Inspection tool in Google Search Console and open the Page indexing panel. It shows two fields, User-declared canonical and Google-selected canonical. When those two values match, Google honored your instruction. When they differ, Google overrode you and picked a different URL.
Does Google index alternate pages with proper canonical tags?
No, and that's the intended outcome. Google indexes the canonical target instead and consolidates ranking signals from the variant onto it. The alternate URL stays crawlable and can still be visited directly, but it won't appear in search results as a separate entry.
Does alternate page with proper canonical tag hurt SEO?
On its own, no. Canonicalization consolidates signals rather than losing them, so the target page benefits. The exception is a canonical pointing at the wrong URL, which sends authority and internal link equity to a page you never intended to rank. That version is a real loss.
Should I remove canonical tags to reduce the count?
No. Every URL you stop canonicalizing becomes a duplicate content candidate, and Google will pick a canonical for you without telling you which one or why. You'd be trading a status that means nothing for one that means something, purely to make a report look cleaner.
What is a canonical chain and why does it matter?
A canonical chain is when page A canonicalizes to page B and page B canonicalizes to page C. Google follows chains but doesn't guarantee how far, and each hop risks losing the signal. Chains usually appear after redirect projects where the redirects got updated but the canonical tags didn't.
Does alternate page with proper canonical tag affect AI citations?
Indirectly, yes. AI assistants retrieve from the indexed version of a page, so whichever URL wins canonical selection is the one eligible to be cited. If a canonical points at a thin variant, the substantive version sits outside the retrieval pool entirely. Canonical hygiene sits upstream of AI visibility work.
Comments