Technical SEO · November 14, 2026 · 8 min read
Why Your Sitemap Isn't Showing New Blog Posts
A sitemap missing new posts is usually a cached copy, a scheduler that never fired, or an excluded post type. Prove which one from the response headers.
By FluxWriter
A sitemap not updating with new posts is almost never a bug in your SEO plugin. In most cases the plugin wrote a correct file and something in front of it is serving an older copy, or the post type was quietly excluded before you ever published. The chain has four common breaking points, and each one leaves a different fingerprint in the HTTP response. This walks the chain in order and shows how to prove which link is broken instead of guessing at settings.
Cache Is The First Suspect, Not The Plugin
Your sitemap is a URL like any other. If you run a page cache, a CDN, or both, that URL can be stored and served exactly the way a product page is. You publish a post, the plugin regenerates the file on the origin, and every request from outside still gets the version cached before the post existed.
This is the most common cause and also the easiest to misread, because logged-in administrators usually bypass the page cache. You open the sitemap in the browser you are already logged into, the new post is sitting there, and you conclude the sitemap is fine. Open the same URL in a private window and it can be a week behind.
The arithmetic is worth doing once. Publish three times a week behind a seven-day cache and the public copy can be missing three posts at any moment. Publish daily and it can be missing seven.
Most caching layers let you exclude a path from caching, and a sitemap is a good candidate. The file is small and requested a handful of times a day, so there is little to gain by holding it. If you run a CDN with a broad cache-everything rule, assume .xml is caught by it until you have checked.
wp_cron Only Fires When Someone Visits The Site
WordPress does not ship with a real scheduler. Tasks are queued and run on a page load, so on a site with 30 visits a day a job scheduled for 2am may not run until someone wanders in at 9. With steady traffic the difference is invisible. On a quiet brochure site it is hours.
Whether this touches your sitemap depends on your plugin. Some regenerate the file inline when you hit publish, in which case the scheduler is irrelevant. Others rebuild it on a queued job, or defer the search-engine notification to one. Where that is how yours works, a stalled queue means a stale file even though nothing looks misconfigured.
There is a sharper version of this failure. Many hosts set the DISABLE_WP_CRON constant and replace the built-in scheduler with a real server cron job, which is the correct setup. If that job was never created, or was removed during a migration, every scheduled task stops silently: scheduled posts miss their publish time, backups stop, and the sitemap freezes. A plugin that lists overdue scheduled events settles this in about a minute.
The Post Type Or The Post Itself Is Excluded
Sitemap inclusion in the major SEO plugins generally follows the same setting that controls whether a content type is indexable. Turn a post type off and it leaves the sitemap along with everything else. This matters most where the blog does not run on the standard post type. Agency builds often use a custom type called Articles, Insights or Resources, and a settings reset can drop it without anyone noticing for months.
The same logic applies per post. Setting an individual post to noindex normally pulls it from the sitemap too, because a sitemap is a list of URLs you want crawled and the two settings would otherwise contradict each other. Check the SEO panel on the post that went missing before you check anything global.
Then there is the boring category. Drafts, private posts, password-protected posts and posts still sitting in the future are all legitimately absent. So are posts that hit the missed-schedule state, where WordPress recorded a publish time, failed to fire the job, and left the post unpublished with a past date. That is the scheduler problem wearing a different hat.
Generation Times Out Once The Archive Gets Big
The sitemap standard caps a single file at 50,000 URLs or 50MB uncompressed, and index files exist so large sites can split across several children. Plugins typically split far below that, often in the low thousands of URLs per file, so most sites never approach the ceiling.
The limit that bites first is time, not size. Building a sitemap section means querying posts and resolving a modified date for each one, and on a large archive with poorly indexed database tables that can run long. PHP installs commonly ship a 30-second execution ceiling, and web servers often sit at a 60-second gateway timeout in front of that. Cross either one and generation dies part-way, which produces a truncated file, a 500, or a stored file that stops changing from the date the failures began.
The tell is specific. The sitemap index still looks healthy and still lists its children, but one child file is frozen at an old date, returns a 404, or takes an absurd time to respond. Time the request rather than eyeballing it: a child file that takes ten seconds to return is already failing for some crawlers.
Fetch The File The Way A Crawler Does
Stop opening the sitemap in your logged-in browser. Fetch the headers from outside instead, with curl -I https://yourdomain.com/sitemap.xml, and read four fields: age, cache-control, last-modified, and whatever cache-status header your CDN adds.
The age header settles the cache argument. It is the number of seconds the copy you just received has been sitting in a shared cache, so an age of 41290 is a copy about eleven and a half hours old. Anything above zero means a cache is in play, and cf-cache-status: HIT or x-cache: HIT says the same thing more loudly. If age is zero and the file is still wrong, the origin is the problem.
Here is how the common responses map onto causes. The fix times are rough figures from typical setups rather than measurements.
| What the response shows | Most likely cause | Rough time to fix |
|---|---|---|
age above zero, cache status HIT |
Shared cache or CDN holding an old copy | Minutes |
age: 0, last-modified days old |
Origin file is stale, so scheduler or regeneration | Under an hour |
| 404 on a child file the index lists | Generation failing or the file was removed | Under an hour |
| Correct fresh file, post genuinely absent | Post type or the individual post is excluded | Minutes |
| Ten-second response or a 500 | Generation timing out on archive size | Half a day |
| File correct, Search Console last read weeks ago | Nothing broken on your side, just fetch cadence | No fix needed |
That last row deserves a warning. The Sitemaps report in Search Console shows when the file was last read, and on a small site that date can lag by days or weeks without anything being wrong. Do not tear up a working configuration over it.
A Missing Sitemap Entry Is Rarely The Whole Reason A Post Is Unindexed
A sitemap is a discovery aid, not an instruction. Search engines do not commit to crawling what a sitemap lists, and they routinely find pages that appear in no sitemap at all. If a new post is linked from your blog index and that index is linked from your navigation, a crawler arriving at your homepage has a path to it regardless.
So the reason to fix a stale sitemap is not that it alone is suppressing your rankings. It is that a stale sitemap is a symptom. If the file froze because the scheduler stopped, your scheduled posts are probably not publishing either. If a cache rule froze it, that rule is likely holding other pages too.
Once the file is genuinely correct, submit the sitemap URL in Search Console and Bing Webmaster Tools so both know where to look. IndexNow gives you a second, faster notification path to the engines that participate in it, which includes Bing and Yandex but does not include Google. Neither route buys you indexing. They shorten the gap between publishing and discovery, and discovery is the only part of this you control.
FAQ
How quickly should a new post appear in my sitemap?
In most setups the file updates the moment you hit publish, because the plugin regenerates it on save. If the copy on the origin is correct and the public copy is not, you are looking at a cache rather than a delay. If the origin copy is also wrong after a few minutes, look at the scheduler next.
Does resubmitting the sitemap in Search Console make Google recrawl faster?
Resubmitting asks Google to fetch the file again, which is worth doing once after you have fixed a genuine fault. It does not commit Google to crawling every URL in it, or to any timeline, and resubmitting an unchanged file repeatedly achieves nothing.
My post is in the sitemap but Search Console says "Discovered - currently not indexed". Is the sitemap still to blame?
No. That status means Google found the post but has not indexed it yet, so the sitemap did its job. The hold-up sits on the crawl and selection side, which tends to track site-wide signals such as internal linking, page quality and how much of the site gets crawled at all. Regenerating the sitemap will not change it.
The Practical Takeaway
Work the chain in order and stop at the first thing that fails. Fetch the sitemap with curl from outside your own session and read the age and last-modified headers, because that one request tells you whether you are debugging a cache or an origin. If it is cache, exclude the sitemap paths from caching and purge. If the origin is stale, check for overdue scheduled events before touching plugin settings. If the file is fresh and the post is genuinely absent, check that post's own SEO panel and its post type. Do that today: run curl -I against your sitemap URL and write down the age value before you change a single setting.