Free tools Windows power users keep installed
One-click scans. No signup required.
A WordPress sitemap 404 usually means the requested URL is not being generated, WordPress has stale permalink rules, another plugin or file owns the route, or the web server is not rewriting the pretty sitemap address correctly. Confirm the exact URL and its generator first, then enable the sitemap, save the existing permalink settings, check for conflicts, and test server rewriting before changing any URLs.
1. Confirm the exact sitemap URL and its owner
Write down the complete address that returns the 404, including the domain, protocol, filename and any path. WordPress sites do not all use the same sitemap route.
sitemap_index.xmlis the index address documented for Yoast SEO.sitemap.xmlmay be generated by another SEO plugin or by WordPress itself rather than Yoast.- A static sitemap file may also occupy the same path.
Check the active SEO plugin and its sitemap settings before troubleshooting a URL owned by a different component. Do not enable multiple generators for the same route without first deciding which one should serve it.
2. Make sure the intended sitemap is enabled and has content
Yoast SEO
- In the WordPress dashboard, open Yoast SEO → Settings → Site features.
- Turn on XML sitemaps if they are disabled.
- Use the screen’s sitemap-view control to confirm the address Yoast actually provides.
Check that the URL in your browser matches the address shown by the active generator. An individual sitemap can contain no entries when that post type or taxonomy has no eligible published content; an empty sitemap and a missing sitemap are different conditions.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
Other generators
Use the plugin’s own settings to identify its index URL and whether XML sitemaps are enabled. If WordPress core or another plugin owns the route, troubleshoot that generator instead of applying Yoast-specific instructions.
3. Refresh rewrite rules without changing public URLs
- Open Settings → Permalinks in WordPress.
- Leave the current permalink structure unchanged.
- Click Save Changes.
- Request the same sitemap URL again in a new browser tab.
Saving the existing structure refreshes WordPress’s rewrite state. Do not switch a long-running site to a different permalink structure as a test: the structure controls public post and page URLs, and an unnecessary change can create unrelated broken links and content 404 errors.
4. Remove competing sitemap routes carefully
Verify that only the intended provider is active for the failing path. Yoast documents that sitemap.xml can come from another plugin or from WordPress core. A physical file with the same name can also take precedence over dynamically generated output.
- Review installed SEO and sitemap plugins and disable a competing provider only after confirming which generator you want to keep.
- Ask an administrator or host to check the web root for a physical sitemap file.
- Do not delete an unfamiliar file before checking its ownership and making a backup.
5. Determine whether server rewriting is the problem
For Yoast, the pretty sitemap_index.xml address is backed by a non-pretty query-string form using ?sitemap=1. Test the query-string form in the same site context, following the address pattern shown by your installation.
| Test result | Likely next check |
|---|---|
The query-string sitemap loads, but sitemap_index.xml returns 404 |
Investigate web-server rewrite handling, virtual-host configuration and the site’s directory path. |
| Both forms return 404 | Recheck the generator, sitemap setting, permalink refresh and competing routes. |
| The sitemap loads but contains no entries | Check whether the relevant post type or taxonomy has eligible published content. |
Apache and NGINX are different
Apache and NGINX use different configuration mechanisms, and a rule intended for one must not be pasted into the other. Subdirectory and multisite installations can require additional path handling. Identify the web server and the correct configuration scope before editing anything.
If you cannot confirm whether the site runs Apache or NGINX, locate the relevant configuration file, or assess a subdirectory or multisite setup, contact your hosting provider or server administrator. Server-level changes can affect every URL on the site.
Rank #4
6. Recheck caching only after the route is corrected
Request the original sitemap address again after each change. If a caching plugin or CDN is serving an old response, clear the cache relevant to that URL and test again. Caching is a conditional check, not the default explanation for a 404; first verify the generator, permalink state, content and rewrite route.
A quick decision path
- Wrong URL or owner? Identify the exact filename and the component intended to generate it.
- Generator disabled? Enable XML sitemaps and verify the displayed sitemap address.
- Stale WordPress rewrites? Save the current permalink settings without changing their structure.
- Conflict? Check other sitemap plugins and physical files using the same path.
- Pretty URL only fails? Compare it with the generator’s query-string form and investigate server rewrites.
- Server details unknown? Ask the host or administrator to inspect the configuration.
When to stop editing and contact your host
Escalate when the fix requires Apache or NGINX configuration, the site is installed in a subdirectory or multisite network, you lack file or server access, or you cannot establish which component owns the route. Give the host the exact failing URL, the result of the query-string test, the active sitemap provider, and whether saving the current permalinks changed anything.
Frequently Asked Questions
Can I fix a sitemap 404 by changing my permalink structure?
No. Save the existing structure to refresh rewrite rules, but do not change a site’s established permalink pattern merely to test the sitemap. A structure change can create unrelated content 404 errors.
Why does Yoast’s sitemap index work in one URL format but not another?
If Yoast’s query-string form loads while the pretty index address fails, the generator is responding and the web server’s rewrite routing is the more likely problem.
Should I delete a sitemap.xml file from the server?
Only after confirming that it is a physical file, identifying its owner and making a backup. It may belong to another sitemap provider or be intentionally managed by the site administrator.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →
