← Back to blog

Technical SEO · November 11, 2026 · 8 min read

Alternate Page With Proper Canonical Tag Explained

Alternate page with proper canonical tag means Google read your canonical, agreed with it, and indexed the target instead. The 30-second check that confirms it, and the rare cases that are real.

By FluxWriter

Alternate page with proper canonical tag is Google telling you the canonical tag worked. The URL was crawled, Google read the canonical you declared on it, agreed with it, and indexed that target page instead. It sits under "Not indexed" in the Page indexing report, which is why it reads like a fault, but on most sites the large majority of URLs in that bucket are behaving exactly as designed. This covers the check that confirms it in about thirty seconds, the small number of setups where the status points at something real, and the platform defaults that generate these URLs by the hundred.

The Label Describes Agreement, Not A Fault

The Page indexing report splits every URL Google knows about into indexed and not indexed. "Not indexed" is not a complaint list. It holds every reason a URL is absent from the index, including the deliberate ones: pages you redirected, pages you blocked, pages you marked noindex, and pages you declared duplicates of something else.

This status is the last of those. You put a canonical tag on the page pointing at a different URL. Google crawled it, compared the two, and accepted your declaration. The word doing the work is "proper". It means the canonical you supplied was respected. The page is called an "alternate" because that is its role: a second address for content that lives at the canonical URL.

The status worth reacting to is the neighbouring one, "Duplicate, Google chose different canonical than user". That is disagreement. Google saw your canonical and picked something else anyway. A canonical tag is a strong hint rather than a directive, and that status is what it looks like when the hint loses. A large number under the proper-canonical status and a small number under the disagreement status is the shape of a setup that is working.

One URL Settles It In Thirty Seconds

Open the status in the Pages report and copy any URL from the list. Paste it into the inspection bar at the top of Search Console. Under the page indexing details you get two lines: the canonical you declared, and the canonical Google selected. If both lines show the same URL, the tag did what you asked.

Then inspect that canonical URL on its own. You want "URL is on Google". Two inspections, and the question is answered. The duplicate is out of the index, the original is in it, and nothing needs fixing. If that target comes back as anything other than indexed, stop there and work on the target instead, because a canonical pointing at a page Google has not indexed consolidates nothing.

One sample is not enough if the list is mixed. Sort the URLs by shape rather than by count: parameter URLs, collection paths, paginated archives, print views. Check one from each pattern. Five inspections covers a list of four thousand URLs if those four thousand come from five templates, which on a CMS-driven site they usually do.

The thing you are looking for at this stage is a declared canonical pointing somewhere you did not intend. It is uncommon, and it is the whole reason to run the check rather than assume.

The URLs Were Generated By Your Platform, Not By You

Almost nobody hand-writes the URLs that end up here. Platforms mint them. Shopify serves the same product at a bare product path and again inside every collection that contains it, then canonicalises the collection-scoped versions back to the bare one. Variant parameters do the same. WordPress produces feed URLs, paginated archives and comment pages. Every ad click and email send appends tracking parameters that create another distinct address for a page you published once.

Faceted navigation is the biggest multiplier. Three filters with five options each produce well over a hundred combinations from a single category page, and a shop with forty categories and four hundred products has generated several thousand addresses without adding a word of content.

The figures in the table are illustrative. The real multiplier depends on how many collections, filters and campaigns you run.

None of those rows is a defect by itself. The fourth column is where attention belongs.

Four Setups That Are Genuinely Broken

The first is a canonical pointing at the wrong variant. The usual shape is a theme or plugin setting that canonicalises every product to its category, or every page to the homepage. The tell is severe: thousands of URLs under this status, a handful indexed, and organic traffic that never got started. Inspect three unrelated pages, and if all three declare the same canonical, you have found it.

The second is a canonical pointing at a URL that redirects. You are asking Google to consolidate on an address that then sends it somewhere else. It usually still resolves, but you have added a hop and a chance of the wrong final choice. Point the tag at the destination.

The third is a canonical pointing at a page that is itself noindexed. The two instructions contradict each other: index that page instead of this one, and do not index that page. Neither URL is a strong candidate for the index after that, and both can drop out.

The fourth is two canonicals on one page, or a canonical outside the head. Page builders, SEO plugins and hard-coded template tags each add their own, and the safe assumption is that conflicting declarations are ignored entirely, leaving the page with no canonical at all. Google renders pages before deciding, so a tag written by JavaScript can be read, but if the served HTML already declares a different target you have given two answers and the choice is no longer yours. View source, search for "canonical", count the matches. One is correct.

A Rising Count Matters More Than A High Count

The absolute number is mostly a property of your platform. A 300-product store with thirty collections can show six thousand URLs here and be perfectly healthy. A 300-page brochure site showing six is equally healthy. Comparing your number against someone else's tells you nothing.

The movement tells you something. Write today's figure down next to your indexed page count and check both monthly. If indexed pages hold steady while this bucket grows, you are watching new parameter URLs arrive and can ignore it. If indexed pages fall while this bucket jumps, something started canonicalising pages you wanted ranked. A theme update, a plugin default or a migration will usually have a date on it that matches the drop.

Crawl budget is the one concern that depends on scale. As a rough rule it becomes practical to worry about somewhere in the tens of thousands of URLs, not on a site with a few hundred pages. Below that, Google crawling your filter combinations costs you nothing you will notice.

Search Console Reports Weeks Behind Your Fix

The counts are built from the last time Google crawled each URL, not from the page as it stands now. Fix a canonical this afternoon and the report can show the old figure for weeks, because Google has to recrawl thousands of low-priority duplicate URLs before the bucket empties.

The honest expectation is weeks rather than days, and the trap is fixing the same thing twice because the number did not move. Use the live test in URL Inspection instead. It fetches the page as it stands right now and shows the canonical currently declared, which is the only confirmation you need that your edit shipped.

There is no Validate Fix button on this status, because Google does not treat it as an error; where a reason does offer one, press it once and leave it alone. Re-running it does not make Google crawl faster.

FAQ

Should I remove the canonical tags so these pages get indexed?

Almost never. Those URLs are duplicates of a page that is already indexed, and removing the tag asks Google to choose between them without guidance. The exception is a page you consider genuinely distinct, such as a variant with its own content, images and demand. That page needs real content of its own, not just the removal of a tag.

Does this status damage my rankings?

The URL is out of the index by your own instruction, so its absence costs you nothing. Signals that reach the alternate URL are consolidated toward the canonical, which is the entire point of the tag. What can cost you is the wrong canonical target, not the status.

One of my main pages is listed under this status. Why?

Something declared it a duplicate. Inspect it and read the user-declared canonical line, which names whatever page the tag points at. The usual sources are an SEO plugin's bulk setting, a template that hard-codes a canonical, or a page duplicated inside the CMS where the copy kept the original's tag.

The Practical Takeaway

Give this thirty minutes, once. Open the Pages report, note today's count for this status and today's indexed count, and keep both somewhere you will see them next month. Sample one URL from each distinct pattern in the list, confirm the declared canonical matches the one Google selected, and confirm that target is indexed. If every sample checks out, close the tab and stop thinking about it, because the status is bookkeeping rather than a task. If one pattern points somewhere you did not intend, that pattern is the only canonical work worth doing this week. Start by inspecting a single product or article URL and reading the user-declared canonical line.

← All posts