WordPress Sitemap Not Updating After Publishing? 9 Fixes for Missing Posts (2026)
Quick answer: If a new WordPress post is absent from your sitemap, first confirm that you are viewing the sitemap actually generated by the site, not an old cached file or a different plugin’s index. Check that the post is published and publicly indexable, then test the exact post URL. Updating a sitemap helps discovery but does not guarantee a Google ranking.
Updated 5 November 2026 · Independent troubleshooting guide. Screens and plugin settings differ by version.
1. Find out which sitemap your site actually uses
Open the sitemap address shown in your site’s robots.txt and compare it with the one submitted in the Google Search Console Sitemaps report. Common WordPress paths include /wp-sitemap.xml for the built-in sitemap and /sitemap_index.xml for some SEO plugins. A site can have more than one address, and an old address may redirect or display a different result.
- Open
https://yourdomain.com/robots.txtand locate anySitemap:line. - Open each candidate sitemap and verify whether it contains links to post or page sub-sitemaps.
- In Search Console, compare the exact submitted URL against the live index, including the domain, protocol and any subdirectory.
- Do not assume that a browser cache view is the same XML Google fetches.
2. Confirm the post is really published
In WordPress, open Posts → All Posts and check that the article says Published, not Draft, Scheduled, Private or Pending. Check the publication date and the permalink. A post scheduled for a later date normally should not appear as a public article today.
Then visit the post link in a signed-out or private window. It should load without login, show the correct article, and return a normal successful page response. If it returns a 404 or redirects to a different post, fix that before investigating the sitemap.
3. Check for noindex and unwanted canonical URLs
Many sitemap generators omit content that is marked noindex. Inspect the post’s SEO settings and the rendered page source for a robots meta tag or X-Robots-Tag response header. Check the canonical link: it should generally point to the intended public post URL rather than another article, a category, or the homepage.
Never remove a legitimate noindex from pages that are intentionally private or low-value. The point is to make sure an important, public article is not excluded accidentally.
4. Clear the right caches without changing everything
A WordPress page cache, host cache, CDN or SEO-plugin sitemap cache may show an outdated XML response. Purge the specific sitemap URL and any generated post sitemap first. If necessary, clear the plugin’s documented sitemap cache or regenerate its index.
- Compare the sitemap in a normal window and a private window.
- If you have a CDN, purge the sitemap paths after checking its cache rules.
- Check whether a security or caching plugin serves a static XML file that never updates.
- Avoid adding random query parameters to the sitemap submitted to Google as a permanent fix.
5. Inspect the post type and sitemap exclusions
Some SEO tools allow entire post types, individual posts, categories or taxonomies to be excluded from sitemaps. Verify the new item is a regular WordPress post and not a private custom post type. Check that your sitemap configuration includes posts. Where there is a manual exclusion list, verify the post ID or slug is not present.
6. Rule out conflicting SEO plugins
If two plugins both advertise sitemap generation, identify which one is responsible for the submitted URL. Do not change or disable production plugins blindly. Take a backup, inspect plugin settings and use a staging site for changes that might affect canonical tags, redirects or metadata.
7. Check the sitemap response itself
A valid sitemap must be publicly fetchable and properly formatted. Look for a 200 HTTP response, an XML document rather than an HTML login page, and links to reachable pages. A 200 response alone is not enough: a WordPress error printed into the XML can also make it unusable. Inspect Search Console’s last-read status and reported sitemap errors.
8. Use URL Inspection for the missing article
Paste the full article URL into Search Console URL Inspection. Compare the indexed information with Test Live URL. If the page is indexable and the canonical is correct, you can request indexing. Repeating the request several times will not make it happen faster; Google’s own guidance says crawling can take days or weeks.
9. Document the fix and confirm it persists
- Write down the sitemap index URL and the number of article URLs it contains.
- Record one previously missing post and confirm its exact permalink now appears.
- After publishing another article, verify whether the count or relevant child sitemap updates.
- Record the Search Console sitemap status and last-read date; these are not the same as the publication date.
- Review errors again after the site or plugin cache has naturally refreshed.
What if the post is in the sitemap but Google still has not indexed it?
That is a different problem. A sitemap helps Google discover URLs; indexing is a separate decision. Investigate accessibility, canonicalization, duplicates, usefulness and indexing reports rather than endlessly rebuilding the sitemap. Read our Google indexing troubleshooting guide.
Frequently asked questions
Is wp-sitemap.xml always the sitemap I should submit?
No. WordPress includes a core sitemap, but an active SEO plugin may take over. Submit and maintain the actual live sitemap your site uses.
Will removing and resubmitting a sitemap force indexing?
No. Google treats sitemap submission as a discovery hint, not a guaranteed indexing or ranking command.
Does a changing sitemap URL count prove Google has found the post?
No. Verify the article in the XML, then use Search Console to evaluate crawling and indexing separately.
Official references
- WordPress Developer Resources: WP_Sitemaps
- Google Search Central: Build and submit a sitemap
- Google Search Console: Sitemaps report
