Public URL check
Check sitemap.xml
Check sitemap.xml by URL: see whether the sitemap responds, what status code it returns, whether it is a sitemap index and how many URLs are visible.
sitemap.xml check by URL
Enter a website or page URL and URLCompass looks for the standard sitemap.xml on the domain, checks the HTTP status and shows whether the sitemap responds.
Sitemap index and child sitemaps
If sitemap.xml is an index, the report checks child sitemaps and shows the visible structure so you can spot basic availability problems quickly.
robots.txt and indexability
The check reviews sitemap.xml alongside robots.txt and public indexability signals such as canonical, robots meta, noindex and status code.
Clear limits
URLCompass does not crawl the whole website or show search results. URL counts come from accessible XML files and may be incomplete for private or non-standard sitemaps.
Example result
What the report can show before you open it
The exact values depend on the URL, but the report highlights practical signals instead of a raw technical dump.
sitemap.xml status, sitemap index and child sitemaps when available.
URLCompass counts URLs in sitemaps and marks the count as limited when needed.
robots.txt status, robots meta and basic signals that can block indexing.
The report groups output into critical issues, recommended fixes and useful context.
Report sections
The scan keeps the result readable
Sitemap.xml
Standard sitemap availability, HTTP status and basic server response.
Sitemap index
Support for sitemap indexes and child sitemaps with an approximate URL count.
robots.txt link
robots.txt, sitemap.xml and public indexability signals in one check.
No full crawl
The report counts accessible XML sitemaps but does not replace a full crawl or Search Console.
FAQ
Common questions
Does URLCompass need access to the website admin area?
No. The report is built from public signals available by URL: HTML, headers, DNS, TLS, robots.txt and sitemap.xml.
Can it show exact traffic or private analytics?
No. Exact traffic requires analytics access or paid data sources. URLCompass intentionally separates public checks from private metrics.
What should I do after the report?
Start with failed checks and warnings: indexability, HTTPS/TLS, security headers, page speed, missing metadata and weak DNS/mail protection.
Which URLs can be checked?
Use public http or https pages. Localhost, private IP addresses and closed admin pages are blocked to keep the checker safe.