Alternate Page With Proper Canonical Tag: Should You Worry?

“Alternate page with proper canonical tag” is a Page indexing status in Google Search Console that means Google found a URL, saw its canonical tag pointing to a different page, agreed with it, and indexed that other page instead. In most cases it is a sign your setup works. Google’s own help page says there is “nothing you need to do.” The status only becomes a problem when a page you actually want in search results is sitting in that list.

So the real job isn’t fixing the status. It’s checking which URLs landed there, and whether each one belongs. After 8 years of reading this report for clients, that’s honestly the only question I care about.

What Does Google Actually Say This Status Means?

Google files this status under Not indexed, in the “Why pages aren’t indexed” table of the Page indexing report. The definition is short. The page is “marked as an alternate of another page,” and it “correctly points to the canonical page, which is indexed.”

Look at the examples Google gives in brackets, though, because they’re narrower than most people assume: an AMP page with a desktop canonical, a mobile version of a desktop canonical, and the desktop version of a mobile canonical. That’s it. In practice, when I audit WordPress and Shopify sites, the list is mostly filled with other things: tracking parameters, sorted and filtered URLs, and duplicate product paths.

Two more lines from the same help page matter here. First, “Alternate language pages are not detected by Search Console,” so a clean hreflang setup is not what fills this bucket.

Second, Google calls a page marked duplicate or alternate “usually a good thing,” because it means the canonical page was found and indexed. That’s the default reading. Start there, and don’t panic.

The Four Questions That Decide Whether You Act

Before touching a single tag, I run every sample URL in the list through four questions. The answers change the outcome completely.

1. Should this URL rank on its own? If no, the status is correct. If yes, you have a real problem.
2. Does the canonical point where you intended? A canonical to the right page is fine. A canonical to the homepage or the wrong product is a template bug.
3. Do your internal links and sitemap agree with the canonical? Mixed signals make Google’s choice less stable over time.
4. Is the count growing fast? A slow climb that tracks new content is normal. A sudden spike after a theme, plugin or migration change deserves a look.

If the answer to the first question is no and the second is yes, you can close the tab. Most sites I look at end right there. Five minutes, done.

When Is Alternate Page With Proper Canonical Tag Normal?

This is the main path, and it covers the majority of URLs I see in the report. Each of these URLs exists for a reason, but none of them should compete with the main page in search.

There’s a real benefit hiding in this list, too. Google’s docs say canonicals help it “consolidate the signals” of similar pages, such as links, into one preferred URL. So when a newsletter link points to /shoes/?utm_source=newsletter, the value of that link flows to /shoes/ instead of being wasted on a throwaway address. I’d much rather see a long list here than a long list of duplicates Google had to sort out on its own.

Google’s canonicalization docs list the same families of duplicates: region variants, device variants, protocol variants, site functions like sorting and filtering, and accidental variants such as a demo site left open. Google also says “some duplicate content on a site is normal and it’s not a violation of Google’s spam policies.” Nobody gets penalized for having ?utm_source links out in the wild, and the same holds for the store-specific copies I cover in ecommerce duplicate content fixes.

If the listed URL is a parameter, AMP, print or mobile variant, then leave it alone. If it’s a Shopify collection path pointing to the /products/ URL, then leave the tag alone but check which version your collection templates link to. If neither fits, move to the next section before deciding.

Parameter URLs are also a URL design question. My post on URL structure SEO covers how to keep them from multiplying in the first place.

When Does It Signal a Real Problem?

This branch is rarer. It’s also the one that costs traffic. The pattern never changes: a URL that should be earning clicks is telling Google, through its own markup, that some other page is the real one, and Google politely believes it and drops the page from results.

Here are the cases I’ve seen most often in audits, and what each one looks like in the list:

• Money pages pointing elsewhere. A service or product page has a canonical to the homepage, usually because a theme or page builder hardcoded one canonical for every template.
• Paginated pages canonicalized to page one. /blog/page/2/ points to /blog/. Google’s ecommerce pagination guidance says the opposite: “give each page its own canonical URL.”
• Product variants you want to rank. A color or size variant with real search demand points to the parent, so it can never appear for its own query.
• Translated pages pointing to another language. Google’s guidance is to specify a canonical in the same language, or the best substitute if none exists.
• HTTP versions still returning a page. http:// URLs in the list mean the old protocol serves content with a canonical, instead of a 301. It works, but a redirect is the stronger signal.
• A staging or old domain. Pages on a copy of the site point to production. The canonical is doing its job, yet the copy shouldn’t be crawlable at all.

For every item on that list except the last two, the fix is to give the page a self-referencing canonical, link to it internally by its real URL, and include it in your sitemap. For the HTTP case, add a 301 redirect to HTTPS. For a staging copy, put it behind a login.

Branch two has one clear sign. The URL sits in your navigation, your sitemap or your ad campaigns, and it still shows up here. Never intentional.

How Do You Check It With URL Inspection?

The Page indexing report shows the pattern. URL Inspection shows the proof. Here’s the exact route I take:

1. In Search Console, open Indexing > Pages and scroll to the “Why pages aren’t indexed” table.
2. Click Alternate page with proper canonical tag to see the example URLs. Google caps this list at 1,000 examples, so treat it as a sample, not a full export.
3. Pick a few URLs from each pattern you spot, and one that surprises you.
4. Hover over a URL and click its inspect icon, or paste the URL into the inspection bar at the top.
5. Expand Page indexing and compare User-declared canonical with Google-selected canonical.
6. Click View crawled page to see the HTML and the canonical tag Google actually received.

If both canonical fields show the same URL and that URL is the page you want ranking, you’re done. If the user-declared canonical is wrong, the bug lives in your template or SEO plugin, not in Google.

One trap to know about. The Test live URL button won’t settle canonical questions. Google’s help page says the live test “cannot predict whether or not the tested version will be considered canonical.” Only the indexed result shows the Google-selected canonical, so you’ll need to wait for a recrawl after any change.

Reading Two Results Side by Side

Say you inspect /shoes/?sort=price-asc. The verdict says it isn’t on Google, citing this status. Both fields show /shoes/, which is the category you want ranking.

Healthy. Move on.

Now try /services/local-seo/ on a site with a broken template. Same label, yet both fields show the homepage. Google obeyed the page, and your service page vanished from search as a result. Identical status, opposite outcome, which is why I never judge this report by its count alone and always open real examples before recommending anything to a client.

Alternate Page vs the Two Duplicate Statuses

People mix these up constantly. The difference tells you who made the call, so I find it easiest to read them side by side:

The third one is the status I actually worry about. Not this one. It means Google read your canonical and decided another URL was better. The status we’re discussing is the calm version of the same story, where your choice and Google’s match.

What Keeps a Healthy List Healthy?

A canonical tag is a hint. A strong one, but still a hint. I cover where the tag goes and the mistakes I see most in how canonical tags work.

Google’s documentation rates redirects and rel="canonical" as strong signals and sitemap inclusion as weak. When everything lines up, Google’s choice stays put. When the clues contradict each other, Googlebot may settle on some other address, and that’s how pages quietly drift into the “Duplicate, Google chose different canonical than user” bucket without anyone touching a setting.

I keep four habits on every site I manage:

• Every page you want indexed carries a self-referencing tag, which Google recommends.
• Tags use absolute addresses, since Google warns relative paths “can cause problems in the long run.”
• The sitemap lists preferred versions only.
• Menus, breadcrumbs and product grids link straight to the preferred version, never a parameter or collection path. Google’s own words: “link to the canonical URL rather than a duplicate URL.”

None of this is exciting. Still, it’s why the status stays dull, and dull is precisely what you want here.

Edge Cases That Change the Answer

A few situations sit between the two branches. Each has its own if/then:

• A spike right after a migration. If thousands of URLs appear here within days of a redesign, check a sample. Often a new theme started adding parameters to internal links. The canonical catches them, but your internal linking now points at duplicates.
• Faceted filters in huge numbers. If filter combinations run into the tens of thousands, the canonical keeps them out of the index but not out of the crawl. Google’s faceted navigation doc calls rel="canonical" “generally less effective in the long term” for cutting crawl volume than blocking those URLs. My category page SEO guide covers when a filter deserves its own indexable page.
• Sitemap and canonical disagree. If a URL sits in your sitemap but canonicalizes elsewhere, you’re sending mixed signals, which is why my rules for a clean XML sitemap allow canonical URLs only. Google’s canonical docs say not to specify different canonical URLs for the same page with different methods.
• Someone “fixes” it with noindex. Don’t. Google doesn’t recommend noindex to steer canonical selection within one site, because it blocks the page from Search entirely.

When a big count of alternates shows up next to a growing pile of “Discovered – currently not indexed” URLs, crawl waste is the usual link. I break that status down in Discovered Currently Not Indexed: What It Means and How to Fix It.

The Decision Matrix

If you skipped straight here, this table is the whole post in one place.

When Should You Get Help?

Most site owners can work through the matrix above on their own. Bring in a technical SEO specialist or your developer when the wrong canonical comes from the theme or CMS code itself, when you’re mid-migration, or when important pages keep landing in “Duplicate, Google chose different canonical than user” after you’ve fixed the tags.

That’s the kind of work our SEO service takes on, and our technical SEO service covers template-level canonical bugs directly. If you’d rather check the basics first, my technical SEO checklist covers canonicals alongside redirects, sitemaps and robots.txt. Or grab a free SEO audit and I’ll tell you which bucket your URLs fall into.

Frequently Asked Questions

Does Alternate Page With Proper Canonical Tag Hurt Rankings?

No. It means the duplicate is out of the index and the canonical version is in. Google’s help page describes this state as usually a good thing. Rankings only suffer when the listed URL is one you wanted to rank, which is a canonical mistake on your side, not a penalty.

Should I Click Validate Fix for This Status?

There’s nothing to validate when the list is healthy, because the status isn’t an error. If you did correct a wrong canonical on important pages, use URL Inspection to request indexing for a handful of them, then watch the Google-selected canonical field after the next crawl.

Why Did My Alternate Page Count Suddenly Jump?

Usually because Google found a new batch of variant URLs, not because anything broke. Common triggers are a new tracking campaign, a theme that appends parameters to links, or newly crawlable filters. Inspect a few samples and confirm their canonical still points to the right page.

Should I Remove the Canonical Tag So These Pages Get Indexed?

Only for pages that genuinely deserve to rank on their own, and then replace it with a self-referencing canonical rather than removing it. For parameter, AMP and mobile variants, keep the tag. Indexing those would just split signals across duplicates.

Last updated: September 2026 by Mizanur Rahman