When does the builder split my sitemap?

One sitemap may list at most 50,000 URLs and be at most 50 MB uncompressed. Larger lists are split automatically into numbered files plus a sitemap-index.xml that references them. Submit the index to search engines; Download all saves every file in one .zip.

Why are and missing from the output?

Google ignores both fields, so the builder does not generate them and the validator reports them as ignored. Use an accurate , the date the page content last changed, instead.

Does validating a sitemap URL or checking URL health send data to a server?

Only when you choose those actions. The URLs are sent to CodingTool servers, which request them from the target site without cookies through guarded fetches that block private and internal addresses, and nothing is stored. Building and validating pasted or uploaded data stay in your browser.

XML Sitemap Builder & Validator

Local processing with network features

Build, split and validate XML sitemaps, then check URL health

Input

Options

Default lastmod

Include hreflang alternates

Sitemap location

Folder URL that will host the files.

<priority> and <changefreq> are not generated because Google ignores them.

Output

No sitemap yet

Paste URLs, upload a file or load an example, then choose Generate sitemap.

Build and Validate with pasted or uploaded data run in your browser; nothing is uploaded.

Hreflang Validator & GeneratorCheck hreflang clusters, return links and codes, then generate tags Broken Link Checker & CleanerFind, remove, and replace dead URLs from text, files, and webpages Robots.txt Tester & BuilderTest URLs against robots.txt, trace the deciding rule and build a valid file

What does the XML Sitemap Builder & Validator do?

It turns a plain URL list, a CSV export, a JSON array or an existing sitemap into a valid XML sitemap that follows the sitemaps.org protocol, and validates sitemaps you paste, upload or fetch from a public URL. Findings name the line and entry so you can fix the source quickly.

How to use

1.Choose Build, Validate or URL Health.
2.Build: paste URLs (optionally followed by a lastmod date), a CSV with a loc,lastmod header, a JSON array or sitemap XML, or upload a file. Choose Generate sitemap.
3.Validate: paste or upload XML, or enter a public sitemap URL, then choose Validate.
4.URL Health: pick up to 50 URLs from the Build or Validate result and choose Check URLs.
5.Copy or download the XML, the CSV issue report or the JSON report.

Splitting and protocol limits

One sitemap may list at most 50,000 URLs and be at most 50 MB uncompressed. Larger lists are split automatically into sitemap-1.xml, sitemap-2.xml and so on, plus a sitemap-index.xml that references them; submit the index. The output explains which limit caused the split. Download all saves every file in one .zip.

What the validator checks

•Well-formed XML, the urlset or sitemapindex root and the sitemap namespace.
•Absolute http(s) URLs, length, whitespace and duplicates.
•W3C lastmod dates and dates in the future.
•xhtml:link hreflang alternates, the xhtml namespace and self references.
•Optional expected host and URLs spread across several hosts.
•<priority> and <changefreq> are reported as ignored by Google, so the builder never generates them.

Privacy and network requests

Build and Validate with pasted or uploaded data run entirely in your browser. Fetching a sitemap URL or running URL Health sends only those URLs to CodingTool servers, which request them from the target site without cookies and return the result; nothing is stored. Private, internal and cloud metadata addresses are blocked, and redirects are checked again on every hop.

Limitations

Remote sitemaps are capped at 10 MB, and URL Health checks 50 URLs per run with a 25 second budget. A healthy status shows what an anonymous server request receives; it does not mean a page is indexed. Search engines decide independently whether to crawl and index the URLs in a sitemap.

XML Sitemap Builder & Validator

Input

Options

Output

Related Tools