Alternate Page with Proper Canonical Tag: What It Means and How to Fix It

What the status actually means

When Google finds several URLs that show the same or almost the same content, it groups them and picks one to index. That chosen URL is the canonical. The others are alternates, and Google keeps them out of search results so people do not see the same page three times.

A page lands in Alternate page with proper canonical tag when three things are true at once: Google crawled it, the page declares a canonical pointing to a different URL, and Google accepted that choice. The word proper is the key. It tells you Google found nothing wrong with the instruction. Google is not complaining; it is reporting that it followed you.

That makes this status different from its two neighbours in the Page indexing report:

For a wider view of every status in the report, see Search Console errors explained.

Which URLs belong in this report

Before changing anything, sort the listed URLs into groups. Export the list from the report and look at the patterns rather than the individual addresses. Most sites find that the bulk of entries fall into a few types that are meant to be alternates:

• Parameter URLs such as ?utm_source=newsletter, ?ref=partner, ?sort=price or ?view=grid, which show the same content as the clean URL.
• Filtered views such as /shoes?colour=red that a shop has chosen not to index.
• Print and share versions such as /article/print/ or ?amp=1.
• AMP pages that point back to the standard page.
• Separate mobile URLs on an m-dot site, where the mobile page canonicalises to the desktop page.
• Protocol and host variants such as the http or non-www version, if those are served rather than redirected.

Entries that deserve a closer look are the ones with content of their own: blog posts, guides, product pages, service pages, location pages and language versions. If one of those is here, either its canonical is wrong or the page is so close to another page that you have told Google, perhaps by accident, that they are the same thing.

How to see the canonical a page really sends

Start in Search Console. Paste a URL you want indexed into URL Inspection and open the Page indexing section. It shows two fields side by side: User-declared canonical, which is what your page says, and Google-selected canonical, which is what Google chose. On this status the two match, and both point somewhere other than the inspected URL.

Next, check the live page yourself, because the inspection result reflects the last crawl. From a terminal:

curl -s https://example.com/guides/running-shoes | grep -io '<link[^>]*canonical[^>]*>'

A correct result for a page that should be indexed looks like this:

<link rel="canonical" href="https://example.com/guides/running-shoes">

A canonical can also be sent as an HTTP header, which is common for PDFs and sometimes added by a CDN. Check the headers too:

curl -sI https://example.com/guides/running-shoes | grep -i '^link:'
# Link: <https://example.com/guides/>; rel="canonical"

If the HTML and the header disagree, Google has to guess, so remove one. Then look at the rendered page. Open Chrome DevTools, go to the Elements panel and search for canonical. If the raw HTML says one thing and the rendered DOM says another, a script is rewriting the tag after load. Google can pick up either value, so the safest fix is to put the correct canonical in the server HTML and stop the script changing it.

Check the whole site at once

One page tells you little about a template. Run a crawl with our site audit or any crawler and list every URL whose canonical does not match its own address. Group the results by folder or template. A pattern such as every post in /guides/ pointing to /guides/ is a template bug, and one fix clears the lot.

Why a page ends up with the wrong canonical

Trailing slash and host mismatches are easy to miss because the pages look fine in a browser. If your canonical points to https://example.com/page while the live URL is https://www.example.com/page/, you are naming a URL that redirects. The trailing slash guide and the www canonicalisation guide walk through settling on one form.

Fixing the tag on common platforms

WordPress

Core WordPress prints a self-referencing canonical on single posts and pages. SEO plugins replace it with their own. In Yoast SEO and Rank Math, open the post, go to the Advanced tab of the plugin panel and look at the Canonical URL field. It should be empty, which means use this page, unless you genuinely want another URL to be the main one. If many posts are affected, the field was probably filled in bulk by an import or a duplicate-post tool. Also confirm that only one plugin outputs canonicals, and that Settings, General shows the correct https site address.

Shopify

Shopify themes normally print the canonical with a Liquid object in theme.liquid:

<link rel="canonical" href="{{ canonical_url }}">

Problems come from themes or apps that replace canonical_url with a fixed address, or from product URLs reached through a collection, such as /collections/sale/products/trainer, which Shopify canonicalises to /products/trainer. That second case is expected and should stay in the report.

Next.js

In the App Router, set metadataBase in the root layout and a per-page canonical in each route's metadata:

// app/guides/[slug]/page.tsx
export async function generateMetadata({ params }) {
  const { slug } = await params;
  return { alternates: { canonical: `/guides/${slug}` } };
}

A common mistake is setting alternates.canonical once in the root layout, which every child route then inherits, so every page claims to be the home page.

Static and hand-built sites

Search the head include for rel="canonical" and make sure the value is built from the page's own path, not typed in once. For the general rules, the canonical tags guide covers syntax and placement.

A worked example

A small outdoor shop exports 1,240 URLs from this report. Grouping them by pattern gives four buckets:

• 1,100 filter and sort URLs such as /shoes?colour=red and /shoes?sort=price, all pointing to /shoes. Correct; leave them.
• 95 collection paths to products such as /collections/sale/products/trail-boot, pointing to /products/trail-boot. Correct; leave them.
• 27 URLs with ?utm_ tracking parameters from an email campaign. Correct, but the menu was linking to some of them.
• 18 guides in /guides/, all pointing to /guides/. Wrong.

URL Inspection on one guide shows the user-declared canonical as https://example.com/guides/. The head template builds the canonical from the section path rather than the page path. After the template is changed to print https://example.com/guides/running-shoes for that page, a curl check confirms the new tag, and the 18 guides are submitted through URL Inspection. Within three weeks the guides show as indexed. The tracking links in the menu are replaced with clean URLs so Google stops finding them.

The fix, step by step

Edge cases worth knowing

• A canonical is a hint, not a command. Google weighs it against redirects, internal links, sitemaps and content similarity. That is why fixing the tag alone sometimes leaves a page in the duplicate statuses instead.
• Pagination. Page 2 onwards of a listing should canonicalise to itself. Pointing them at page 1 can stop Google reaching the items linked only from deeper pages.
• Cross-domain canonicals. If you syndicate articles to a partner site, the copy there may canonicalise to your original. The partner's URL will sit in their report, not yours.
• Noindex plus canonical. Avoid putting noindex on a page that also canonicalises elsewhere. The signals conflict, and Google may carry the noindex over to the canonical.
• Product variants. Whether size and colour variants should be separate pages depends on search demand. The product variants guide helps you decide.

Keeping it fixed

Canonical bugs usually arrive with a theme update, a new plugin, a migration or a developer copying a page. Add a canonical check to your routine after any of those changes. A monthly crawl that flags pages whose canonical differs from their own URL catches most regressions before Google does.

Keep your sitemap limited to canonical URLs that return 200, and keep internal links pointing to the same versions. When the sitemap, the menu and the tag all name one address, Google rarely overrides you. If the sitemap and canonicals drift apart, the sitemap mismatch guide shows how to reconcile them. Finally, when two pages truly cover the same thing, merge them and redirect the weaker one; see the duplicate content guide.