What we look for
These sitemap files (files that list a site's pages for search engines) each hold more than 50 MB of text, the most the sitemap format allows in one file.
Why it matters
Search engines may reject a sitemap over the limit, so the pages it lists may not reach them through it.
How to fix
Split each file into smaller sitemaps and list them in a sitemap index (a sitemap that lists other sitemaps). Most CMS and SEO plugins can do this for you.
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.
over_ 50mb - 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. over_ 50mb" - The HTML report
- This link opens the finding in the report, and each finding shows its id.
crawl.
html# finding= sitemaps. over_ 50mb - 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. over_ 50mb" }