Alternate Page With Proper Canonical Tag: Usually Fine, Sometimes a Warning

"Alternate page with proper canonical tag" shows up in the Not indexed part of Search Console's Page indexing report, next to real errors like 404s and server failures. It looks like something went wrong. In most cases it means your canonical tag did its job.

Most of the time you can leave it alone. The work is spotting the few cases where you can't.

What Google says it means

Google's Page indexing report help defines the status in two sentences:

This page is marked as an alternate of another page (that is, an AMP page with a desktop canonical, or a mobile version of a desktop canonical, or the desktop version of a mobile canonical). This page correctly points to the canonical page, which is indexed, so there is nothing you need to do. Alternate language pages are not detected by Search Console. [1]

Three things have to be true for a URL to land here. It declared a canonical that points somewhere else. Google agreed with that choice. And the canonical URL is itself indexed. The alternate isn't indexed because the page it points to is.

The examples in the definition, AMP and separate mobile pages, are older setups. In practice most of what fills this bucket today is parameter URLs, tracking links, pagination and filter variants, and alternate hostnames, all carrying a canonical to a cleaner URL.

The last sentence of the definition matters if you run a multilingual site. Translations linked with hreflang don't show up in this bucket. Our English and Chinese articles each carry their own self-referencing canonical, so neither version appears here. That's correct, because each one should be indexed.

How it differs from the other canonical statuses

Search Console has three canonical statuses, and they describe different situations.

• Alternate page with proper canonical tag. You named a canonical, and Google agreed with you.
• Duplicate, Google chose different canonical than user. You named a canonical and Google picked another URL. That's a disagreement worth reading about, and we covered the usual causes.
• Duplicate without user-selected canonical. You didn't name one, so Google chose on its own. That one usually means a missing tag.

Only the first status confirms your setup is working. The other two mean Google is making the decision, or overruling yours.

Our home page is in this bucket right now

On 24 September 2026 we ran URL Inspection on our own domain variants. https://enfect.com/, the bare domain without www, came back as "Alternate page with proper canonical tag", with both the user-declared and the Google-selected canonical set to https://www.enfect.com/.

That was accurate, but only for the date Google last crawled it, 20 September. At that point the bare domain served the full site with a 200 status and a canonical tag pointing at www. On 23 September we added a 301 redirect from the bare domain to www. Today, the same URL redirects in one hop.

The http:// versions, which had redirected for much longer, already show "Page with redirect". Once Google recrawls https://enfect.com/, it should move to that status too.

The report records what Google saw on its last crawl. It says nothing about your site's current state. If you've changed the setup since, check the last crawl date before concluding anything.

It also means this status often shows up before a redirect does. If an alternate hostname or protocol only has a canonical tag, a redirect sends the stronger signal.

Why a canonical tag is only a hint

Google's guide on consolidating duplicate URLs ranks the signals it uses. Redirects are "a strong signal that the target of the redirect should become canonical", rel="canonical" is also a strong signal, and sitemap inclusion is a weak one. The guide adds that "these methods can stack and thus become more effective when combined" [2].

A canonical tag works well when nothing else contradicts it. If your internal links point at the alternate URL and your sitemap lists it too, the tag is outvoted. Google may start picking its own canonical, and the URL moves to "Google chose different canonical than user".

That's the practical answer to a recent r/TechSEO question about pages Google indexes despite a canonical tag. The most useful reply was to check the Google-selected canonical in URL Inspection first, then compare internal links, sitemap entries and redirects for conflicting signals [3].

When the count is worth investigating

The status is harmless per URL. The number can still tell you something. Three patterns are worth a look.

The count is far larger than your site

A site with 400 pages and 40 alternates is normal. A site with 400 pages and 700,000 alternates is being fed URLs from somewhere.

One r/Wordpress thread from July 2026 is the extreme case. A WooCommerce site had about 743,000 URLs as "Alternate page with proper canonical tag", 479,000 as "Crawled – currently not indexed", and only about 30 pages indexed. The alternates were parameter URLs (?i=) that nothing on the site linked to. All of them returned 200 with the home page as their canonical [4].

The canonical tags were working, since each URL correctly pointed home. The problem was that the site answered every made-up query string with a 200. One commenter pointed out that WordPress accepting arbitrary query strings explains the 200 but not how Google found the URLs, and suggested pulling access logs for the first requests to that prefix. Another had seen the same pattern after a hack: the pages looked normal in a browser, but Search Console's live test returned spam [4].

When the number is out of proportion to your site, look for the source of the URLs. The canonical tags already did their job.

The canonical target is the wrong page

"Proper" only means the tag is valid and Google accepted it. Search Console doesn't check that the tag points where you meant it to.

Common mistakes that land here without an error:

• Paginated pages (/blog?page=2) with a canonical to page 1, so nothing past the first page can rank.
• Product variants with a canonical to the parent when the variant is what people search for, like a specific colour or size.
• A template that hardcodes the home page or a category as the canonical for every page it renders.

In each case the alternate count grows and the status says everything is fine. Export the URLs from the report and read a sample. If the canonical target isn't what you'd want to rank for that URL's own search terms, the tag is the problem.

Pages you wanted indexed are in the list

This is the same check from the other direction. If a URL you built to rank shows up here, something on that page names another URL as canonical. Usually it's a plugin setting, a CMS default, or a canonical copied from another page.

When to leave it alone

A Rank Math user on r/Wordpress asked about a query-string URL shown as an alternate. Several replies said the same thing: the ugly URL has a canonical to the clean one, Google followed it, and nothing needs to change [5].

That describes most of this report. Tracking parameters, sort orders, session IDs and print views should all end up here.

Don't try to force the count down with the wrong tools. Google's guidance says not to use robots.txt for canonicalization, and doesn't recommend noindex for choosing a canonical within a site [2]. Blocking an alternate in robots.txt also stops Google from reading its canonical tag, which is how URLs end up "Indexed, though blocked by robots.txt" instead.

A short checklist

1. Compare the count with the number of pages you actually publish. If it's in the same range, stop here.
2. Export the list and sample 20 URLs. Note which patterns they share: parameters, hostnames, pagination, variants.
3. For each pattern, confirm the canonical target is the page you'd want to rank.
4. Run the canonical targets through a status checker. Each one should return 200 directly, without redirecting.
5. Make internal links and the sitemap point at the canonical URLs, so every signal agrees.
6. For alternate hostnames and protocols, replace the canonical-only setup with a 301 redirect.
7. If the count is far larger than your site, check your access logs for where the URLs came from.

For step 4, our bulk URL checker takes a pasted list and reports the status code of each URL. Any canonical target that doesn't return a clean 200 needs looking at.

Sources

1. Google Search Console Help, Page indexing report.
2. Google Search Central, How to specify a canonical URL with rel="canonical" and other methods.
3. r/TechSEO, How do you troubleshoot pages Google keeps indexing despite a canonical tag?, 7 September 2026.
4. r/Wordpress, Google discovered 1.2M parameter URLs (?i=) on my WordPress site, 30 July 2026.
5. r/Wordpress, Need help with Google Search Console errors on my WordPress site (Rank Math), 15 June 2026.

First-party figures come from this site's Google Search Console URL Inspection results for enfect.com and www.enfect.com, pulled on 24 September 2026.