The sitemap should be reachable on the public site without errors.
Sitemap XML
The XML sitemap helps search engines discover the public URLs that matter on a site. In a WordPress launch or handoff workflow, this check helps confirm that the sitemap exists, is accessible, and reflects the current public structure of the website.
Why it matters
A valid XML sitemap supports URL discovery and gives search engines a clearer view of the public pages that should be considered for crawling and indexing. If the sitemap is missing, broken, outdated, or filled with the wrong URLs, the launch setup becomes less reliable.
This matters especially after migrations, staging cleanups, or structural changes, where a sitemap may still expose old URLs or fail to include the current public ones. The sitemap does not replace signals like canonical or meta robots, but it should remain technically coherent with them.
What to review
Before marking this check as correct, review the following points:
It should return a valid response and not fail because of broken redirects or server issues.
The sitemap should reflect current public URLs, not staging, blocked, or outdated versions.
It should not include obviously wrong or irrelevant URLs.
The sitemap should be consistent with the site's current canonical and indexability signals.
How PreFlight checks this check
PreFlight requests the public sitemap location and verifies whether the XML sitemap is accessible from the outside. The goal is to detect whether the file exists, loads correctly, and behaves like a real sitemap for the live site.
This check helps surface technical issues such as missing sitemaps, invalid public access, or sitemap outputs that do not look coherent with a production-ready WordPress setup. It is a practical verification step before delivery.
PASS / WARN / FAIL
The XML sitemap exists, is publicly accessible, and looks coherent with the live public site structure.
The sitemap exists, but accessibility or URL signals still deserve review before launch.
The sitemap is missing, invalid, inaccessible, or clearly out of sync with the live public site.
Common mistakes
Leaving a sitemap from staging or an old migration active on the live site.
Serving a broken or inaccessible sitemap URL.
Including URLs that should not be public or indexable.
Assuming the sitemap is correct without checking whether it reflects the current site structure.
Treating the sitemap as a substitute for canonical or page-level index controls.
FAQ
Is an XML sitemap required for WordPress?
A site can exist without one, but an XML sitemap is still a useful technical signal for discovery and launch readiness, especially on sites with multiple public URLs.
Can a sitemap be valid and still be badly configured?
Yes. A sitemap may load correctly and still contain outdated, irrelevant, or inconsistent URLs that weaken the final setup.
Does the sitemap replace canonical or meta robots?
No. The sitemap helps search engines discover URLs, but canonical and meta robots still control other important indexing signals.
Check your WordPress site before delivery
Reduce rework, catch last-minute issues and review critical points before launch.
Run analysis