A 200 status code means a server responded — it doesn't confirm what it responded with. A misconfigured redirect, a maintenance page served with the wrong status code, or a staging banner left on production can all pass a health check while the actual page looks nothing like it should. A screenshot closes that gap with a direct visual check.
Captured Automatically, Every Crawl
There's nothing to turn on. A screenshot of the site is captured as part of every crawl, alongside the URL health data and sitemap generation — one more signal collected in the same pass, not a separate step you have to remember to run.
Where It Shows Up
The most recent screenshot appears as a small thumbnail on the sitemap detail page, next to the rest of that crawl's results. It's a glance-level check, not a full visual regression tool — the point is a fast sanity check that the site captured is the site you expect, not a pixel-by-pixel diff against a previous version.
Best-Effort, Never Blocking
Screenshot capture is intentionally best-effort: if it fails for any reason, the crawl itself still completes normally with full health data and a valid sitemap. A failed screenshot capture never holds up or breaks anything else in the crawl — you might just see the previous screenshot in place until the next successful capture.