After a content management system (CMS) update, sitemap.xml opens, but contains no URLs. HTTP 200 can mask an empty selection, a disabled post type — such as services or products — or an old cache. Don’t start by resubmitting the sitemap to a search engine: first find out why the generator stopped including known published pages.
Is the entire file empty or just a section sitemap?
A sitemap lists URLs that the site owner considers preferable for search engines to process. Official documentation.
First determine exactly what is empty. A page sitemap has a urlset root element and URLs inside url/loc. An empty sitemap is different from a sitemap index — a list of section sitemaps. If the index includes a product sitemap but the services sitemap is empty, the problem has a limited scope. Save the root element and the list of child sitemaps. Separately note any syntax error: truncated XML is not a valid empty sitemap. The response 200 confirms that the file was loaded. To check whether it is useful, look for the URL of a known published page inside it.
A published page and a draft
| Example | What was found | What to check in the CMS | Expected result |
|---|---|---|---|
| Published service | The services post type is disabled | Check the setting | Re-enable the required type |
| Service draft | Not intended for the public | Keep it out of the sitemap | Do not increase its size |
| Empty child file | Its own segment | Check the selection | Don’t confuse it with the index |
| Cached old sitemap | The generator has already been fixed | Compare the new response | Clear the relevant cache |
Check the post type and exclusions
After a CMS update, check the settings for including post types, categories, and individual exclusions. Then find out whether the internal post type name used by the generator has changed. An import may have left a post published but moved it to a different group. A plugin may automatically exclude pages with noindex. If a service should appear in search, first find out why it received this tag; simply adding it to the sitemap won’t override it. If the generator uses its own URL list cache, compare its build date with the CMS update. Valid XML can still be empty if the generator wasn’t given the required posts.
Open a known published service as a guest. Search the XML for its full URL. If the URL is missing, check whether this post type is enabled in the sitemap settings, along with any individual exclusion and noindex. Don’t enable all types at once: changing one condition makes it possible to find the cause.
Compare a missing service with an article that remains
Suppose articles remain in the sitemap, but services have disappeared. Compare one article with one published service: public status, SEO directives, post type name, and sitemap settings. If the only difference is whether services are enabled, that gives you a specific hypothesis to test. Enable the required type on a test copy and regenerate the sitemap; don’t change several filters at once. If the service still doesn’t appear, check the individual exclusion and the source of the selection. This small test explains the cause better than reinstalling the plugin and losing its previous settings.
Check the generator and cache
Find out whether the sitemap is built on request, on a schedule, or by a separate background task. For a background generator, save the time of the last successful run and any error. Check write permissions and the file’s publication location, without exposing internal infrastructure paths or data in a public report. If a content delivery network (CDN) is used, ask the developer to compare the file on the site’s server with the response at the standard public URL. The fixed generator may already be producing a good file, while visitors still receive an old, empty response. The generator must first build a non-empty sitemap; then the CDN can serve its new version.
Regenerate the sitemap using the standard process
The test service should appear in its sitemap, while the draft should remain outside it. Fetch the regular public sitemap again after refreshing the cache. If the file is built by a background task, check the time of its successful run and any saved error.
Also read: Setting up a sitemap in WordPress (Yoast, Rank Math) and Errors in sitemap.xml: how to find and fix them. Site checks are available on the reChecker technical audit page.