Why Search Console lists these pages as not indexed, and when to leave them alone

What the error means

The page points to another URL as its canonical, and Google agreed. This URL is not indexed because the canonical version is. In most cases this is Search Console confirming your setup works.

Why Google rejects it

Stores and content sites produce many alternate URLs on purpose: variant parameters, collection-scoped product paths, tracking parameters and AMP or mobile versions. They exist for visitors and correctly send Google to the main URL.

How to fix it

1. Open a few examples and confirm each one really is an alternate of the page named as canonical. If it is, no action is needed.
2. Act only when a page you want indexed appears in this report. That means its canonical points somewhere it should not; change it to a self-referencing canonical.
3. Stop linking internally to alternate URLs where you can, so Google spends less time crawling them.
4. Keep alternate URLs out of your sitemap.

Common causes

Tracking or sorting URL points to clean page

Campaign parameters, sort values, or other alternate URL forms may declare the clean product or category URL as canonical. Search Console excludes the alternate because Google intends to represent the group with the canonical. This is usually expected if the target is the page you want indexed.

Mobile or AMP alternate relationship

Some implementations use alternate pages that point to a canonical desktop or corresponding page. Inspect the relationship and target rather than treating the excluded alternate itself as an error.

Canonical points to the wrong product or category

A template bug can send many pages to one canonical target that is not equivalent. Google may treat the inspected URL as an alternate, while the intended page is different or not indexed. Compare page content, product IDs, and variant details between source and target.

Canonical destination is inaccessible or redirected

The target may return an error, redirect to another URL, or carry noindex. That weakens the intended preference and can leave the whole group unresolved. Inspect the canonical destination directly and confirm the final URL is indexable.

Fix it on your platform

On Shopify

1. For tracking or collection-context product URLs, inspect the canonical target in page source and confirm it is the intended clean product URL. If so, the alternate status may need no change.
2. Review custom theme code and SEO apps for broad canonical rules that point every product to the same collection or homepage.
3. Check variant behavior and market domains. Keep distinct product pages from canonicalizing to a different item unless the pages truly represent the same product content.
4. Confirm the canonical target is published and returns 200 on the primary domain.

On WooCommerce

1. Inspect the affected page's canonical setting in the active SEO plugin and compare the target with the product or category shown.
2. For parameters such as sorting and tracking, canonicalize to the clean page only when the content is effectively the same.
3. Check that the target is not a redirecting, noindex, or deleted URL, and that the sitemap links to the preferred destination.
4. Review plugin conflicts if many unrelated product pages share the same canonical.

On other platforms

1. Determine whether the alternate URL is intentionally secondary, such as a tracking or sort variant. If its canonical target is correct, leave it excluded.
2. For a wrong target, update the platform's page-level SEO field or template and ensure each page points to its true representative.
3. Check the target's response, indexability, and content before changing canonical behavior.
4. Align internal links and sitemap entries with the URL intended for search results.

How to confirm it is fixed

1. Inspect the reported alternate and its canonical target. Confirm they show substantially equivalent content and that the target is the preferred URL.
2. Inspect the canonical target in URL Inspection to see whether Google indexes it; an excluded alternate is not a problem if the target is indexed.
3. Use the canonical check to catch wrong, redirecting, or inaccessible targets across sampled pages.
4. If you corrected a template, inspect several URLs of that type and wait for recrawling; do not request indexing for alternates that should remain excluded.

A worked example

Hypothetical case: a Shopify store's product links carry campaign parameters, while each parameterized URL declares the clean product URL as canonical. Search Console lists those campaign URLs as Alternate page with proper canonical tag. The owner inspects the clean target, confirms it is published, indexable, and contains the same product, then checks that the sitemap and collection links use the clean URL. No change is needed to the alternate rule. They focus on whether the canonical page itself is indexed and leave the tracking variants excluded, which avoids turning normal URL variants into a false alarm.

Other errors like this