What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A WordPress sitemap 404 usually means the requested URL is not being generated, WordPress rewrite rules are stale, another sitemap provider owns the route, or the web server is not forwarding the pretty URL correctly. Confirm the exact sitemap address and its generator first, then enable the generator, save the existing permalink settings, and test for conflicts or server-rewrite problems.
1. Confirm the exact sitemap URL and its owner
Write down the complete address that returns the 404, including the domain, protocol and filename. Common WordPress installations do not all use the same path. Yoast SEO documents sitemap_index.xml as its index address, while sitemap.xml may be generated by another plugin or by WordPress itself.
Identify which component should serve that precise URL:
- the active SEO plugin;
- WordPress core;
- another sitemap plugin; or
- a physical XML file on the server.
Do not troubleshoot Yoast settings until you know that Yoast owns the address you are requesting.
#1 Best Overall
2. Enable the sitemap and verify that it has content
Yoast SEO
In the WordPress dashboard, go to Yoast SEO → Settings → Site features. Make sure XML sitemaps are switched on, then use the same screen’s view control to open the sitemap Yoast generates. Test that displayed address rather than assuming it is sitemap.xml.
Check for an empty individual sitemap
An index can exist while an individual post-type or taxonomy sitemap contains no entries. That can happen when the relevant content type has no eligible published content. An empty sitemap is a content-eligibility issue, not automatically a rewrite failure.
3. Refresh WordPress rewrite rules without changing your URLs
Go to Settings → Permalinks and click Save Changes without changing the selected structure. This makes WordPress rebuild its current rewrite state and is a documented first remedy for a sitemap 404.
Do not switch a long-running site to a different permalink structure just to test the sitemap. Permalink settings define public URL patterns; changing them can create broken links and new content 404 errors unrelated to the sitemap.
Free tools Windows power users keep installed
One-click scans. No signup required.
4. Remove competing sitemap providers safely
Only one intended generator should answer the route. Check whether another SEO or sitemap plugin is active and whether a static file named sitemap.xml or a similar sitemap file exists in the site’s document root.
Yoast advises disabling competing sitemap plugins and removing physical sitemap files before enabling Yoast sitemaps. If you need file access, ask a site administrator or your host to verify ownership and make a backup first. Do not delete an unknown file blindly; it may belong to another system or be referenced by your robots or search-console configuration.
Rank #4
5. Test whether the web server is rejecting the pretty URL
Yoast describes a non-pretty query-string form, ?sitemap=1, behind its pretty sitemap_index.xml address. If the query-string form loads but the pretty address still returns 404, the sitemap generator is probably working and server rewrite routing becomes the likely fault area.
Apache and NGINX require different fixes
Apache and NGINX use different configuration and rewrite mechanisms. Rules also vary for subdirectory installs and multisite networks. Never paste an Apache rule block into an NGINX configuration, or copy a root-site rule into a subdirectory or multisite setup without adapting it.
Recommended Free Tools
If you cannot identify the server, locate the correct configuration file, or assess a subdirectory or multisite installation, contact your hosting provider or server administrator. Server-level edits can affect every URL on the site, so they should be made by someone who can validate and roll back the change.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.6. Re-test after each change
- Request the same sitemap URL that originally returned 404.
- Confirm that the response is XML from the intended generator rather than an HTML error page.
- If the query-string route works but the pretty route does not, give the host the exact URLs and ask them to inspect rewrite handling.
- If a caching plugin or CDN is present and an old redirect or error appears to persist, purge the relevant cache and test again.
Cache clearing is a conditional check, not the default explanation for a sitemap 404. The primary checks are generator settings, eligible content, permalink state, conflicts and server rewrites.
Choose the next check from the symptom
| What you observe | Most useful next check |
|---|---|
| The intended sitemap feature is disabled | Enable it in the generator’s settings, then view the generated address. |
| Saving current permalinks fixes the URL | Leave the existing permalink structure unchanged and verify the sitemap and a few normal post URLs. |
sitemap.xml works under another provider |
Decide which provider should own the route and disable the competing generator. |
| The individual sitemap has no entries | Check whether that post type or taxonomy has eligible published content. |
?sitemap=1 works but sitemap_index.xml is 404 |
Ask the host or administrator to inspect Apache/NGINX rewrite routing and the site’s directory or multisite configuration. |
| The route remains wrong only in cached responses | Purge the relevant plugin or CDN cache, then request the URL again. |
When to contact your host
Escalate when the problem reaches server configuration: you do not know whether the site uses Apache or NGINX, cannot safely edit the relevant configuration, or run WordPress in a subdirectory or multisite network. Send the host the exact failing URL, the working query-string result (if any), the active sitemap generator and the time of your test. That information lets them distinguish a WordPress setting problem from a rewrite-routing problem.
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.
