HCODX/XML Sitemap Generator
SEO · sitemaps.org protocol · Google/Bing/Yandex compliant

XML Sitemap Generator & Validator — Google-ready in seconds

Paste your URLs to generate a valid sitemap.xml for Google, Bing, Yandex and Baidu — or paste an existing sitemap to validate it against the sitemaps.org protocol. 50,000-URL / 50 MB compliant. No upload. No signup.

Mode
Generator options
URLs (one per line)0 urls
sitemap.xml
URLs
0
Bytes
0
Limit
50,000 / 50 MB
Status
Ready
Use cases

Sitemaps still matter in 2026

A clean sitemap means faster discovery, better crawl budget, and fewer "indexed though blocked" warnings in Search Console.

Submit to Google Search Console

Google still recommends sitemaps for any site with more than 500 URLs or with content that's hard to discover via internal links.

Speed up indexing of new pages

A fresh lastmod in your sitemap signals "this URL just changed" — search engines treat it as a re-crawl hint.

Validate before submitting

Catch broken XML, invalid URLs, missing <loc> elements and duplicate URLs before they show up as errors in Search Console.

Fix sitemap errors from GSC

Paste the offending XML, get a checklist of exactly what to fix. No reading the schema spec by hand.

Bing/Yandex/Baidu compliance

Same protocol, different submission consoles. A spec-compliant sitemap works everywhere.

Static site / Jamstack sitemaps

Generated at build time or runtime — paste your list of routes, drop the output into your public folder.

Step by step

How to use this tool

1

Pick a mode

Choose Generate to build a new sitemap from a list of URLs, or Validate to check an existing sitemap against the protocol.

2

Paste URLs or XML

In Generate, paste one URL per line (absolute or relative to the Base URL). In Validate, paste your sitemap.xml or upload the file.

3

Tune defaults / read findings

Generator: set default lastmod, changefreq, priority. Validator: review the 10-point checklist of spec compliance.

4

Upload to your root

Copy or download the result, place it at https://yourdomain.com/sitemap.xml, and reference it from robots.txt.

FAQ

Frequently asked questions

The sitemaps.org protocol caps a single sitemap file at 50,000 URLs and 50 MB uncompressed. If you need more, split into multiple sitemaps and reference them with a sitemap index file (sitemapindex element) — Google, Bing and Yandex all support nested indexes up to 50,000 sitemaps per index, so practically there is no upper bound.

Only <loc> is mandatory. Google has publicly stated it ignores changefreq and priority entirely, and uses lastmod only when the value is accurate and consistent. Bing still respects all three. Best practice in 2026: include accurate lastmod (in W3C Datetime format), skip changefreq, and only set priority if you have a meaningful internal hierarchy.

Upload sitemap.xml to your domain root, then add the URL in Google Search Console under Indexing → Sitemaps. You can also add the line Sitemap: https://yourdomain.com/sitemap.xml to your robots.txt — Googlebot, Bingbot, YandexBot and DuckDuckBot all auto-discover sitemaps via robots.txt. Re-submitting after big changes triggers a faster crawl.

A sitemap index is a meta-sitemap that lists multiple sitemap files using <sitemapindex> as the root element instead of <urlset>. Used when you exceed the 50,000-URL or 50-MB single-file limit, or when you want to organize sitemaps by content type (one for pages, one for images, one for products). Submit only the index URL to search engines — they will fetch the children automatically.

About

About sitemaps and the sitemaps.org protocol

The XML Sitemap protocol was created by Google in 2005 and donated to the community as sitemaps.org in 2006. Bing, Yahoo and Yandex co-signed; today it is the universal way to tell search engines about your URLs. The format is simple: a <urlset> root element with one <url> child per page, each containing at minimum a <loc> with the absolute URL.

When to use a sitemap index

Anything beyond 50,000 URLs or 50 MB uncompressed must be split. Wrap multiple sitemap files in a <sitemapindex>. Common patterns: one sitemap per content type (pages-sitemap.xml, posts-sitemap.xml, products-sitemap.xml), one per language (en-sitemap.xml, fr-sitemap.xml), or chunked monthly for very large sites. Submit only the index file to search engines.

Image and video extensions

The Image extension (xmlns:image="http://www.google.com/schemas/sitemap-image/1.1") lets you list up to 1,000 image URLs per page entry — useful for image search visibility. The Video extension does the same for video assets with extra metadata like duration and thumbnail. Both are namespace add-ons on the standard urlset.

lastmod best practices

Use W3C Datetime format — either a date (2026-05-22) or a full ISO timestamp (2026-05-22T08:00:00+00:00). The value must reflect a real content change; setting all URLs to today's date on every deploy is one of Google's stated reasons for ignoring lastmod entirely on a site. Set it once per genuine update.

Related

Related tools