Canonical Tags and Indexing: Every Search Console Canonical Status Explained

What is a non-canonical URL? It is a URL that Google treats as a duplicate of another page and therefore does not index: Google picked a different URL from the same group as the canonical, the one version it indexes and ranks.

What is a non-canonical URL?

A non-canonical URL is any URL in a group of duplicates that Google did not choose as the main version. Google defines the canonical as the URL of a page that Google chose as the most representative from a set of duplicate pages. Everything else in that set is non-canonical.

Duplicates arise more often than people think. One article can be reachable as http:// and https://, with and without www, with a trailing slash, with tracking parameters such as ?utm_source=, as a printer version or through a category path. To Google these are separate URLs with the same content. It indexes one, and Search Console lists the others under a non-canonical status.

A non-canonical URL is not an error by itself. Google’s own help page says that having a page marked duplicate or alternate is usually a good thing: it means Google found the copy and folded it into the right page.

How does Google choose the canonical URL?

Google picks the canonical from the signals you send and the signals it finds on its own. You can state a preference, but Google calls that preference a hint, not a rule. The documentation ranks the signals you control like this:

Google adds that these methods stack: a redirect plus a canonical tag plus a clean sitemap is more convincing than any one of them. Google also prefers HTTPS over HTTP and pages that are part of a hreflang cluster, and it looks at internal links and content quality.

When the signals conflict, Google chooses. Its troubleshooting page lists the usual reasons it overrides you: quality of the content or technical signals, such as language variants without hreflang, a CMS or plugin writing the wrong canonical, servers that return identical soft-404 pages, hacked pages, syndicated copies and copycat sites. One hard rule: if the canonical you declare is not similar to the page it sits on, Google won’t ever choose that URL.

Which Search Console statuses are about canonicals?

Four reasons in the Page indexing report describe a non-canonical URL. Two more often appear next to them because they interfere with canonical selection. The names below are the ones in Google’s current list.

If your page is missing for a reason that is not in this table, such as Crawled — currently not indexed, it is not a canonical problem. Start with why Google isn’t indexing your site or crawled vs. discovered.

How do you read user-declared vs Google-selected canonical?

Open the URL in Search Console’s URL Inspection tool and expand Page indexing. Two lines answer the canonical question:

• User-declared canonical — the canonical your page states. Google’s help page is blunt: there is no guarantee Google will choose it, but it is taken into consideration.
• Google-selected canonical — the URL Google actually treats as the main version when it found similar pages on your site.

Read them as a pair. Same URL on both lines: you and Google agree. Different URLs: you have a Google chose different canonical case. No user-declared canonical: Google decided alone. Two practical limits: the live test cannot predict which canonical Google will select, and the indexed values can be a few hours out of date.

To check many pages at once instead of one by one, see how to check if a page is indexed.

How do you fix a non-canonical URL?

First decide whether there is anything to fix. A non-canonical URL needs work only when the URL you want in Google is the one that lost. Then work through these cases in order:

1. The page is a genuine duplicate. Leave it, or 301-redirect it to the canonical if visitors don’t need it. This is the normal outcome.
2. Your preferred URL lost to a variant (http, www, slash, parameter). Redirect the variant to your preferred URL in one hop, make the canonical tag on the preferred URL self-referencing, link internally only to that URL and list only that URL in the sitemap.
3. A unique page was folded into another page. Check its canonical tag: a theme or plugin that points every page to the homepage or to page 1 of the blog is the classic culprit. Fix the tag, then make the content clearly distinct if two pages really are near-identical.
4. Two of your pages compete for one topic. Merge them into one strong page and 301-redirect the other. Fighting Google’s choice with tags alone rarely works when the content overlaps.

What does “non-canonical page in sitemap” mean?

It is an audit-tool warning, not a Search Console status: your XML sitemap lists a URL that points its canonical tag at a different URL. Google’s rule is that all pages listed in a sitemap are suggested as canonicals, so listing a non-canonical URL sends two contradictory signals at once.

The fix is to list only the URL you prefer. Google’s sitemap guidance says to choose the preferred URL and include that instead of every URL that leads to the same content. WordPress SEO plugins do this automatically for normal posts; the warning usually points to manually added URLs, redirected pages or pages whose canonical was set by hand. If Google can’t read the sitemap at all, that is a different problem: see sitemap could not be read.

How do redirects, noindex and X-Robots-Tag affect canonicals?

They are separate tools, and mixing them is the fastest way to confuse Google.

• Redirects. Permanent redirects (301, 308, an instant meta refresh) tell Google the target should be canonical. Temporary ones (302, 303, 307) do not. The redirecting URL itself ends up as Page with redirect, which is normal.
• noindex. Google doesn’t recommend noindex to steer canonical selection within one site. A page with both noindex and a canonical to another page sends mixed instructions; use the canonical alone.
• robots.txt. Don’t use it for canonicalization. A blocked URL can’t be crawled, so Google never sees its canonical tag and may still index the bare URL as Indexed, though blocked by robots.txt.
• X-Robots-Tag and the Link header. For PDFs and other non-HTML files you can send both rules as HTTP headers. X-Robots-Tag carries indexing rules such as noindex; the canonical goes in a Link header with an absolute URL:

Link: <https://www.example.com/downloads/white-paper.pdf>; rel="canonical"

Pick either the header or the HTML link element for a page, not both: Google says using both at the same time is more error-prone. And never use the URL removal tool to hide duplicates: it hides all versions of a URL from Search, including the one you want. What the tool is actually for is in how to remove a URL from Google.

How do canonical tags work with hreflang and language versions?

Each language version should be its own canonical, linked to its siblings with hreflang. Google asks you to specify a canonical page in the same language, or the best possible substitute language. Pointing the Dutch version’s canonical at the English page tells Google the Dutch page is a duplicate, and it drops out of Dutch results.

This site is an example: our English guide to Google’s canonical choice and its Dutch counterpart each have a self-referencing canonical and point to each other with hreflang (checked in the page source on 17 October 2026). Google also notes that alternate-language pages are not detected by Search Console as “alternate” pages, so don’t expect to find them under Alternate page with proper canonical tag.

FAQ