XML sitemap inclusion
XML sitemap inclusion shows whether a page’s URL is currently listed in the site’s XML sitemap. This is a useful support signal because XML sitemaps help search engines discover important URLs and understand which pages the site is presenting for crawling and indexing.
This is not usually a hard indexing switch on its own, but it still matters. If a page drops out of the XML sitemap unexpectedly, it may become less visible as a discovery candidate, especially on larger sites or deeper pages.
What it is
An XML sitemap is a machine-readable file that lists URLs a site wants search engines to know about.
This field checks whether the page URL appears in that sitemap.
If the value is TRUE, the page is included in the XML sitemap. If the value is FALSE, it is not.
SEOlerts monitors this as a boolean because the practical question is simple: is the page being surfaced in the XML sitemap or not?
Why it matters
XML sitemaps are a discovery support mechanism.
They help search engines find URLs more efficiently, especially when pages are new, deep in the site structure, lightly linked internally, or part of large websites where discovery can take time. Inclusion can also reinforce that the page is one the site considers important enough to surface for crawling.
A page does not need to be in the XML sitemap to be indexed, and inclusion alone does not guarantee indexing. But sitemap presence still contributes useful crawl and discovery context, which is why changes here are worth monitoring.
What can go wrong if unchecked
If a page disappears from the XML sitemap unexpectedly, search engines may have one less signal pointing them towards that URL.
Common causes include:
- sitemap generation rules changing
- a CMS or SEO plugin altering which pages are included
- canonical or indexability logic removing the page from the sitemap
- migrations or URL changes leaving pages out
- template or taxonomy rules affecting whole groups of URLs
- page status or metadata changes causing auto-exclusion
If this goes unnoticed, important pages may no longer be surfaced consistently for discovery. On larger sites, that can slow down recrawling, reduce visibility for newly updated URLs, or make it harder to spot which pages the site intends search engines to prioritise.
The reverse matters too. If a page becomes included unexpectedly, it may now be treated as a page the site wants crawled and indexed. That may be correct, but it may also reveal that low-value or non-indexable URLs are being exposed in the sitemap.
Why monitoring it matters
Monitoring XML sitemap inclusion helps you catch changes in crawl support that are easy to miss when looking only at the page itself.
A page can still return 200, remain indexable, and look perfectly healthy while quietly dropping out of the XML sitemap. Equally, a page can appear in the sitemap when it should not be there. This field gives a simple, practical signal of whether sitemap logic has changed for that URL.
It is especially useful after CMS updates, sitemap generator changes, migrations, canonical updates, indexing changes, or template edits that can affect whole classes of pages.
What an alert may mean
An alert means the page’s sitemap inclusion state has changed.
If the value changes from TRUE to FALSE, the page is no longer listed in the XML sitemap. In practice, that could mean:
- sitemap generation rules changed
- the page is now excluded because of indexability or canonical logic
- the page URL changed and the old URL dropped out
- a migration or CMS change affected sitemap output
If the value changes from FALSE to TRUE, the page is now listed in the XML sitemap. That could mean:
- the page has become eligible for inclusion
- sitemap rules were updated
- a previous exclusion was removed
- the site is now surfacing the page for discovery
The alert is not proof of an SEO problem by itself. It is a sign that the page’s discovery support has changed and should be checked against the intended sitemap strategy.
What to check next
Start by confirming whether the page should be in the XML sitemap at all.
Then review:
- whether the page is indexable
- whether the page canonicalises to itself or elsewhere
- whether the current URL is the correct one for sitemap inclusion
- whether the change affects one page or a wider group of URLs
- recent CMS, sitemap, migration, or SEO configuration changes
If the page has dropped out unexpectedly, check whether a noindex directive, canonical change, status code issue, or URL rewrite caused the exclusion. If the page has appeared unexpectedly, confirm that it is a page you actually want search engines to discover and index.
It is also worth reviewing related fields such as indexability state, canonical href, status code, and robots directives, because sitemap inclusion usually makes the most sense when those signals are aligned.
Key takeaway
XML sitemap inclusion shows whether a page is currently listed in the site’s XML sitemap. Monitoring it helps you catch changes in discovery support, sitemap logic, and page eligibility before they create wider crawl or indexing confusion. An alert means the page’s sitemap inclusion status has changed, and that change should be reviewed to confirm it matches the intended SEO setup.
