Quick answer
A sitemap is useful only if crawlers can retrieve and parse it. NOTABIS reports sitemap-unavailable when a declared sitemap cannot be fetched successfully during the audit. Verify the exact URL, status code, redirects, content type, XML structure, and access rules; do not assume that a sitemap error means every page is inaccessible.
What the issue means
Sitemaps are XML documents that can list canonical URLs and optional metadata. They may be referenced in robots.txt, submitted separately, or linked through a sitemap index. An unavailable sitemap may return an error, time out, redirect unexpectedly, serve HTML instead of XML, or be blocked by authentication, firewall, or an invalid certificate.
Why it matters for SEO
A sitemap can help search engines discover URLs, especially on large, new, or internally complex sites. It is not a replacement for internal links, canonicalisation, or good responses. A sitemap failure can reduce a useful discovery channel without proving that indexed pages will disappear.
How NOTABIS detects it
NOTABIS follows the sitemap locations available from the audited site and records a sitemap issue when the resource cannot be read successfully. The finding reflects the audit’s network position, safety rules, timeouts, and the response observed at that time. It does not certify that a sitemap is complete or that every listed URL is valid.
How to check it yourself
Request the exact location:
curl -sSIL https://example.com/sitemap.xml
curl -sS https://example.com/sitemap.xml | head
Check for a successful final response, an XML content type, a valid <urlset> or <sitemapindex>, and public access. Inspect robots.txt for typos and compare the declared URL with the deployed route.
How to fix it
Publish the sitemap at a stable public URL, return a successful response, and generate valid XML with absolute canonical URLs. Correct incorrect robots.txt references, remove accidental login requirements, and configure redirects to end at the actual sitemap rather than a generic HTML page. Keep the file within provider size and URL limits, using an index when necessary.
Recheck the final response from outside your office network and submit the corrected sitemap through the relevant search-engine tooling where appropriate.
When it is intentional or does not need fixing
Small sites may gain little from a sitemap if their pages are already well linked, but a declared broken sitemap should still be corrected or removed. Private environments should not expose internal URLs merely to satisfy a public audit.
Related issues
Also review XML sitemap access, orphan pages, and broken internal links.
Run a NOTABIS audit
NOTABIS records sitemap access evidence and helps distinguish a discovery-resource failure from page-level crawl failures.