HTML sitemap inclusion
HTML sitemap inclusion shows whether a page’s URL appears in an HTML sitemap, where the site uses one. This is generally a support or helper field rather than a major SEO control, but it can still be useful for spotting structural changes in how pages are exposed for discovery.
An HTML sitemap is aimed more at users and general crawl support than at direct indexing control. Even so, a change in inclusion can reveal that a page has been added to or removed from an important navigational layer.
What it is
An HTML sitemap is a normal web page that lists important URLs on the site in a browsable format.
This field checks whether the page URL appears in that HTML sitemap.
If the value is TRUE, the page is listed in the HTML sitemap. If the value is FALSE, it is not.
SEOlerts monitors this as a simple yes-or-no signal. In the example here, the stored value is FALSE, meaning the page was previously not included.
Why it matters
HTML sitemaps are not as central to technical SEO as XML sitemaps, canonicals, or robots directives, but they can still help with discovery and site structure.
They may provide:
- an extra internal link path to important pages
- a browsable overview of site sections for users
- support for crawl access on larger sites
- a simple fallback navigational layer
Because of that, inclusion can matter as a supporting signal. If a page is present in an HTML sitemap, it may be easier for users and crawlers to reach through that additional route.
What can go wrong if unchecked
If a page drops out of an HTML sitemap unexpectedly, it may lose one source of internal discovery and structural support.
Common causes include:
- the HTML sitemap being regenerated differently
- changes to template or CMS logic
- page eligibility rules changing
- migrations or URL changes leaving pages out
- sections being removed from the HTML sitemap without review
If this goes unnoticed, the practical impact is usually limited compared with more critical fields, but it can still point to wider structural drift. On sites that rely on HTML sitemaps as a secondary navigation layer, important pages may become less visible or less connected.
The reverse can matter too. If a page appears in the HTML sitemap unexpectedly, it may now be exposed through a user-facing navigational page when that was not intended.
Why monitoring it matters
Monitoring HTML sitemap inclusion helps you catch changes in secondary discovery paths without needing to review sitemap pages manually.
This is especially useful on sites that still use HTML sitemaps as part of their information architecture or internal linking strategy. A small template or CMS change can alter the sitemap output for many URLs at once.
As a helper field, it is best used alongside XML sitemap inclusion and internal link monitoring rather than as a standalone SEO health check.
What an alert may mean
An alert means the page’s inclusion in the HTML sitemap has changed.
If the value changes from FALSE to TRUE, the page is now listed in the HTML sitemap. In practice, that could mean:
- the page was added intentionally
- sitemap generation rules changed
- a broader section of the site is now being exposed through the HTML sitemap
If the value changes from TRUE to FALSE, the page is no longer listed. That could mean:
- the page was removed intentionally
- sitemap logic changed
- a migration or template update affected the HTML sitemap output
- the page may have lost a secondary internal discovery path
The alert is not automatic proof of a problem. It is a sign that the page’s presence in the HTML sitemap has changed and should be checked against the intended site structure.
What to check next
Start by confirming whether the site uses an HTML sitemap and whether the page should appear in it.
Then review:
- whether the change was intentional
- whether the page is still important enough to include
- whether the linked URL in the HTML sitemap is correct
- whether the change affects one page or a wider section
- recent CMS, template, or migration changes that may explain it
It is also worth checking related fields such as XML sitemap inclusion, internal link count, navigation links, and indexability state. A change in HTML sitemap inclusion may reflect a broader shift in how the page is linked and surfaced across the site.
Key takeaway
HTML sitemap inclusion shows whether a page appears in a user-facing HTML sitemap, where one exists. Monitoring it is useful as a support field because it can reveal changes in secondary discovery paths and shared site structure. An alert means the page’s HTML sitemap presence has changed, and that change should be reviewed to confirm it is intentional and appropriate.
