A sitemap helps search engines discover the public URLs you want considered for indexing. WordPress can provide a core sitemap, while an SEO plugin may replace it with its own sitemap system. Use the active site's actual sitemap and verify the listed URLs before submitting it.
IN THIS ARTICLE
01 Identify the active sitemap provider
Try the WordPress core sitemap address, https://example.com/wp-sitemap.xml, using your real domain. If an SEO plugin manages sitemaps, use the address shown in that plugin's current settings instead. Some plugins use a sitemap index with a different filename. Avoid enabling overlapping providers merely to create more sitemap files.
02 Check the content
- Open the sitemap in a browser and confirm it returns a sitemap or sitemap index rather than an error, login page or unrelated redirect.
- Open several child sitemaps if an index is used.
- Check that listed URLs use the intended HTTPS hostname and public paths.
- Look for staging addresses, deleted content, private material or URLs redirected elsewhere.
- Correct the source content or sitemap configuration, then refresh the relevant cache and check again.
Does a sitemap guarantee indexing?
No. It is a discovery and canonicalisation signal, not a promise that every URL will appear in search results. Search engines still evaluate accessibility, duplication, quality and indexing directives. A page blocked by authentication or deliberately marked noindex is not made publicly indexable simply by listing it.
Why does the sitemap return a 404?
Check whether core sitemaps are disabled or replaced by an SEO plugin, whether the website is configured for search visibility, and whether rewrite rules or a security layer block the request. Use the provider's documented address rather than creating a static file that may become outdated.
03 Submit and monitor
Submit the verified sitemap through the appropriate search-engine webmaster account if you manage one. Review processing errors and inspect sample URLs after a migration. Keep sitemap URLs aligned with canonical URLs and redirects. Remove staging restrictions only from the intended live website, and protect staging with access controls rather than depending solely on robots instructions. Recheck the sitemap after a domain change or major change to content types and SEO plugins.