Skip to content
Raptor home
Menu

Error or noindex page in sitemap

sitemaps.non_indexable_in_sitemap
Priority
Medium
Severity
Warning

What we look for

These addresses are in a sitemap (the file that lists your pages for search engines), but the crawled page answered with an error (a 4xx or 5xx status code) or is marked noindex (told search engines not to list it).

Why it matters

A sitemap tells search engines which pages to list, so entries they cannot list waste their visits and make the sitemap a less reliable guide to your site.

How to fix

Remove these addresses from the sitemap, through your CMS or SEO plugin, or fix the pages if they should be listed.

What it cannot know

Raptor matches sitemap addresses as written, so an entry that redirects to an error page is not caught.

Seen in a real crawl

From a crawl of Fernhollow Outdoor, a test site built for this site’s demo.

Medium

2 sitemap addresses lead to an error or a hidden page

  • /waterproofs/Non-indexable (noindex) in /sitemap.xml
  • /products/storm-shellNon-indexable (status 404) in /sitemap.xml
Paths on http://127.0.0.1:8006raptor 0.3.0, 17 Oct 2026

Open this finding in that crawl’s report

It also fired on Millbrook Hardware.

Where you’ll see it

The id is stable, and every surface uses it, so it’s the thing to search for or hand to an agent.

Terminal
When it is one of the five findings under Fix first, raptor crawl prints the id under it.
Check: sitemaps.non_indexable_in_sitemap
crawl.json and the CSV
The crawl JSON names the finding by this id, and so do the CSV and raptor_query.
"check_id": "sitemaps.non_indexable_in_sitemap"
The HTML report
This link opens the finding in the report, and each finding shows its id.
crawl.html#finding=sitemaps.non_indexable_in_sitemap
MCP
raptor_findings with this check_id returns the finding in full, with a fix brief ready to paste into a task. If it didn’t fire, it says why.
raptor_findings {
  "job_id": "...",
  "check_id": "sitemaps.non_indexable_in_sitemap"
}