Encited logo
PricingTalk to sales
Alternate Page with Proper Canonical Tag: What It Means and When to Fix It

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

Nov 9, 2026November 9, 2026·Updated Nov 18, 2026November 18, 2026·by Aki from Encited

Alternate page with proper canonical tag means Google indexed the URL your canonical points to. See when it's fine, when it hides a bug, and how to fix it.

Alternate page with proper canonical tag means Google found a page whose canonical tag points to another URL, agreed with it, and indexed that other URL. Most of the time there is nothing to fix. Tracking links, product variants, sort and filter URLs and AMP pages are meant to end up in this status. It's a problem when a page you want in search results is on the list, or when the canonical points to the wrong URL.

Key takeaways

  • Products, services, articles, categories, paginated and regional pages in this status need a fix.
  • Sorting the exported list by URL pattern tells you in a few minutes whether any of it belongs in Google.
  • Compare the two canonical fields in URL Inspection with what your server sends, before and after JavaScript runs.
  • A list far bigger than your site costs crawls, so cut the duplicate URLs Googlebot can find.

What Alternate page with proper canonical tag means

A canonical tag is a line in a page's <head> that names the URL you want Google to index for that content. The main page names itself, and its copies name the main page:

html
CopyDownload
<!-- On https://example.com/products/trail-runner -->
<link rel="canonical" href="https://example.com/products/trail-runner" />
<!-- On https://example.com/products/trail-runner?color=black -->
<link rel="canonical" href="https://example.com/products/trail-runner" />

When the page's own URL differs from the URL in the tag, the page is an alternate. Google treats the tag as a strong hint, weighs it with redirects, internal links and the sitemap, and picks the canonical page: the one version it indexes and shows in results. The Google indexing field guide explains how it weighs those signals.

Google's Page indexing help says the page "correctly points to the canonical page, which is indexed, so there is nothing you need to do." Its examples are AMP and mobile versions of a page, and in practice the list holds every URL whose canonical names a different page. In URL Inspection the URL shows "Page is not indexed: Alternate page with proper canonical tag". Links pointing to it count toward the canonical URL.

Sort the list into fine and fix

Click the status in the Pages report, export the URLs, and group them by pattern before you open any single page.

URL patternExampleFine whenFix when
Tracking parameters?utm_source=, ?gclid=, ?fbclid=The canonical drops the parameterYour own menu, footer or body links carry the parameter
Product variants/products/trail-runner?variant=123Nobody searches for the variant by nameThe variant has its own searches and its own content
Category paths to a product/collections/shoes/products/trail-runnerThe canonical points to the main product URLYour templates link to products through these paths
Sort and filter URLs?sort_by=price, ?color=blackThe canonical points to the unfiltered categoryA filter has search demand and deserves its own page
Pagination/blog/page/2NeverPage 2 and later point to page 1
Protocol, host and slash variantshttp://, www., /page/ and /pageThe canonical points to your https URLThey answer 200 where a 301 belongs
AMP and mobile URLs/amp/, m.example.comThey point to the regular pageThe regular page points to them
Regional pages/en-gb/, /en-au/NeverThey point to another region's page
Pages you want rankingProducts, services, articles, categoriesNeverAlways

A list made of the first four rows is Google handling duplicates the way you asked. Check pagination, regional pages and pages you want ranking first, because those cost you traffic. Paginated pages pointing to page 1 hide every item that is linked only from page 2 onward, and Google's pagination guidance asks for a canonical on each page; the category pagination section of the ecommerce guide has the setup.

To count the patterns, save the exported URLs in urls.txt, one per line, and run:

bash
CopyDownload
for p in 'utm_|gclid|fbclid' 'variant=' '/collections/.+/products/' 'sort_by|filter' '/page/[0-9]|[?&]page=' '^http://|//www\.' '/amp/'; do
printf '%6d %s\n' "$(grep -cE "$p" urls.txt)" "$p"
done
grep -vE 'utm_|gclid|fbclid|variant=|/collections/.+/products/|sort_by|filter|/page/[0-9]|[?&]page=|^http://|//www\.|/amp/' urls.txt

The last command prints every URL that matches none of the patterns. Open those one by one.

Every URL in your sitemap should be a canonical, so check those first. Index Rush pulls the live Search Console status of each sitemap URL and labels this status "Indexed (alt canonical)". Filter to it, and each row is a page your sitemap calls canonical while its own tag sends Google elsewhere, with "Your canonical" shown next to "Google's pick".

Read the canonical in URL Inspection

Paste one URL from the list into the inspection bar at the top of Search Console and open "Page indexing". Two lines matter:

  • User-declared canonical is the URL your page names in its canonical tag, HTTP header or sitemap.
  • Google-selected canonical is the URL Google indexed for this content.

For this status both lines show the same other URL. If that URL is the one you want, the page is fine. If it's wrong, your page sent Google there, and the fix starts in your template or CMS. If Google-selected canonical says "Inspected URL", the page is now its own canonical and the Pages report hasn't caught up.

Skip "Test live URL" when you check a canonical fix. Google's URL Inspection help says the live test can't predict canonical selection, so it can report "URL is available to Google" for a page that will still be grouped under another URL. The indexed result changes only after Googlebot recrawls the page.

Read the canonical your server sends

URL Inspection shows what Google stored at its last crawl. This curl check prints what your server sends now: the status code, any redirect, any canonical or robots rule in the HTTP headers, then the canonical and robots tags in the HTML:

bash
CopyDownload
url="https://example.com/products/trail-runner?variant=123"
curl -s -o page.html -D headers.txt "$url"
grep -iE '^(HTTP/|location:|link:|x-robots-tag:)' headers.txt
grep -ioE "<link[^>]*rel=[\"']?canonical[^>]*>" page.html
grep -ioE "<meta[^>]*name=[\"']?robots[^>]*>" page.html

In the output:

  • One canonical line pointing to the URL you want is correct. Two lines with different URLs give Google conflicting hints.
  • A link: header with rel="canonical" is a canonical too. Google recommends picking either the header or the HTML tag, since two that disagree are easy to miss.
  • A relative URL works, though Google recommends absolute https:// URLs.
  • A noindex in the robots tag or x-robots-tag header keeps the page out whatever its canonical says.

Then check the variants that should redirect. Each line prints the status code and the redirect target:

bash
CopyDownload
for u in "http://example.com/pricing" "https://www.example.com/pricing" "https://example.com/pricing/"; do
curl -s -o /dev/null -w "%{http_code} $u -> %{redirect_url}\n" "$u"
done

A healthy site returns 301 on each variant, pointing to the one URL you use. A 200 is a second copy of the page held back only by its canonical tag. A 301 is the stronger signal and moves the copy to "Page with redirect".

Check the canonical after JavaScript runs

On sites built with React, Vue, Angular or an AI website builder, the canonical in the raw HTML and the canonical after scripts run can differ. A common setup ships one index.html with the homepage as canonical, then changes the tag per route in the browser. Google's documentation asks for the canonical in the HTML source, with JavaScript leaving it alone.

Compare the two versions with curl and headless Chrome. The Chrome path is the macOS one; on Linux, use google-chrome:

bash
CopyDownload
url="https://example.com/pricing"
curl -s "$url" | grep -ioE "<link[^>]*rel=[\"']?canonical[^>]*>"
"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" --headless=new \
--virtual-time-budget=10000 --dump-dom "$url" | grep -ioE "<link[^>]*rel=[\"']?canonical[^>]*>"

On a test page that sets the homepage canonical in HTML and rewrites it with JavaScript, the first command prints https://example.com/ and the second prints https://example.com/pricing. That pair is the problem. When every route's raw HTML carries the same homepage canonical, Google can follow it, and your routes show up in this status with the homepage as their canonical.

In a browser, View Source shows the raw tag, and this line in the DevTools console shows the live one:

js
CopyDownload
[...document.querySelectorAll('link[rel="canonical"]')].map((l) => l.href)

Send each route its own canonical in the HTML, through server-side rendering, static generation or pre-rendering, which serves crawlers a rendered copy of each page with its canonical already in the HTML. If your setup can't put the tag in the HTML, Google's advice is to leave it out of index.html and set it only with JavaScript. The JavaScript SEO guide applies the same rule to titles, noindex and hreflang.

Shopify: variants, collection paths and filters

On a live Shopify store we checked in November 2026, the server HTML carried these canonicals:

URL requestedCanonical in the HTML
/collections/mens/products/mens-tree-runners?variant=123/products/mens-tree-runners
/collections/mens?sort_by=price-ascending/collections/mens
/collections/mens?filter.v.availability=1/collections/mens
/collections/mens?page=2/collections/mens?page=2

Variant, collection-path, sort and filter URLs on Shopify land in this status by design, and paginated collections keep their own canonical. Shopify's default robots.txt also blocks sort_by URLs and URLs with two or more filters. Two things are worth fixing:

  • Product links through the collection path. Themes that build product links with Shopify's within: collection filter create a second URL for every product in every collection, and Shopify's documentation warns about the SEO side of that filter. Link product cards with {{ product.url }} so Googlebot reaches the main URL first.
  • A second canonical from an app or a theme edit. Run the curl check on a product, a collection and the home page, and confirm each prints exactly one canonical. If your theme prints none, the Duplicate without user-selected canonical guide has the line to restore.

Product page SEO covers when a variant has enough demand for its own URL.

WordPress: the canonical field and the site address

On most WordPress sites an SEO plugin such as Yoast or Rank Math controls the canonical. A post requested with ?utm_source=newsletter returns a canonical to the clean post URL, which is correct. Wrong canonicals on WordPress usually come from three places:

  • The canonical URL field in the plugin's Advanced tab, filled in with another URL. A page duplicated from an older one can keep the old page's canonical.
  • The WordPress Address and Site Address under Settings, then General. If either says http:// or a host you don't use, every canonical on the site follows it.
  • Two plugins, or a theme and a plugin, each printing a canonical. The curl check shows two lines.

After a plugin or theme change, run the curl check on a post, a page, a category and the home page.

Regional pages, AMP pages and mobile URLs

Regional versions in one language, such as US, UK and Australian English, are duplicates by Google's definition, and so are pages where only the menu and footer are translated. When /en-gb/ names /en-us/ as its canonical, Google can honor it, and UK searchers get the US page. Give each regional page a canonical to itself and connect the set with hreflang. Google ignores a canonical tag that carries an hreflang attribute.

This prints the canonical, hreflang and AMP links on a page:

bash
CopyDownload
curl -s "https://example.com/en-gb/pricing" | grep -ioE "<link[^>]*(canonical|hreflang|amphtml)[^>]*>"

A correct regional page prints a canonical to its own URL and one hreflang line per version, including itself.

AMP pages belong in this status. The regular page links to its AMP version with rel="amphtml", and the AMP page names the regular page as canonical. The mistake is a regular page whose canonical points to the AMP URL, unless the AMP page is the only version. Separate mobile sites follow the same pattern: the desktop page links to the mobile URL with rel="alternate" and a media attribute, and the mobile page's canonical points to desktop. Google usually still shows the mobile URL to people searching on a phone.

When the list is far bigger than your site

Google crawls a URL to read its canonical. Duplicates get crawled less often than canonical pages, but each one still costs a request, and on a store with filters the alternates can outnumber real pages. New pages that wait behind those requests show up as Discovered - currently not indexed. Compare the count in this status with the number of URLs in your sitemap.

If the alternates dwarf the sitemap, reduce the duplicate URLs Googlebot can find. Stop linking to tracking and collection-path URLs from your own pages, keep parameters out of the sitemap, and block sort and filter patterns with no search demand in robots.txt. Google's documentation says not to use robots.txt for canonicalization, so block only URLs you don't need consolidated. Faceted navigation SEO has the full method, including how to count Googlebot hits on parameter URLs in your logs.

The site audit crawls your site the way a bot does and flags each page whose canonical is missing, points to another path or host, or appears twice in the head. A template that sends every product to the wrong URL shows up as one group of pages with the same issue.

How to fix Alternate page with proper canonical tag on a page you need

  1. Change the page's canonical to its own URL, written as an absolute https:// URL.
  2. Use that same URL in your sitemap and internal links, and remove the variants from both.
  3. If the other URL is a copy you don't need, 301 it to the page.
  4. Run the curl check again, and on a JavaScript site the raw and rendered check.
  5. Inspect the URL in Search Console and click "Request indexing".

Google's canonical troubleshooting guide says a page can stay grouped with its duplicates for up to two weeks after a fix. Indexing requests have a daily quota, so spend them on the pages that matter and let the sitemap carry the rest.

FAQ

What does Alternate page with proper canonical tag mean?

The page names another URL as its canonical, Google agreed, and Google indexed that other URL. The page itself stays out of search results on purpose.

Is Alternate page with proper canonical tag an error?

No. It's an exclusion Google reports for your information. Act on it only when the page should be in search results or the canonical points to the wrong URL.

Does Alternate page with proper canonical tag hurt SEO?

Not by itself. Links to the alternate URL count toward the canonical one. It costs crawl requests when the list is very large, and it costs traffic when a page you need is on it.

Should every page have a canonical tag?

Every page you want indexed should carry a canonical that points to itself. Google recommends this self-referencing canonical, though no canonical method is required. A page without one leaves the choice to Google, which is how Duplicate without user-selected canonical shows up.

How is this different from Duplicate without user-selected canonical?

Here the page declared a canonical and Google agreed with it. Duplicate without user-selected canonical means the page declared none, and Google picked a canonical by itself.

Can I delete the alternate URLs?

Parameter URLs have nothing to delete, because your server builds them on request. Stop linking to them and keep them out of the sitemap. A real duplicate page you no longer need should 301 to the canonical.

Google
Gemini
ChatGPT
Claude
Grok
Meta
Perplexity

Analyze and patch issues causing indexing delays

Find the pages Google skips, fix what holds each one back, and request a recrawl.

See how it works
Avatar
How can we help?
Get instant answers to your questions or leave a message for an engineer will reach out
Ask AI about Encited
See our docs
Contact support
Leave a message
We'll get back to you soon
Avatar
Ask AI about Encited
Product questions, troubleshooting and
Thinking
Preview
Drop an image to attach
Powered by ReplyMaven