Sitemap URLs and HTTP 200
An XML sitemap tells search engines which URLs you care about. For those listed URLs, it is good hygiene that each URL responds with HTTP 200 on the first HTTP response—without relying on redirects (3xx), client errors (4xx), or server errors (5xx). That keeps crawl budgets predictable and avoids sending crawlers through unnecessary hops or dead ends.
This is separate from “soft” error pages that still return 200 with a thin or misleading body; those require manual review and are not inferred automatically here.
What SEO Perception does
We discover sitemap documents from your site’s robots.txt file using standard Sitemap: lines (case-insensitive). If none are declared, we also try a common default path (/sitemap.xml on your site’s host).
We parse urlset sitemaps for <loc> entries and follow sitemap index files to nested sitemaps, with limits on how many documents and page URLs we process per run so large or unusual setups stay bounded.
For each in-scope page URL (same crawl scope as your website, including subdomain settings where applicable), we merge a sitemap marker onto that URL’s row in our database (or queue it for the normal crawler if it was not discovered yet). There is no separate bulk HTTP probe: the crawler records the first HTTP response when it visits that exact URL string (redirects not followed).
A background pass then compares that stored status to 200; you can also refresh possibilities from saved crawl data using Recheck possibilities on the website. Fixing the server response or updating the sitemap to match live URLs addresses the finding.