
You published a new post yesterday. It is live on the site, visitors can read it, and the homepage lists it. But when you open your sitemap, the new post is not there. The sitemap still shows last week’s content, as if nothing changed. When wordpress sitemap not updating leaves new pages out, search engines keep working from an old map of your site, and new content takes longer to be found.
This problem is different from a missing sitemap. Your sitemap exists and loads — it is simply stale. The usual causes are caching, two sitemap generators fighting, content that is excluded from the sitemap, or a static sitemap file sitting in the way. This guide works through 11 fixes in order, from the simplest cache check to the deeper generator and scheduling checks. Back up before any fix that touches files, and use official WordPress and plugin controls only.
Table of Contents
- Why This Error Happens
- Quick Checks
- Diagnosing the Problem
- Fix 1: Check the Live Sitemap in a Private Window
- Fix 2: Purge Every Layer of Cache
- Fix 3: Confirm Which Sitemap Generator Is in Charge
- Fix 4: Check for a Static Sitemap File in the Site Root
- Fix 5: Resave Your Permalink Settings
- Fix 6: Check the New Content Is Published and Public
- Fix 7: Check Your SEO Plugin Sitemap Settings
- Fix 8: Test for a Plugin Conflict
- Fix 9: Check Robots.txt and the Sitemap Index
- Fix 10: Check the CDN and Server Cache Rules
- Fix 11: Check Scheduled Tasks and Run a Fresh-Post Test
- What to Avoid
- Frequently Asked Questions
- Conclusion
- Helpful Official Resources
Why This Error Happens
A sitemap is generated when it is requested, or served from a stored copy. Publishing a post should change what the sitemap lists the next time it is read. When it does not, one of these reasons is standing between the new content and the sitemap output.
1. A Cache Is Serving an Old Copy of the Sitemap
Caching plugins, server caches, and content delivery networks store copies of pages so they load faster. If a cached copy of the sitemap is served instead of a fresh one, the sitemap looks frozen even though WordPress has the new content ready. This is the most common cause of wordpress sitemap not updating, and it is also the easiest to fix — once you purge every cache layer, not just one.
2. Two Sitemap Generators Are Fighting
WordPress itself generates a sitemap, and most SEO plugins generate their own. Normally the SEO plugin takes over and the core sitemap steps aside. But if two SEO plugins are active, or if a plugin’s sitemap setting is half-configured, you can end up with two sitemaps at different addresses, and you may be checking the one that is no longer maintained. The “stale” sitemap is then not stale at all — it is simply the wrong one.
3. A Static Sitemap File Is Overriding the Dynamic One
Some tools and older plugins write a physical sitemap file into the site’s main folder. When a real file exists at the sitemap address, the server sends that file instead of asking WordPress to generate a fresh sitemap. The file never updates on its own, so the sitemap freezes at the moment the file was written. This cause is easy to miss, because the sitemap loads perfectly — it just never changes.
4. The New Content Is Excluded, Private, or Set to Noindex
Sitemaps list public, indexable content. A post set to private, a page excluded in the SEO plugin settings, a post type that is not included in the sitemap, or content marked noindex will not appear — by design. When wordpress sitemap not updating affects only some new content, an exclusion rule is the likely cause, and the sitemap is behaving correctly for the rules it was given.
5. Permalinks or Rewrite Rules Are Serving Stale Output
WordPress generates its sitemap through its rewrite rules, the same system that turns post addresses into pages. If those rules are damaged or out of date, requests for the sitemap can be answered with old output, an error page, or a cached response. Resaving the permalink settings rebuilds the rules and often clears the fault in seconds.
6. Scheduled Regeneration Is Not Running
Some sitemap setups rebuild their stored sitemap on a schedule, using WordPress’s scheduled task system. If scheduled tasks are not running — because of low traffic, a disabled task system, or a hosting setup that blocks it — the stored sitemap is never rebuilt. The content is ready, the generator works, but nothing tells it to run again.
Quick Checks
Two minutes before the deep fixes.
- Open the sitemap in a private browsing window, so your browser cache cannot fool you.
- Confirm the new post is published, not a draft or scheduled for later.
- Check whether the post is set to public — private and password-protected posts do not belong in a sitemap.
- Note which sitemap address you are checking, and whether an SEO plugin also provides one.
- Purge your caching plugin’s cache once, then re-check the sitemap.
- Check whether only one post is missing, or whether nothing new has appeared for days.
- Think about when it started — did wordpress sitemap not updating begin after a new plugin, a cache change, or a host move?
Diagnosing the Problem
| Symptom | Cause | Go to Fix |
|---|---|---|
| Sitemap fresh in private window only | Browser cache showing old copy | Fix 1 |
| Sitemap stale everywhere | Plugin, server, or CDN cache | Fix 2 |
| Two different sitemaps exist | Two generators active at once | Fix 3 |
| Sitemap never changes at all | Static sitemap file in the site root | Fix 4 |
| Sitemap loads wrong content | Damaged rewrite rules | Fix 5 |
| Only some new posts missing | Excluded, private, or noindex content | Fix 6 |
| Whole post type missing | SEO plugin sitemap settings | Fix 7 |
| Sitemap stale after new plugin | Plugin conflict | Fix 8 |
Fix 1: Check the Live Sitemap in a Private Window
Start by making sure the problem is real. Your browser loves to show you a saved copy of a page you visited before, and a sitemap you opened last week is exactly the kind of page it will serve from cache.
- Open a private or incognito browsing window.
- Type your sitemap address directly — your site address followed by /wp-sitemap.xml for the WordPress core sitemap.
- Look for your newest post in the list.
- If the post is there, your sitemap is updating fine, and your normal browser was showing a cached copy. Clear your browser cache and carry on.
- If the post is still missing, note the newest date shown in the sitemap — it tells you when the sitemap last changed.
- Repeat the check on a different device or network if you can, to rule out a local network cache.
- Write down which sitemap address you checked, because later fixes need to test the same address.
The newest date in step 5 is useful evidence. A sitemap that stopped changing on a specific day points to something that changed that day: a plugin install, a cache setting, a host move. A sitemap that changes sometimes but not always points to caching with a long lifetime. Either way, the private-window test costs a minute and stops you from fixing a problem that only exists in your browser. If the sitemap does not load at all, that is a different fault — our guide to WordPress sitemap not found covers the missing-sitemap case, including the permalink and plugin causes that stop a sitemap from appearing.
Fix 2: Purge Every Layer of Cache
WordPress sites often have several caches stacked on top of each other: a caching plugin, a server cache, and a content delivery network. Purging one layer while another holds the old sitemap changes nothing. Purge them all, then check again.

- In WordPress, open your caching plugin’s settings and purge or clear all caches.
- If your host provides a server cache control in the hosting panel, purge that cache too.
- If you use a content delivery network, purge its cache for your site, or at least for the sitemap address.
- Clear your browser cache, or use a private window for the check.
- Wait a minute, then open the sitemap and look for the newest post.
- If the post appears, caching was the cause. Note which cache layer you purged last, so you know where to look next time.
- If the post is still missing, leave the caches purged and move on to Fix 3 — the caches are now clean, which makes every later test trustworthy.
Caching is the cause most people find first and fix last, because they purge one layer and stop. A caching plugin’s purge button does not purge the server cache, and neither purges the delivery network. Work through all three, in order, every time. If cache problems keep returning across your site, our guide to WordPress cache not clearing explains each cache layer in detail, including the host and network caches that WordPress plugins cannot reach.
Fix 3: Confirm Which Sitemap Generator Is in Charge
WordPress core generates a sitemap, and SEO plugins generate their own. Only one should be in charge. When two are active, you can easily check the sitemap that nobody maintains, while the live one updates normally elsewhere.
- Check whether an SEO plugin is active on your site, and open its settings.
- Find the plugin’s sitemap settings and note whether its sitemap feature is switched on.
- Note the sitemap address the plugin provides — it is often different from the core sitemap address.
- Open the plugin’s sitemap address in a private window and check for the newest post.
- Open the core sitemap address in a private window and check it too.
- Decide which sitemap is the live one: it is the one your SEO plugin provides, when a plugin sitemap is switched on.
- If two SEO plugins are active, deactivate one of them — running two SEO plugins at once causes conflicts far beyond sitemaps.
- Check the live sitemap once more after any change, and use only that address from now on.
The confusion in this fix is common and completely understandable. Nothing on the site labels one sitemap “old” and the other “live”. The rule is simple: when an SEO plugin’s sitemap is on, that plugin’s sitemap is the one that matters, and the core sitemap is expected to step aside. If the plugin’s sitemap is the stale one, the later fixes apply to it. If the core sitemap is stale while the plugin’s is fresh, there is no problem at all — you were simply looking at the retired copy.
Fix 4: Check for a Static Sitemap File in the Site Root
A physical sitemap file in your site’s main folder overrides the dynamic sitemap completely. The server sends the file, WordPress never gets asked, and the sitemap stays frozen at the day the file was written. Finding and removing that file restores the live sitemap.
- Take a backup of your site before touching any files.
- Connect with your host’s file manager or a file transfer program.
- Open your site’s main folder — the folder that holds wp-config.php.
- Look for files named sitemap.xml, sitemap_index.xml, or similar sitemap files.
- If you find one, download a copy to your computer, then check its contents: does it list old content only?
- Rename the file rather than deleting it at first — add “-old” to the file name — so you can restore it if needed.
- Purge all caches as in Fix 2, then open the sitemap address in a private window.
- If the fresh, dynamic sitemap now appears, the static file was the cause. You can delete the renamed file once you are sure everything works.
- If nothing changes, restore the file’s original name and move on to Fix 5.
Static sitemap files usually arrive from older SEO tools, site migration tools, or manual uploads long forgotten. They are not harmful in themselves, but they silently take over the sitemap address. The rename-first approach in step 6 is deliberate: it tests the theory without destroying anything. If the renamed file turns out to be needed by another tool, restoring it is a ten-second job. If wordpress sitemap not updating has persisted for months with no change at all, a static file is a strong suspect — dynamic sitemaps rarely freeze so completely without one.
Fix 5: Resave Your Permalink Settings
WordPress builds its sitemap address through its rewrite rules. If those rules are damaged or out of date, sitemap requests can be answered wrongly. Resaving the permalink settings rebuilds the rules from scratch, and it takes less than a minute.
- In WordPress, go to Settings, then Permalinks.
- Do not change any setting — just look at the current structure and note it.
- Click Save Changes at the bottom of the page.
- WordPress rebuilds the rewrite rules, even though you changed nothing.
- Purge all caches as in Fix 2.
- Open the sitemap address in a private window and check for the newest post.
- If the sitemap now updates, the rewrite rules were the cause.
- If nothing changes, the rules were fine, and no harm was done — move on to Fix 6.
This fix feels too simple to work, and that is exactly why it is often skipped. Rewrite rules are rebuilt on save, and a rebuild clears the quiet corruption that follows plugin changes, host moves, and failed updates. It changes no content, no settings, and no addresses — it only refreshes the rule set. If permalink problems are showing up elsewhere too, such as pages returning not-found errors, our guide to WordPress permalink structure causing 404 covers the wider permalink faults that share this same root cause.
Fix 6: Check the New Content Is Published and Public
A sitemap lists public, indexable content. Before assuming the sitemap is broken, confirm the missing content actually qualifies for the list. A surprising number of stale-sitemap reports end here, with content that was never meant to appear.

- Open the missing post in the WordPress editor.
- Confirm its status is Published, not Draft, Pending, or Scheduled.
- Confirm its visibility is Public, not Private or Password Protected.
- Check the post’s SEO settings for a noindex instruction — a noindex post is deliberately kept out of search results and out of the sitemap.
- Check whether the post is excluded from the sitemap in your SEO plugin’s settings for that post.
- Check the post’s categories and tags: some sitemap settings exclude content in certain categories.
- Fix whatever you find, save the post, purge caches, and re-check the sitemap.
- If the post qualifies on every check and is still missing, move on to Fix 7.
Each check in this fix has a simple logic: the sitemap mirrors what search engines should find, and content that should not be found is correctly absent. A scheduled post will appear when its date arrives. A private post will never appear, and should not. The fix here is not to force such content into the sitemap, but to recognise when absence is correct — and to correct the setting when absence is a mistake, such as a noindex flag left on from a staging copy. If old content is showing in other places too, our guide to WordPress website showing old content covers the wider stale-content problem across pages, posts, and archives.
Fix 7: Check Your SEO Plugin Sitemap Settings
SEO plugins let you choose exactly which content types appear in the sitemap. A post type, taxonomy, or archive switched off in those settings vanishes from the sitemap, even though the content itself is live and public.
- Open your SEO plugin’s sitemap settings.
- Confirm the sitemap feature itself is switched on.
- Check the list of included post types — posts, pages, and any custom post types your site uses.
- Check the list of included taxonomies — categories and tags, if your plugin includes them.
- Look for an exclusion list, and check that your missing content is not listed there by accident.
- Check the settings for individual posts that were excluded one by one.
- Save any changes, purge all caches, and re-check the sitemap in a private window.
- If you changed an included post type, publish or update one post of that type to trigger a refresh, then check again.
Sitemap settings are usually configured once and forgotten, which is why a change months ago can cause confusion today. A post type added by a new plugin — a portfolio, a course, a product — will not appear in the sitemap until the SEO plugin is told to include it. The same applies to content imported from another site, which can arrive with exclusion flags set. Work through the settings slowly, one section at a time, and compare what is switched on with what your site actually publishes. The gap between those two lists is usually the answer.
Fix 8: Test for a Plugin Conflict
A plugin that alters rewrite rules, caching, or SEO output can freeze a sitemap without any visible error. Testing for a conflict means deactivating suspects one at a time and checking the sitemap after each change.
- Take a backup of your site before you start.
- List the plugins most likely to affect the sitemap: caching plugins, SEO plugins, redirection plugins, and security plugins.
- Deactivate the most likely suspect first — one plugin at a time.
- After each deactivation, purge caches and check the sitemap in a private window.
- If the sitemap updates, you have found the conflicting plugin. Check its settings for a sitemap or caching option, or contact the plugin’s support.
- If nothing changes, reactivate the plugin and move to the next suspect.
- Test during a quiet period, or on a staging copy if your host provides one, so visitors are not affected.
- Reactivate everything you deactivated, except the plugin you proved was at fault.
One at a time is the rule that makes this test work. Deactivating everything at once proves the cause is a plugin, but leaves you testing them all again to find which one. The patient version takes longer per step and finishes sooner overall. Pay special attention to having two plugins that both manage sitemaps or both manage caching — duplicate roles are the most common source of sitemap conflicts. If wordpress sitemap not updating began the same day a plugin was installed or updated, start with that plugin, even if it seems unrelated.
Fix 9: Check Robots.txt and the Sitemap Index
Your robots.txt file can point search engines to a sitemap address. If it points to an old address, search engines read the old sitemap while your live one updates unnoticed. The sitemap index — the master list that points to the individual sitemap files — deserves the same check.
- Open your robots.txt file by adding /robots.txt to your site address in a private window.
- Look for a line starting with “Sitemap:” and note the address it gives.
- Open that address and confirm it is the live sitemap you have been checking.
- If robots.txt points to a different address, update it to the live sitemap address, or remove the line if your SEO plugin manages robots.txt.
- Open the sitemap index itself and check that it lists the individual sitemap files for posts, pages, and other content types.
- Open one individual sitemap file from the index and confirm it lists recent content.
- If the index lists files that return errors, purge caches and resave permalinks as in Fix 5, then check again.
- After any change, re-check the index and one individual file in a private window.
Robots.txt does not control whether your sitemap updates — it controls which sitemap search engines are told to read. That distinction matters: a wrong robots.txt line makes the problem look like a stale sitemap when the real fault is a wrong pointer. Fix the pointer, and search engines start reading the fresh sitemap that was updating all along. If your SEO plugin manages robots.txt, edit it through the plugin, not by uploading a physical robots.txt file, which can cause the same override problem as the static sitemap file in Fix 4.
Fix 10: Check the CDN and Server Cache Rules
A content delivery network sits between your server and the world, and it can cache the sitemap for hours or days under its own rules — rules that your WordPress purge button cannot reach. Server-level caching, such as a host’s built-in page cache, can do the same.
- Sign in to your content delivery network’s dashboard, if you use one.
- Purge the cache for the sitemap address specifically, or purge everything if a single-address purge is not offered.
- Check the caching rules for XML files or for the sitemap address — a long cache lifetime for the sitemap keeps it stale.
- Set the sitemap address to bypass the cache, or to a short cache lifetime, if the dashboard allows it.
- Sign in to your hosting control panel and purge any server-level cache it provides.
- Check whether your host offers a cache exclusion list, and add the sitemap address to it.
- Wait a few minutes, then check the sitemap in a private window.
- Note the settings you changed, so you can explain them to your host if the problem returns.
Delivery networks are excellent for speed and terrible for stale sitemaps, because they are designed to serve stored copies. The sitemap is a small, fast file that changes often, so caching it aggressively buys almost no speed and costs freshness. Bypassing the cache for the sitemap address is the right trade-off on most sites. If you are unsure which cache layers your site has, ask your host — hosts can usually list them in one support reply, and knowing the layers makes every future cache problem easier.
Fix 11: Check Scheduled Tasks and Run a Fresh-Post Test
The final fix proves whether the sitemap updates at all. A fresh test post, published after every other fix, gives the sitemap a clean chance to include new content. The scheduled task check covers setups that rebuild the sitemap on a timer.

- In WordPress, go to Tools, then Site Health, and read any warnings about scheduled tasks or background jobs.
- If Site Health reports that scheduled tasks are not running, note the warning and contact your host — the task system is a hosting matter.
- Create a new test post with a distinctive title you will recognise in the sitemap.
- Publish the test post, then purge all caches as in Fix 2.
- Wait five minutes, then open the sitemap in a private window and search for the test post title.
- If the test post appears, your sitemap is updating, and the earlier missing content was held back by one of the causes in Fixes 1 to 10. Delete the test post.
- If the test post does not appear, note every fix you tried and contact your hosting provider or your SEO plugin’s support with that list.
- When you contact support, include the sitemap address, the test post title, and the time you published it — precise evidence gets faster answers.
The fresh-post test is the honest final verdict. It removes every doubt about old content, old caches, and old settings, because the test post is brand new and the checks are brand new too. A sitemap that includes the test post is a working sitemap. A sitemap that ignores a fresh post after all 11 fixes has a fault outside the settings you can reach, and the right next step is support — with the evidence this fix gathered. Do not keep changing settings in circles: if the test post fails, stop, gather the notes, and ask for help.

What to Avoid
- Do not run two SEO plugins at once — pick one, and let it own the sitemap.
- Do not upload a physical sitemap file to the site root — it overrides the live sitemap and freezes it.
- Do not purge only one cache layer and declare the fix failed — purge plugin, server, and network caches together.
- Do not force private, noindex, or draft content into the sitemap — its absence is correct.
- Do not edit robots.txt by uploading a physical file when your SEO plugin manages it.
- Do not keep changing settings in circles after the fresh-post test fails — gather your notes and contact support.
- Do not use nulled SEO or caching plugins — they are a security risk, and official plugins handle sitemaps properly.
- Do not judge the sitemap in a normal browser window — always check in a private window first.
Frequently Asked Questions
How long should a WordPress sitemap take to update after publishing?
In most setups, the sitemap reflects a new post within minutes of publishing, once caches are purged. If a new post is still missing after an hour and a full cache purge, one of the causes in this guide is at work. The fresh-post test in Fix 11 gives you a definite answer instead of more waiting.
Why is my new post live but not in the sitemap?
The usual reasons are a cache serving an old sitemap, the post being excluded or set to noindex, or the wrong sitemap being checked when two generators exist. Work through Fixes 1 to 3 first, then check the post’s own settings with Fix 6. Most cases of wordpress sitemap not updating for a single post end at one of those fixes.
Does WordPress create a sitemap automatically?
Yes. WordPress generates a sitemap on its own, and most SEO plugins replace it with their own version that offers more control. When an SEO plugin’s sitemap is switched on, that plugin’s sitemap is the live one. Fix 3 explains how to tell which generator is in charge on your site.
Should I submit my sitemap to search engines again after fixing it?
Once the sitemap itself is updating correctly, re-submitting it through your search engine’s webmaster tools can speed up re-reading, but it is not required for the fix. Fix the sitemap first, confirm it with the fresh-post test, and then re-submit if you want search engines to pick up the fresh version sooner.
Can a caching plugin stop my sitemap from updating?
A caching plugin can serve an old copy of the sitemap, which looks exactly like a sitemap that is not updating. The sitemap itself is usually fine underneath. Purging all cache layers, as in Fix 2, and excluding the sitemap address from aggressive caching, as in Fix 10, solve the caching side of the problem.
What if my sitemap updates for posts but not for pages?
That pattern points to the SEO plugin’s sitemap settings, where post types are included one by one. Open the plugin’s sitemap settings with Fix 7 and confirm that pages are switched on. A page type added by another plugin needs the same check — it will not appear until the SEO plugin is told to include it.
Conclusion
When wordpress sitemap not updating leaves new content off the map, start with the private-window check and a full purge of every cache layer. Then confirm which generator owns the sitemap, look for a static file in the way, and check that the missing content is public, included, and not set to noindex. Finish with the fresh-post test — a new post appearing in the sitemap is the proof that counts. Your sitemap is the map search engines use to find your work, and keeping it fresh is worth these eleven checks.
