The Sitemap-only pages signal shows URLs that were listed in the sitemap but were not discovered by the crawl during this scan.
This is a scan-level signal. It answers: “Which sitemap URLs did the crawl not reach?”
What this signal means
A sitemap-only page is present in the sitemap data captured for the scan, but Siteimp did not find it by following the site’s crawl paths.
That means the sitemap and crawl do not fully agree.
This can happen for harmless reasons, but it is often worth reviewing.
How to read the table
The table lists the URLs found for this signal.
Each row is one URL that appeared in the sitemap but was not discovered by the crawl.
Why it matters
Sitemap-only pages can reveal pages that are published but poorly connected from the rest of the site.
That may indicate:
- orphaned pages
- pages missing from navigation
- weak internal linking
- old sitemap entries
- pages intentionally listed but not linked
- pages blocked or skipped during the crawl
A sitemap-only URL is not automatically bad. It is a prompt to check whether the page should be reachable from the site itself.
What to check next
Open the listed URL.
Decide whether the page should be reachable through normal site navigation or internal links.
If yes, add or repair internal links.
If no, decide whether the URL should remain in the sitemap.
If the page is old or removed, update the sitemap.
If the crawl was blocked by robots rules or scan scope, review the scan context before changing the site.
Signal vs issue
This is a scan-level signal. It looks at sitemap-to-crawl mismatch across the whole snapshot.
Unlike the page-level Sitemap issue, this signal may include URLs that were in the sitemap but not crawled as pages in this snapshot.
Why this signal may be empty
If the page says No URLs were found for this signal in the current scan, Siteimp did not find sitemap-only URLs for this snapshot.
That means the sitemap did not contain extra URLs outside the crawl for this check, or no rows were available for this signal.