What we look for
Raptor found no sitemap (an XML file listing the pages you want search engines to find), either in robots.txt (the site's file of crawling rules) or at the usual addresses such as /sitemap.xml.
Why it matters
A small site that links every page well can do without one. On a larger or newer site, a sitemap helps search engines find pages that few links lead to.
How to fix
Have your CMS or an SEO plugin create /sitemap.xml, add a "Sitemap:" line with its full address to robots.txt, and submit it in Google Search Console.
Seen in a real crawl
From a crawl of Kestrel Bay Digital (the canonical-variants fixture), a test site from Raptor’s fixture suite.
The site has no XML sitemap
A site-wide finding: it describes the site, so it lists no pages.
http://127.0.0.1:8003raptor 0.3.0, 17 Oct 2026Open this finding in that crawl’s report
It also fired on the js-heavy fixture.
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.
no_ sitemap_ found - 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. no_ sitemap_ found" - The HTML report
- This link opens the finding in the report, and each finding shows its id.
crawl.
html# finding= sitemaps. no_ sitemap_ found - 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. no_ sitemap_ found" }