Sitemaps · worked example
XML Sitemap Validation: Review Six Entries Before Submission
Check XML and repeated locations, then review the live facts that a pasted file cannot establish.
A readable XML file still needs a URL review
XML sitemap validation has two practical parts: checking the file’s structure and checking whether its listed URLs belong in the sitemap. A document can parse correctly while repeating a location, listing a redirect or pointing to a page you deliberately keep out of search. Those decisions require information about the website beyond the XML text.
Start with the sitemap your publishing system already maintains. If an existing SEO setup owns it, review that output before creating a competing file. A manual sample is useful for learning and diagnosing an export, while a changing website needs a reliable way to keep its URL list current.
This guide uses an invented six-entry sitemap and ProSEO’s local XML Sitemap Validator. The tool reads pasted XML and reports basic location issues. The page states its processing limits separately from the sitemap protocol’s file limits.
Paste a six-entry sample
Copy this complete document into the validator in the tools directory. The repeated guide URL is intentional. None of these example.com destinations represents a page whose live response we checked.
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url><loc>https://example.com/</loc></url>
<url><loc>https://example.com/guides/redirect-map/</loc></url>
<url><loc>https://example.com/guides/redirect-map/</loc></url>
<url><loc>https://example.com/tools/meta-preview/</loc></url>
<url><loc>https://example.com/old-guide/</loc></url>
<url><loc>https://example.com/private-draft/</loc></url>
</urlset>Run Validate XML. The sample contains six URL entries and five distinct location strings. Both copies of the guide location should receive a repeated-location note. The other four entries can receive a basic location pass even though this check knows nothing about their page content, redirects or index controls.
Export locations when you need a review list. Keep the XML as well: a location export is convenient for a worksheet, but the original file preserves its structure and any other metadata. Record the source sitemap URL and the time you saved it so another editor can identify the version under review.
Make the content decisions outside the parser
Suppose a separate review of this fictional site establishes the following conditions. These conditions are teaching assumptions, not output from ProSEO’s validator.
| Entry | Assumed page condition | Decision |
|---|---|---|
| Homepage | Preferred public homepage | Keep once. |
| Redirect-map guide, first copy | Preferred public guide | Keep once. |
| Redirect-map guide, second copy | Same location string | Remove the duplicate row. |
| Meta-preview tool | Preferred public utility | Keep once. |
| Old guide | Redirects to the retained guide | Use the final preferred guide URL already listed. |
| Private draft | Deliberately marked noindex | Exclude from the intended search URL list. |
The revised sample contains the homepage, the guide and the tool. Retest the document after editing it, then check the published file. A passing local preview does not establish that the website serves the same bytes or that its sitemap source will preserve a manual change during the next rebuild.
For a live audit, record each listed URL’s response, redirect destination where relevant, canonical preference and index controls. Investigate conflicting instructions before changing them. A private draft should remain private according to its actual purpose; adding it to a sitemap is not a reason to remove a deliberate restriction.
Check the format details that commonly break a sample
Use absolute locations, the standard sitemap namespace and UTF-8 encoding. XML has its own escaping rules: a literal ampersand in a query string must be represented as & inside the XML. This preserves the URL’s value after parsing. It does not mean the live address should acquire the five characters &.
A urlset contains page-location entries; a sitemapindex lists sitemap files. Keep those roles distinct when preparing a review. The protocol permits a single sitemap up to 50,000 URLs and 50 MB uncompressed, while ProSEO’s local checker accepts at most 1 MB and 5,000 entries per check. Split a larger review into suitable batches without mistaking the tool’s capacity for Google’s file limit.
Add modification dates only when you can maintain accurate significant-update dates. Replacing every date whenever a file is generated creates a maintenance problem. A compact sitemap with truthful locations and dates is easier to investigate than an elaborate file full of guessed values.
Verify the published sitemap and then inspect search adoption
Open the actual sitemap your site advertises and confirm that the intended entries appear there. Check the publication system if deleted rows return, newly published pages are omitted or an older export keeps being served. For a migration, use the redirect mapping workflow to keep final destinations consistent across the sitemap and internal links.
Search Console’s Sitemaps report helps you review file processing. Submission supports discovery and does not guarantee crawling or indexing of every location. Use URL-level inspection and the site’s indexing reports when the question concerns a particular page. Keep the file check, destination check and search-adoption check as separate observations in your review notes.
The noindex and canonical guide explains the supplied-HTML part of the page review. The On-page SEO Review worksheet provides editable fields for evidence and a later retest. Start with the actual sitemap and the intended URLs, then record which remaining question requires a live response or Search Console.
References
Checked 17 October 2026: Google’s sitemap construction guidance, the sitemap protocol and Google’s sitemap overview. The XML, diagram and page conditions are original illustrative material.