Alternate Page With Proper Canonical Tag: What the Search Console Status Means and How to Diagnose It

“Alternate page with proper canonical tag” usually means Google is doing exactly what you asked: it found a duplicate or near-duplicate URL, saw a canonical tag pointing to the preferred version, and chose not to index the alternate page. In most cases, this is not an error. It is a signal that Google has grouped similar pages and picked the canonical URL for search results.

TLDR: This Search Console status means a URL was not indexed because it correctly points to another URL as the main version. For example, if /shoes?color=black has a canonical tag pointing to /shoes, Google may index only /shoes. In one ecommerce audit, 8,400 product filter URLs showed this status, but only 73 needed fixing because the rest were intentional duplicates. Check it only when the “alternate” URL should rank on its own.

What the status means in plain English

Google does not want to index every version of the same content. If your site has several URLs that show the same, similar, or slightly filtered content, Google tries to pick one version. That selected URL is the canonical.

The Search Console status “Alternate page with proper canonical tag” appears when:

• Google crawled a URL.
• The page contains a canonical tag pointing to another URL.
• Google agrees that the other URL should be the indexed version.
• The alternate URL is kept out of the index.

A simple example:

• Alternate URL: https://example.com/jackets?sort=price
• Canonical URL: https://example.com/jackets

That is often perfect. Sorting parameters rarely deserve separate rankings. Google keeps the clean category URL and ignores the sorted copy.

When this status is normal

This status is common on healthy sites. It often shows up for URLs created by filters, tracking tags, printer pages, mobile variants, AMP pages, and product options.

You normally do not need to fix it when the alternate URL is only a copy or utility version. Common safe cases include:

• Tracking URLs: ?utm_source=newsletter points to the clean page.
• Sorting URLs: ?sort=low-to-high points to the base category.
• Session URLs: temporary IDs point to the clean URL.
• HTTP versions: HTTP pages point to HTTPS pages.
• Slash variants: /page points to /page/, or the reverse.
• AMP pages: AMP points to the standard HTML version.

Honestly, it feels like Search Console makes this status sound scarier than it is. Seeing thousands of excluded URLs can look bad at first glance. But if those URLs are duplicates, exclusion is the correct result.

When it becomes a problem

The status becomes a problem when the URL in the report should be indexed. That usually means your canonical logic is too broad, broken, or copied from a template without enough care.

Watch for these red flags:

• A key service page points to the homepage as canonical.
• A product page points to a category page by mistake.
• Every paginated page points to page one.
• Localized pages point to the wrong country version.
• Filtered pages with real search demand point to a generic page.
• The canonical URL returns a redirect, 404, soft 404, or server error.

Here is a painful example. A site has separate pages for blue running shoes, black running shoes, and white running shoes. Each page has unique copy, stock, images, and search demand. But the template adds a canonical tag from every color page to /running-shoes. Google may exclude all color pages. If those terms bring high-intent traffic, that “proper” canonical is not proper for the business.

How to diagnose the issue in Search Console

Start with the URL Inspection tool. It is the fastest way to see what Google thinks. Expect to waste time on repeat checks, though. Sometimes a URL test takes 20 seconds longer than it should, only to tell you what the report already suggested.

1. Open Search Console. Go to Indexing, then Pages.
2. Click “Alternate page with proper canonical tag.” Export the sample URLs.
3. Inspect a sample URL. Use the URL Inspection search bar.
4. Compare canonicals. Look at User-declared canonical and Google-selected canonical.
5. Test the live URL. Google’s indexed view may be old.

If the user-declared canonical and Google-selected canonical match, Google accepted your signal. If they differ, Google ignored your chosen canonical and picked another URL. That calls for a deeper check.

Image not found in postmeta

Check the canonical tag itself

Open the page source or inspect the rendered HTML. Search for rel="canonical". The tag should look like this:

<link rel="canonical" href="https://example.com/preferred-page/">

Look for common errors:

• Multiple canonical tags on the same page.
• Relative canonical URLs that resolve in strange ways.
• Canonical tags added by plugins and overwritten by themes.
• JavaScript-injected canonicals that differ from the raw HTML.
• Wrong protocol, such as HTTP instead of HTTPS.
• Wrong host, such as non-www instead of www.

A canonical tag is a hint, not a command. Google usually follows it when the content matches and the signal is clean. If the target page is unrelated, blocked, slow, or broken, Google may choose something else.

Compare the alternate page with the canonical page

Open both URLs side by side. Ask a blunt question: Would a searcher see these as the same result?

If the answer is yes, the status is probably fine. If the answer is no, fix the canonical.

Use this quick comparison:

• Title: Is it unique or nearly identical?
• Main heading: Does it describe a separate topic?
• Body content: Is there meaningful unique content?
• Products or listings: Are the items different enough?
• Search intent: Would the page satisfy a different query?

For example, /laptops?sort=rating does not need its own index entry. But /gaming-laptops probably does. If both canonicalize to /laptops, you may be hiding a valuable page.

Check internal links and sitemaps

Canonical tags are only one signal. Google also looks at internal links, sitemap entries, redirects, hreflang, and content similarity.

If your sitemap includes many alternate URLs, but those pages canonicalize elsewhere, you are sending mixed signals. Your sitemap should usually include only the canonical URLs you want indexed.

Internal links matter too. If your menus, breadcrumbs, and product cards point to parameter URLs, Google may crawl piles of alternates. That wastes crawl activity and clutters reports. Link to the clean canonical URL when possible.

How to fix unwanted alternate canonical statuses

If the status is wrong, fix the source. Do not just request indexing again. That rarely helps if the same canonical tag remains.

• Set a self-referencing canonical on pages that should rank on their own.
• Update templates so unique product, category, and service pages do not point to a parent page.
• Remove alternate URLs from XML sitemaps unless they are meant to be canonical.
• Fix redirects so the canonical URL returns a clean 200 status.
• Standardize internal links to point to the preferred URL format.
• Use parameter rules in your platform to prevent endless crawlable filter combinations.

After fixing, use Validate Fix in Search Console if the report allows it. Also inspect a few key URLs manually. Search Console can lag by days or weeks, so do not panic if the chart moves slowly.

What you should report to stakeholders

Do not report this status as a raw error count. That creates noise. Split the URLs into intentional alternates and wrongly canonicalized pages.

A useful status note might say:

• 12,300 URLs reported as alternate with proper canonical.
• 11,850 URLs are expected filter, sort, and tracking variants.
• 450 URLs need review.
• 38 URLs are high-value pages with incorrect canonicals.

That tells the real story. Most alternates are harmless. A small group may be costing traffic.

The practical takeaway

“Alternate page with proper canonical tag” is usually a housekeeping status, not a disaster. Treat it as a prompt to verify your canonical strategy. If the alternate page is a duplicate, leave it alone. If it has unique value, give it a self-canonical, link to it clearly, add it to the sitemap, and make sure Google can crawl a clean 200-status page.

The goal is simple: let Google ignore the junk copies, while your best pages stay eligible to rank.