What we look for
These crawled pages are not in any sitemap (the file that lists your pages for search engines) Raptor read. Only pages search engines may list, and that name no other page as preferred, are counted.
Why it matters
Search engines can still find these pages through links, but a complete sitemap helps them find new and changed pages sooner.
How to fix
Add these pages to the sitemap, usually by letting your CMS or SEO plugin include every type of page you publish.
What it cannot know
Raptor compares addresses as written, so a page the sitemap lists under an address that redirects to it counts as missing.
Seen in a real crawl
From a crawl of Fernhollow Outdoor, a test site built for this site’s demo.
3 pages are not listed in the sitemap
/journal/ /journal/ storm-shell-review/ /journal/ pitching-in-the-rain/
http://127.0.0.1:8006raptor 0.3.0, 17 Oct 2026Open 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 crawlprints the id under it.Check: sitemaps.
urls_ not_ 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. urls_ not_ in_ sitemap" - The HTML report
- This link opens the finding in the report, and each finding shows its id.
crawl.
html# finding= sitemaps. urls_ not_ in_ sitemap - MCP
raptor_findingswith thischeck_idreturns 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. urls_ not_ in_ sitemap" }