How to Confirm Your XML Sitemap Lists New Blog Posts
You hit Publish, shared the link, and moved on. That moment feels like the finish line, but crawlers may not know the page exists yet. That matters for your XML sitemap: new blog posts only help discovery if they actually appear in the file crawlers fetch.
To confirm, open your sitemap index, find the post sitemap, and search it for the new slug. Check that the URL and its last-modified date are correct, then confirm the URL in Google Search Console.
Most tutorials stop at creating a sitemap. Few show how to check that today's post made it in, and posts can go missing quietly. For example, a post goes live, but a cached sitemap URL keeps serving the old list, so the new URL is absent from what crawlers download.
This guide gives you a repeatable five-point check called PEFID: Present, Exact, Fresh, Indexable, and Discovered. You'll also learn which sitemap tag Google trusts and which two it ignores. Once the sitemap checks out, you can get Google to discover new posts faster.
What Should a New Post Look Like in Your XML Sitemap?
Each new post should appear as its own url entry with an exact loc (the page address) and an accurate lastmod (the last-modified date). If either value is missing or wrong, crawlers get a misleading signal.
An XML sitemap is a machine-readable file that lists the URLs you want search engines to crawl. A sitemap index is a parent file that links to several child sitemaps, such as one for posts and one for pages. Lastmod is the tag that records when a page's content last changed.
Think of the sitemap index as a library's catalog and each child sitemap as one drawer of cards. Your new post needs its own card in the right drawer, with the correct address and date. For more background, see our XML sitemap basics.
A healthy entry needs only two tags inside the url element:
| Line | What it means |
|---|---|
| <url> | Opens one entry for one page. |
| <loc>https://example.com/blog/new-post/</loc> | The full canonical URL of the post. |
| <lastmod>2026-11-12T09:30:00+00:00</lastmod> | The last change, in W3C datetime format. |
| </url> | Closes the entry. |
The changefreq and priority tags are left out on purpose. Google ignores both, so they add bulk without adding signal.
To find your sitemap, check these locations in order:
- robots.txt: Open yourdomain.com/robots.txt and look for a line that starts with Sitemap:.
- WordPress core: /wp-sitemap.xml
- Yoast or Rank Math: /sitemap_index.xml
- Blogger: /sitemap.xml
If you'd rather skip the hunt, BloGoose locates your XML sitemap automatically when it crawls your site during setup.
How Do I Check That My XML Sitemap Includes My New Blog Posts?
Open your sitemap index, open the post sitemap, and search it for the new slug. Then confirm the URL in Google Search Console.
To verify that a new blog post is in your XML sitemap, open the sitemap index and click the child sitemap that holds posts. Press Ctrl+F (Cmd+F on Mac) and search for the post's slug. Confirm that the loc value matches the post's canonical URL exactly, including https, www, and any trailing slash. Confirm that lastmod uses W3C datetime format and matches the publish date. Make sure the page carries no noindex tag and isn't blocked by robots.txt. Finally, check the Sitemaps report in Google Search Console and run URL Inspection on the post.
You'll need: a browser, the post's canonical URL, and Search Console access. The full check takes about five minutes.
- Present: the slug appears in the post sitemap.
- Exact: loc matches the canonical URL.
- Fresh: lastmod matches the publish date.
- Indexable: no noindex tag and no robots.txt block.
- Discovered: Search Console confirms the URL.
1. Present: Find the Slug (1 minute)
Open the sitemap index, then click the post sitemap. Press Ctrl+F and type the slug. You should see one highlighted match inside a url entry.
Pro tip: If the slug is missing, purge the page cache or CDN cache for the sitemap URL after publishing, then reload the file.
2. Exact: Match the Canonical URL (1 minute)
Compare the loc value with the canonical tag in the post's page source. Protocol, www, and trailing slash must all match. Learn how to fix canonical URL mismatches.
3. Fresh: Check Lastmod (30 seconds)
Confirm lastmod reads like 2026-11-12T09:30:00+00:00 and matches the publish date. Lastmod is the tag Google trusts: Google Search Central documentation says Google uses lastmod when it is consistently and verifiably accurate, and ignores priority and changefreq.
4. Indexable: Rule Out Blocks (1 minute)
View the page source and search for "noindex." Then open robots.txt and confirm no Disallow rule covers the post's path. See how the noindex robots meta tag works.
Here's where most audits stop too early:
5. Discovered: Confirm in Search Console (2 minutes)
Open Search Console, click Indexing, then Sitemaps. The status should read Success with a recent read date. Then paste the post URL into URL Inspection to see whether Google knows it. Clean sitemaps also help Google spend crawl budget on pages that matter.
If any check fails, the next question is why the post never made it in.
Why Is My New Post Missing From the Sitemap?
A new post usually goes missing from your sitemap for one of five reasons: a stale cached sitemap, a noindex tag, a post type excluded in plugin settings, the post still sitting in draft or scheduled, or a site URL setting that outputs http or the wrong host. Each cause has a single fix.
| Symptom | Cause | Fix | Where to fix it |
|---|---|---|---|
| Post is live, but the sitemap shows old entries only | Stale cached sitemap | Purge the cache | Caching plugin or CDN on any platform |
| Post is live but never listed | Post has noindex | Remove the tag, because sitemap plugins drop noindex URLs | Yoast or Rank Math per-post settings, or Blogger custom robots tags |
| Every post of one type is absent | Custom post type excluded | Enable it in sitemap settings | Yoast or Rank Math content type settings |
| URL is absent or returns 404 | Post still in draft or scheduled | Publish it | Post editor on any platform |
| <loc> shows http or a non-canonical host | Wrong site URL setting | Fix the site URL setting | WordPress Settings > General, or the Blogger HTTPS setting |
- WordPress core sitemap: Best for lean sites that publish standard posts and pages and need no extra configuration.
- Yoast or Rank Math: Best for publishers who need per-post and per-type control. That control is also how pages get excluded by accident.
- Blogger: Best for solo bloggers who want a sitemap generated automatically with almost no settings to manage.
For example, suppose your recipes live in a custom post type that your plugin excludes. You enable that type in sitemap settings, reload the file, and rerun the Present check.
After each fix, rerun Present and Fresh to confirm the URL appears with the correct lastmod. An engine that publishes and then verifies inside one workflow removes this manual loop.
Sitemap FAQ for New Blog Posts
These answers cover the sitemap questions the steps above leave open, starting with the most common myth.
Does resubmitting my sitemap speed up indexing?
No. Resubmitting an unchanged sitemap does not make Google crawl faster, and Google Search Central has deprecated its sitemap ping endpoint. Two signals actually help. The first is an accurate lastmod. The second is a crawl request through the proper channel, such as URL Inspection in Search Console or the workflow to request a crawl via the Indexing API. The catch? Bumping lastmod on every URL with each build trains Google to ignore it. Change lastmod only when a post's content actually changes.
Do changefreq and priority matter?
No. Google Search Central states that Google ignores both changefreq and priority. Spend your effort keeping <loc> and lastmod accurate instead of tuning values Google discards.
What is the sitemap size limit?
Under the sitemaps.org protocol, each sitemap file can hold up to 50,000 URLs or 50 MB uncompressed. Larger sites split their URLs across several files and list those files in a sitemap index.
How long until a new post appears in the sitemap?
Usually immediately. Plugin and WordPress core sitemaps generate on request, so delays almost always come from a page cache or CDN serving an older copy. Purge the cache and reload the file.
Let BloGoose Find Your Sitemap and Plan the Next 30 Days
Your sitemap is the receipt that proves each post shipped and can be discovered. Make two habits standard: purge your cache, then run the PEFID check on every new post before you call it published.
The same discovery path can also drive your planning. When you enter your domain in the BloGoose setup wizard, it locates your sitemap through robots.txt and common CMS paths, inspects your published pages, and detects your CMS. This mirrors how Google finds your URLs.
From that crawl, BloGoose generates context files that shape a 30-day content calendar.
Let BloGoose crawl your sitemap and plan your next 30 days of posts. See BloGoose pricing to choose your plan, and every post you publish becomes a verified asset that search engines can find.