Pages Removed From Your Sitemap: What to Do Next
When pages are removed from a sitemap, the first job is to find out whether they left the sitemap or left the website. Request a handful of the missing URLs directly: if they return 200 and are still linked internally, they will generally stay indexed, and if they return 404, 410 or a redirect, the sitemap is only reporting a change that happened to the pages.
Sitemaps are generated by the CMS, a plugin or a build step, so they change whenever those change. Nobody edits sitemap.xml by hand to drop two hundred product URLs; a deploy, a setting or a stock update does it for them.
Step 1: work out what actually disappeared
If you do not have yesterday's list of URLs, Search Console can help. The Sitemaps report shows the number of discovered URLs for each submitted sitemap, and a drop there is your first confirmation. If you saved a copy, a two-line diff gives you the exact URLs:
curl -s https://example.com/sitemap.xml | grep -o '<loc>[^<]*</loc>' | sort > today.txt
comm -23 yesterday.txt today.txt
For a sitemap index, run the same command against each child sitemap. Then take five to ten of the missing URLs and check them individually.
Step 2: read the status codes
| Response | What it tells you | Next move |
|---|---|---|
200 |
Page exists, only the sitemap entry went | Find the exclusion rule (step 3) |
301 / 302 |
URL moved | Confirm the destination is in the sitemap |
404 / 410 |
Page deleted | Decide whether it should come back or be redirected |
200 with noindex |
Page exists but is excluded from indexing | Check whether that noindex was intended |
Also check whether the pages are still linked from menus, categories or related-content blocks. A page with no sitemap entry and no internal links is effectively orphaned. Our guide on how to check if a page is indexed covers URL Inspection and the limits of site: queries.
Step 3: find the cause
The most frequent one is a deploy or migration that replaced the sitemap generator, or reset its configuration. Custom post types, taxonomies or paginated archives drop out because the new setup never included them.
Plugin settings come next. In Yoast SEO, each content type has a "Show [type] in search results" toggle under Settings, and turning it off removes that type from sitemap_index.xml. Rank Math has an equivalent "Include in Sitemap" switch per post type in its Sitemap Settings. One click there can take out hundreds of URLs.
On shops, check whether a setting or plugin hides out-of-stock or unpublished products, since those URLs will move in and out of the sitemap with stock levels. On any CMS, a bulk change to draft or private status has the same effect.
Then there is noindex. Well-behaved generators leave noindex pages out of the sitemap, so a removal is often the first visible sign that one was added by mistake. Finally, slug or structure changes without redirects replace the old URLs with new ones, which looks like removals plus additions in the same diff.
Step 4: judge the SEO impact honestly
A sitemap helps discovery; it is not the index. A page that still returns 200 and is linked internally normally keeps its indexing and rankings. What it can lose is how often it is recrawled, so edits take longer to register. New pages, and pages several clicks deep, are where a missing sitemap entry hurts most, because internal links may not get them discovered quickly.
The bigger value is diagnostic. The removal itself is often minor, but whatever caused it (a noindex, a deletion, a broken template) usually is not.
Step 5: fix and verify
Restore the page or 301 it to the closest relevant URL. Remove the exclusion, whether that is the plugin toggle, the noindex or the generator rule. Clear any cache in front of the sitemap, open the file in a browser to confirm the URLs are back, and resubmit it in Search Console. Then look at titles, canonicals and H1s on the same templates, because a deploy that changed the sitemap may have changed those too. Only canonical, indexable, 200 URLs belong in the file, as set out in our XML sitemap best practices.
Catching it the day it happens
All of this is quick once you know URLs went missing. The hard part is noticing. Deltio reads each site's sitemap on a daily cycle, compares it with the previous check, and sends an alert to that site's Slack channel and email when URLs are removed. It checks the pages as well, including noindex, canonicals, titles and robots.txt, so the cause often shows up in the same alert batch. That is the habit described in how to monitor client websites for changes. It is a daily check, so a removal this afternoon is reported on the next cycle rather than instantly.
Frequently asked questions
- Is it a problem if deleted pages are removed from the sitemap?
- No, that is the correct behaviour. A sitemap should only list pages that return 200 and are meant to be indexed. The only question is whether the deletion was intentional and whether valuable URLs were redirected rather than left as 404s.
- Should I leave removed URLs in the sitemap so Google notices the 404?
- Generally no. Google will recrawl known URLs and see the 404 or 410 on its own. Keeping dead URLs in the sitemap adds errors to the Page indexing report and makes the file a less reliable signal. The exception is a short-term migration sitemap listing old URLs to speed up discovery of their redirects.
- How quickly does Search Console reflect a changed sitemap?
- The Sitemaps report updates when Google next fetches the file, which varies by site. Resubmitting prompts a fetch but does not guarantee immediate processing or recrawling of the listed pages, so allow a few days before reading much into the discovered URL count.
- Can the number of URLs in a sitemap change without any real change to the site?
- Yes. Some generators paginate sitemaps by a fixed number of entries, and caching layers can serve an old or partially built file. Always compare actual URL lists, not just totals, before concluding that pages were removed.
- How much does sitemap monitoring cost with Deltio?
- Sitemap monitoring is included in every plan. Starter covers up to 50 sites and 5,000 URLs for £24 / €29 / $31 a month, or £20 / €24 / $26 a month billed annually. Professional (200 sites) and Enterprise (500 sites) start at £49 and £119 a month respectively. All plans come with a 14-day free trial.