Skip to content
SEO Madmanby Adam Hafez
Free tool

Noindex, canonical and sitemap conflict checker

Noindex, canonical and sitemap conflict checker: see where one page's three signals contradict Google's own guidance. Free, runs in your browser.

Runs entirely in your browser. Nothing you enter is uploaded, logged or stored.

Cross-references the signals you enter for one page. It cannot crawl the live site to discover them itself, so accuracy depends on entering the page's real robots meta tag, canonical tag and sitemap status.

Key takeaways

  • Google does not recommend noindex to prevent selection of a canonical page, because it will completely block the page from Search.
  • Google's sitemap guidance says to include the URLs you want to see in search results, which a noindexed page is not.
  • Google says to list the URL you prefer in a sitemap, not every URL that leads to the same content.
  • Google calls sitemap inclusion a weak canonical signal and sitemap submission a hint, so a missing entry is only worth checking.
  • This checker cross-references one page's own three signals, unlike the site's sitemap-vs-robots.txt checker, which compares a whole sitemap against Disallow rules.

What it takes

  • The page's own URL
  • Its declared canonical URL, if any
  • Whether it carries a noindex directive
  • Whether it is listed in the XML sitemap
  • Whether other pages canonicalize to it

More tools

All of them free, all of them browser-only.

Browse the tools

How to use it

  1. 1Enter the page's URL and canonicalLeave the canonical field matching the page URL, or blank, if the page has no canonical tag at all; that reads as a self-referencing canonical.
  2. 2Check whether the page carries noindexThis is the page's own robots meta tag or X-Robots-Tag header value, not a directive on any other page.
  3. 3Check whether it is listed in the sitemapThis is whatever the live sitemap.xml actually contains today, not what it should contain.
  4. 4Check whether other pages canonicalize to itAnswer yes only if you have confirmed at least one other URL's rel=canonical points here; this is the condition that turns a lone noindex into a cluster-wide problem.
  5. 5Resolve a flagged conflict at the sourceEach conflict names the specific Google guidance it contradicts; fix whichever of the three signals is actually wrong rather than adding a fourth signal to compensate.

Enter one page’s URL and canonical, tick whether it carries noindex, whether it is in the XML sitemap and whether other pages canonicalize to it, and the checker lists every conflict with Google’s documented guidance. It works on what you enter, in your browser, and does not crawl the site, so accuracy depends on entering the page’s real tags and sitemap status.

What this conflict checker tests

  • noindex on a canonical target (problem). Google’s canonicalization guide says it does not recommend using noindex to prevent selection of a canonical page within a single site, because it will completely block the page from Search. When other pages point their canonical here, a noindex removes the whole cluster, not one URL.
  • noindexed page in the sitemap (warning). Google’s sitemap guide says to include the URLs you want to see in search results.
  • Duplicate in the sitemap (warning). When the page is indexable but its canonical points to a different URL, Google’s advice is to choose the URL you prefer and list that instead of all URLs leading to the same content.
  • Canonical page missing from the sitemap (information). Google calls sitemap submission a hint and sitemap inclusion a weak canonical signal, so this is worth checking, not a conflict.

The canonical comparison is exact after URL parsing. https://example.com/a and https://example.com/a/ count as different URLs, as do http and https versions, so enter the canonical exactly as the tag declares it.

How to read the results

  • Problem (red): the noindex-on-canonical conflict. Fix this first, because it can remove several URLs from Search at once.
  • Warning (amber): a sitemap entry that contradicts the page’s own signals.
  • Information (grey): an indexable, self-canonical page left out of the sitemap.
  • Pass (green): “Consistent” when the page is indexable, self-canonical and listed, or “Consistent, intentionally excluded” when it is noindexed, not a canonical target and not in the sitemap.

One state returns no lines: an indexable page whose canonical points elsewhere and that is not in the sitemap. Nothing contradicts there, since the duplicate is correctly left out.

An error appears if the page URL or a filled-in canonical is not a valid absolute URL.

Worked example

The tool loads with https://example.com/blog/old-post as both page and canonical, no noindex, listed in the sitemap. Result: “Consistent”, a pass.

Now say an editor added noindex to retire the post, but three category duplicates still canonicalize to it and it is still in the sitemap. Tick “Has a noindex directive” and “Other pages point their canonical at this URL”. Two lines appear: “noindex on a canonical target” as a problem, and “noindexed page listed in the sitemap” as a warning.

The fix depends on intent. To keep the content in Search, remove the noindex. To retire it, point the duplicates’ canonicals at a live page and drop the URL from the sitemap.

For the duplicate case, untick noindex and the canonical-target box, and change the canonical to https://example.com/blog/new-post. The result is “Non-canonical duplicate listed in the sitemap”, naming the canonical URL the sitemap should carry.

Common mistakes it catches

  • Using noindex to pick a canonical. Google lists redirects and rel canonical as strong canonical signals. noindex on the preferred URL does not choose it; it blocks it completely.
  • Stale sitemaps. Pages noindexed after launch often stay in a generated sitemap.
  • Mixed signals across methods. Google warns against specifying different URLs as canonical through different techniques. A sitemap listing the duplicate while its rel canonical points elsewhere is one form of that.

Sources

  1. 1.How to specify a canonical URL with rel="canonical" and other methods - Google Search CentralPrimary
  2. 2.Robots meta tag, data-nosnippet, and X-Robots-Tag specifications - Google Search CentralPrimary
  3. 3.Build and submit a sitemap - Google Search Central

Frequently asked questions

Can a page have both noindex and a canonical tag?

It can, but Google does not recommend noindex to prevent selection of a canonical page, because it will completely block the page from Search. If other pages canonicalize to a noindexed URL, the checker reports that as a problem.

Should noindexed pages be in my XML sitemap?

Google's sitemap guidance says to include the URLs you want to see in search results. A noindexed page is not one of those, so the checker warns when a noindexed page is still listed.

Should the sitemap list the canonical or the duplicate?

The canonical. Google says to choose the URL you prefer and include that in the sitemap instead of all URLs that lead to the same content. A page whose canonical points elsewhere triggers a warning if it is listed.

Is it fine for a canonical, indexable page to be missing from the sitemap?

It is not an error. Google calls sitemap submission a hint, and a page can still be found through links. The checker shows it as information worth checking, not a conflict.

How is this different from the sitemap vs robots.txt conflict checker?

That tool checks every URL in a pasted sitemap against robots.txt Disallow rules for a whole site. This one takes a single page's noindex, canonical and sitemap status and checks whether those three signals agree.

Tools

Hreflang XML sitemap generator

Hreflang sitemap generator: turn language codes and URLs into sitemap XML with xhtml:link alternates, and check codes and URLs. Free, runs in your browser.