TROUBLESHOOTING NOTE
Sitemap not found: what a /sitemap.xml 404 actually means
Updated
An HTTP 404 at /sitemap.xml means that particular URL was not found. It does not establish that your site has no sitemap, or that Google cannot discover its pages.
Locate the sitemap your site actually publishes
Check your CMS or framework configuration and read the Sitemap declarations in robots.txt. Some sites use another filename or a sitemap index. Our checker requests the conventional /sitemap.xml path only.
Open the declared public sitemap directly and verify the response. An HTML error page served with HTTP 200 is not valid sitemap XML. If your sitemap lives elsewhere, use that real location when submitting it to Search Console.
Review the listed URLs
Use absolute URLs for the intended canonical pages. Confirm they point to the public HTTPS origin rather than localhost or a preview deployment. Keep private, temporary and unwanted URLs out of the sitemap.
A sitemap index points to other sitemaps. Our tool reports the index structure but does not fetch its child files or verify the availability of every listed page. Files exceeding our 8 MB inspection limit are marked Couldn't check; this is a checker limitation, not proof that Google rejects the file.
Check discovery and indexing separately
Submit the correct sitemap URL in the verified Search Console property and review processing errors. Inspect important URLs separately to understand Google's indexing observations.
Sitemap submission is a discovery hint, not an indexing guarantee. Internal links still matter. If a page remains absent, investigate its HTTP response, canonical and indexing directives instead of repeatedly resubmitting the same file.
Reference and scope
Google Search Central: build and submit a sitemap
This guide explains a diagnostic workflow. Provider-specific configuration and actual messages or browser behavior require separate verification. The linked tools report bounded observations, not a complete audit.