“Alternate page with proper canonical tag” in Google Search Console
What the status means, whether it's a problem, and how to fix it, step by step.
Not indexed · Checked against Google's documentation on 2026-10-19
Short answerUsually fine
Usually nothing to fix. The page names another URL as canonical, Google agrees, and that URL is indexed. Check only that no page you want in search is on the list: a template, plugin or language version with the wrong canonical is the one case that costs traffic.
Google: “This page correctly points to the canonical page, which is indexed, so there is nothing you need to do.” Page indexing report help
What the status means
The page has a rel="canonical" that points to a different URL, Google agrees with that choice, and the other URL is indexed. Google's help is direct: the page “correctly points to the canonical page, which is indexed, so there is nothing you need to do.”
In other words, this is a list of duplicates you told Google about, and Google listened. A growing number here is not a penalty and doesn't hurt the canonical page.
Is it a problem?
| What's in the list | Verdict |
|---|---|
URLs with tracking or sorting parameters (?utm_source=, ?sort=) | Fine, working as intended |
| Product URLs inside collections or categories (common on Shopify) | Fine |
http://, www or no-trailing-slash versions that still resolve | Fine, though a 301 is cleaner than a canonical |
| AMP or print versions, mobile URLs on a separate m-dot site | Fine |
| Language versions pointing to the main language | A mistake: each language should be its own canonical |
| Pages you want to rank, pointing somewhere else | A mistake: a template or plugin sets the wrong canonical |
So the only work here is a spot check: make sure no page you need in search is on the list.
Typical sources by platform
- Shopify: a product is reachable at
/products/nameand at/collections/category/products/name. The collection version points to/products/name, which lands here. Expected. - WordPress: Yoast and Rank Math add canonicals automatically. Paginated comments,
?replytocom=links and attachment pages often appear here. - Next.js and other headless builds: canonicals come from the page metadata. A shared layout that sets one canonical for every page, often the home page, is a classic bug: then every page shows up here pointing to
/. - Any site with marketing links: every ad and email link with UTM parameters creates a URL that canonicalizes to the clean one.
How to check that the list is clean
- Open Indexing → Pages → Alternate page with proper canonical tag and export the examples.
- Filter out the expected patterns: parameters,
http/wwwvariants, collection paths, pagination. - Look at what's left. Any service page, product, article or language version you want indexed should not be here.
- Inspect a suspicious URL. URL Inspection shows the User-declared canonical and the Google-selected canonical. If the declared canonical is not the page itself, find where it comes from: the theme, the SEO plugin, a hard-coded tag.
- Check the live page with the checker below; it reports the canonical in the HTML and in the
Linkheader, and flags pages with more than one canonical tag.
How to fix a wrong canonical
- Make the page point to itself. A page you want indexed should carry a self-referencing canonical: its own full URL.
- Fix the source, not the symptom. If a layout or template sets the canonical, fix it there so every page gets its own URL.
- Language versions: each one points to itself, and the versions are tied together with
hreflang. Google's documentation says to point a canonical to a page in the same language. - Remove duplicate tags. A theme and a plugin both adding a canonical can produce two conflicting tags; keep one.
After the fix, request indexing for the most important pages. The status updates when Google recrawls them.
When a redirect is better than a canonical
A canonical keeps the duplicate URL accessible. If nobody needs that URL, such as the http:// or www version of the site, redirect it with a 301 instead. Google calls both a redirect and rel="canonical" strong signals; a redirect also sends visitors to the right page. Keep canonicals for duplicates that must keep working, like URLs with parameters.
What not to do
- Don't try to make this list empty. Parameter and tracking URLs will always land here, and that is fine.
- Don't noindex the duplicates. Google's documentation advises against using noindex to choose a canonical within a site; use
rel="canonical". - Don't block the duplicates in robots.txt. Google can't see their canonical then, and blocked URLs can still be indexed without content.
Check a URL
Paste one of the URLs from the report. The checker follows redirects and tests the status code, robots.txt, noindex and canonical.
Related statuses
- DependsDuplicate without user-selected canonicalThe page duplicates another, declares no canonical, and Google chose a different URL.
- DependsDuplicate, Google chose different canonical than userThe page names a canonical, but Google picked another URL.
- Usually finePage with redirectThe URL redirects elsewhere, so the target is indexed instead.
FAQ
No. They are duplicates you've labeled correctly. Parameter, tracking and collection URLs will keep adding to this list, and that's fine.
Shopify makes each product reachable inside every collection, at /collections/…/products/…, and those URLs point their canonical to /products/…. That's working as intended.
No. The removal tool hides URLs temporarily and can affect all versions of a URL. These pages are already handled by their canonical.
Want us to look at your Search Console?
We go through the Pages report, crawl the site and tell you which statuses cost you traffic and which are harmless, with the fixes in priority order.