A successful response is only the first check
HTTP 200 means the request succeeded at the HTTP level. It does not prove that the response contains sitemap XML or that the requesting tool extracted any page URLs. Some servers return an HTML login page, a challenge screen or an error template with a 200 status.
Look at the response body received by the tool, not just the file name or what your browser displays. A public browser request and a server-side fetch can receive different content because of redirects, access rules, user agents or network routing.
Identify whether it lists pages or other sitemaps
A standard URL sitemap has a urlset root and page addresses inside url/loc elements. A sitemap index has a sitemapindex root and lists child sitemap addresses inside sitemap/loc elements. A tool that only understands page lists can incorrectly treat an index as empty.
Open the child sitemap files when the root is an index. They must be reachable too. Large sites may use several files or compressed .xml.gz sitemaps, so confirm that the tool supports the format and nesting it receives.
Work through the discovery chain
Follow the exact URL from the tool’s input through its final response. Keep private query parameters and credentials out of any logs or screenshots you share.
- Check redirects and the final hostname. A redirect to a login page or unrelated host does not deliver the intended public sitemap.
- Confirm the final body is XML, with the expected root and loc entries. Check encoding, XML namespaces and whether the file is compressed.
- For an index, fetch each relevant child and count the page URLs there. One working parent file does not prove every child can be read.
- Compare the tool’s error with the actual response: timeout, denied access, parsing failure and zero matching page URLs are different outcomes.
- Check the selected website/property. A tool may correctly reject page URLs belonging to a different site or outside a URL-prefix property.
- Review collection limits. A tool may stop at a URL count, sitemap count or time budget and should disclose that its collection is partial.
Check the server-side request when the browser works
If the XML is valid and the browser can read it, inspect the tool’s server-side fetch. Hosting rules, bot protection and requests from a website back to its own hostname can behave differently from an external browser request. Use the observed status and body to diagnose the issue before changing DNS or broadly disabling protections.
An error such as “No page URLs were found” should not erase a saved scan. Keep existing scan history while diagnosing the next discovery attempt. Test the corrected path with a fresh scan and compare its discovered count with the sitemap you actually inspected.
Discovery is not indexing
Finding ten URLs in a sitemap means ten URLs were discovered from that source. It does not mean all ten are indexed, and pages absent from the sitemap may still exist elsewhere on the site.
After discovery works, assess each important page separately. Redirects, duplicates and intentionally excluded pages can be legitimate. Google’s sitemap processing status and stored URL Inspection results answer different questions.
See discovered pages and their review status
AAA Signal keeps sitemap discovery and stored Google indexing results distinct, with saved progress and collection limitations shown. A sitemap submission does not guarantee a crawl or indexing.
Keep reading
- Is my website getting me customers? A simple 15-minute check
- Why isn’t my business showing up on Google? Common reasons and what to do
- How to track enquiries from your website (forms and phone calls)
- Google Business Profile for local service businesses: a plain-English setup checklist
- A weekly website check for small business owners (10 minutes)
- A weekly SEO report checklist for small-business owners
- How to read average keyword position without being misled
- What to include in a small-business SEO report
- Discovered – currently not indexed: what to check next
- Search Console clicks vs Analytics sessions: why the numbers differ
Google’s Page indexing report documentation · Google Analytics reporting documentation