Quick answer: what does sitemap validation check?
Sitemap validation checks whether XML has the expected sitemap structure and whether its entries are usable URL values. It does not prove that the listed pages are reachable, indexed or eligible to rank. Review those questions separately.
Validate your XML with the Sitemap Checker
Start with the right file
A sitemap lists URLs that you want search engines to discover. A URL sitemap and a sitemap index have different structures: the index points to sitemap files, while a URL sitemap lists pages. Check the actual input and any limitations shown in the workspace before interpreting the result.
Open your sitemap in a browser or obtain a current copy from your website. If the response is an HTML error page or a login screen, copying that response into an XML checker will not produce a valid sitemap. Resolve the underlying response first.
Validate in Inficore
- Open the XML Sitemap Checker from this guide.
- Paste your sitemap XML, or use the supported file input shown in the workspace.
- For a supported remote check, enter the public HTTPS sitemap address.
- Run validation and read the reported structure and entry errors.
- Correct the source that generates the sitemap, then validate a fresh copy.
Pasted XML is checked in the browser. A remote fetch sends the public URL to the server and is restricted to permitted public destinations. A blocked fetch is not, by itself, evidence that Google cannot reach the sitemap. Do not bypass the protection by submitting private network URLs.
Check the entries, not just the XML
A syntactically valid sitemap can still list the wrong pages. Use the preferred canonical address for each public page. Remove accidental duplicates and avoid listing sign-in pages, admin pages or obsolete addresses as discovery targets.
For a migrated tool, the sitemap should contain the current destination. If an old tool address has a genuine replacement, handle that old URL with the appropriate redirect separately. Do not rely on a sitemap entry to create a redirect.
Only report a last-modified date when you have a meaningful content update date. Replacing every date with today's date each time the sitemap is generated does not describe when the content actually changed.
Submit and investigate in Search Console
After validating a current sitemap, submit its public URL in the Sitemaps section of Search Console. Review the processing result and use URL Inspection for individual important pages. Discovery through a sitemap does not guarantee crawling, indexing or ranking.
A page may be excluded because it redirects, has a noindex directive, is a duplicate or no longer exists. Some exclusions are intentional. Match the diagnosis to the page's purpose instead of trying to make every known URL indexed.
Common questions
My sitemap is valid. Why is a page not indexed? XML validation and Google's indexing decision are different checks. Inspect the page's response, canonical, crawl access, content and Search Console details.
Should I include query-string variants? Prefer the actual canonical page unless a variant represents a distinct page that should be indexed. Review currency and tracking parameters carefully.
Will a checker inspect every page in the sitemap? This checker validates the supplied structure and entries; it does not independently establish page reachability or indexing. Use separate page-level checks for those questions.
Finish with a page-level check
Open the XML Sitemap Checker. For a URL that moves elsewhere, use the Redirect Checker and inspect the final destination.
No published comments yet. Start the conversation.