Skip to content
littlekit.app

Sitemap generator

Build a sitemap from page URLs with date validation, duplicate removal, and a live XML preview.

Up to 200 URLs on the same origin. Optional per-page date after a tab: URL [tab] YYYY-MM-DD.
Optional sitemap hints
YYYY-MM-DD. Use only when this is the actual last change date for these pages. A tab-separated date overrides it.
3URLs in sitemap
0Duplicates removed

Host at https://example.com/sitemap.xml · 0 fragments removed

Normalized sitemap entries
Page URLLast modified
https://example.com/Omitted
https://example.com/coffeeOmitted
https://example.com/aboutOmitted

No pages are crawled. All URLs must share a protocol, host and port. Date-only lastmod values are validated, including leap years.

Live sitemap XML280 characters
<?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/coffee</loc>
  </url>
  <url>
    <loc>https://example.com/about</loc>
  </url>
</urlset>
Processed on your device

How it works & useful details

How this tool works

Enter one HTTP(S) URL per line, optionally followed by a tab and YYYY-MM-DD lastmod date. A per-page date overrides the optional default. All URLs must use the same protocol, host and port; host the file at that origin root. Duplicate removal retains the first normalized URL and its date. Fragments can be removed explicitly. Up to 200 lines and 200,000 input characters; normalized URLs must be shorter than 2,048 characters. No crawling, cross-site sitemaps or sitemap indexes. Optional hints do not guarantee indexing.

Sitemap protocol

About this tool

Sitemap generator builds an XML sitemap from a list of page URLs, validating dates, removing duplicates, and showing a live preview. It is the quick way to produce a valid sitemap without hand-writing XML.

Optional hints such as change frequency and priority are supported and clearly marked as hints, not guarantees. URLs are normalized and unsafe characters are escaped for XML.

How to use it

  1. Paste the page URLs, one per line or as full URLs.
  2. Optionally add last-modified dates and hint values.
  3. Check the preview for duplicates and invalid entries.
  4. Copy or download the sitemap XML.

Worked example

Entering three URLs, one per line,

https://example.com/
https://example.com/coffee
https://example.com/about

produces a standard XML sitemap with one <url><loc> entry for each. Add a tab and a date after a URL (https://example.com/coffee<tab>2026-09-24) to include a <lastmod> for that page.

Sitemap good practice

  • List only canonical URLs that return 200 and that you want in search results. Leave out redirects, noindex pages, and duplicates.
  • Use lastmod only for real content changes. Search engines learn to ignore dates that change on every build.
  • Host the file on the same origin as the URLs, reference it in robots.txt with a Sitemap: line, and submit it in Google Search Console and Bing Webmaster Tools.
  • A single sitemap file can hold up to 50,000 URLs. Larger sites use a sitemap index. This generator is sized for small sites and landing pages, up to 200 URLs.

A sitemap helps crawlers discover pages, especially on new sites with few inbound links, but it does not guarantee that they are indexed. Quality, internal links, and usefulness decide that.

Frequently asked questions

Do priority and change frequency affect indexing?

They are hints that search engines may ignore. Accurate lastmod values and internal links matter far more.

Can it include cross-site URLs?

No. A sitemap should list URLs from a single host; cross-site entries are rejected.

What is the limit?

Up to 200 URL lines and 1,000,000 characters of generated XML.

Should I set priority and changefreq?

Google ignores both. They are optional hints in the protocol, and a clean list of canonical URLs with honest lastmod dates is more useful.