Respond to sitemap availability, membership, and quality issues

Investigate unavailable files, missing pages, invalid members, limits, and lastmod values.

Last checked 21 August 2026

Open Sitewide Checks or the incident and identify the exact result, severity, and evidence before changing the site. Sitemap availability, membership, member validity, file limits, and date quality have different causes and repercussions.

Sitemap unavailable or unparseable

Sitemap unavailable or unparseable is Warning. It opens only after TechDash previously completed a usable walk. A website that has never exposed a usable sitemap stores a quiet no-baseline Good result because there is no prior successful sitemap to lose.

TechDash does not follow redirects. Check every robots.txt starting URL, or /sitemap.xml when none is declared, then check each child.

Look for redirects, authentication, HTTP errors, rate limits, timeouts, HTML returned as 200, unrecognized XML, malformed locations, unreadable .gz files, and failed children.

A reachable root does not make the complete tree usable. One failed child leaves the walk incomplete and queued for retry. Loss of a working sitemap can slow discovery of new and updated URLs, although internal links may still expose them.

The last complete, usable sitemap baseline is sticky. An unavailable, partial, or repeatedly failing walk does not clear its URL count or samples. The Sitemap URLs row can therefore continue showing the last successful count while this current availability check fails.

URLs missing from sitemap

URLs missing from sitemap is Warning. It is evaluated only after the full tree is usable and complete. The incident lists enabled monitored URLs not found after normalization. TechDash does not open it while a file failed or the walk is catching up.

For each URL, confirm it should be indexable, search the complete tree, compare scheme, host, path, and trailing slash, and inspect the generator's CMS, locale, product, or canonical rules. Re-add it only if inclusion is intended.

Sitemap membership helps discovery and does not guarantee indexing. Do not add redirected, duplicate, noindex, or error pages merely to clear an incident. A deliberate omission can be benign for account, checkout, duplicate, or retired pages. If monitoring should stop, remove the page from Monitored Pages only after confirming that decision.

Non-indexable URLs in sitemap

Non-indexable URLs in sitemap is a functional Warning check. After a complete walk, TechDash intersects found monitored sitemap members with their latest stored page snapshots. It fails when a listed monitored URL:

  • Has noindex in its indexability state, robots meta, or X-Robots-Tag
  • Returns an HTTP status outside 2xx and 304

Evidence lists each URL and reason, such as https://example.com/private (noindex) or https://example.com/broken (HTTP 503).

For an important page, remove noindex or repair its HTTP failure. Otherwise, remove it from the sitemap to avoid mixed signals.

The check uses the latest stored page snapshot, so rerun the affected page after fixing it. A sitemap-only recheck cannot create a newer page snapshot.

Sitemap limits exceeded

Sitemap limits exceeded is Warning. Exactly 50,000 URLs in one sitemap file is permitted. The check fails only above 50,000 URLs or when the file exceeds 50 MB. A 50,001-URL file fails.

URL-count evidence gives the file URL and observed count. Split that URL set and reference its parts from an index. A tree can also remain incomplete at the 50,000-child boundary or job deadline.

Implausible sitemap lastmod

Implausible sitemap lastmod is Advisory. It stores up to eight examples when <lastmod>:

  • Cannot be parsed as a date
  • Is 10 or more years in the past
  • Is more than 24 hours ahead of the check time

Use W3C Datetime such as 2026-08-21 or 2026-08-21T14:30:00+00:00. The value should describe meaningful page modification, not sitemap regeneration. Omit it if the CMS cannot provide an accurate value. A harmless timezone difference less than 24 hours ahead is not flagged.

Understand Good and skipped states

Good means a check passed or had no prior baseline from which to identify a loss. It does not guarantee indexing. Advisory can mean membership or member validity was skipped because the walk is incomplete.

When a child fails or the walk is still catching up, XML sitemap membership and Sitemap non-indexable members are not judged. Fix the failed file and allow the checkpoint to resume. The sticky successful baseline prevents an outage from resetting sitemap history.

Verify a correction

Use Check & Verify when available, or Check now in Site Resources. A manual run checks connectivity, enters the single-worker queue, fetches resource files, and starts or resumes the walk.

Large trees may need more than one pass. Check the Site resources lane in Queue Status, wait for a complete walk, and review Sitewide Checks. For Non-indexable URLs in sitemap, also rerun affected monitored pages and confirm their new snapshots. Repeatedly selecting Check now is not useful while the same child remains unavailable.

Related articles