Quick answer
A sitemap helps search engines discover intended public URLs. WordPress core and SEO plugins can provide different sitemap systems, so identify the one actually active rather than assuming every site uses the same file.
Before you start
Confirm the public site address, search-visibility policy, active SEO plugin, and canonical hostname. Use a browser without privileged access when checking whether listed pages are public.
Steps
- Inspect the site's robots.txt and SEO settings for the declared sitemap. WordPress core normally provides a wp-sitemap.xml index when its sitemap feature is enabled; a plugin may replace it.
- Open the sitemap index and representative child maps. Confirm that each listed address uses the intended HTTPS hostname and returns the right public content.
- Look for staging domains, deleted pages, redirecting URLs, private content, and duplicate URL variants. Fix the content status or sitemap owner rather than editing a generated XML file by hand.
- Submit the correct index through the owner's authorized search-console account when appropriate, then monitor its reported processing and discovered URL issues.
Verify the result
The sitemap should load as valid XML and describe the current public site. A submitted sitemap is a discovery aid, not a promise that every listed page will be indexed or ranked.
Troubleshooting and recovery
If it returns 404 or HTML, inspect permalink handling, plugin configuration, cache, and search visibility. Do not expose draft content solely to increase the sitemap's URL count.
Related help
- Check WordPress search-engine visibility before and after launch
- Technical SEO reviews: scope and checks
- Plan redirects when website page addresses change
Official references
Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.
