Generate a sitemap from a small site
Run a capped, same-site, robots-respecting crawl and create XML from the eligible discovered URLs.
XML Sitemap Generator
Free, no signup. Generate a sitemap from a small, robots-respecting crawl — with clear inclusion rules, an honest cap, and only evidence-backed last-modified dates.
Bounded and polite: at most three page requests run at once; each request is capped at 900 KB/10 seconds, and the server also rate-limits each target host. This is a sitemap seed, not a full-site crawler.
Checks run from our server; we fetch the URL you enter and don't keep the results. The start site, its robots.txt, and eligible same-host HTML pages are sent through this site's bounded fetch endpoints. Crawl decisions and XML generation run in your browser. Anonymous run-level outcome counters may be used for aggregate research; URLs, domains, IPs, and identifiers are never included, and no statistic is released below 100 runs.
Site passport Local context for this saved site
Local data
Saved targets, named lists, and recent check summaries remain only in this browser.
Sitemap output
Excluded
Unknown / not included
Rate this tool
How it works
- Fetch
robots.txtand apply its Googlebot rules before each candidate request. A temporary robots failure stops the crawl rather than treating it as permission. - Follow same-origin links only, with a maximum of three concurrent requests and the cap you selected.
- Include only successful HTML pages that are not noindex and do not canonicalize to another URL.
- Keep exclusions and unknown responses separate. A cap, timeout, failed response, or truncated HTML never becomes an implied clean page.
About priority and changefreq: Google ignores these sitemap hints, so this generator intentionally omits them. lastmod appears only when the page provides a verifiable date.
Frequently asked questions
Will this crawl my entire site?
No. You choose a hard cap up to 200 pages. The tool states when the queue is still non-empty at that cap, so a capped crawl is never presented as complete.
Which pages are excluded?
Pages with a noindexNoindex is a directive that tells search engines to keep a page out of their index, so it won't appear in search results. It works only on pages a crawler can actually fetch — a page blocked in robots.txt can never be noindexed. header or meta tag, pages whose canonical points elsewhere, and URLs disallowed for GooglebotGooglebot is Google's web crawler — the software that fetches pages so Google can index and rank them. It comes in two variants, Googlebot Smartphone (primary, under mobile-first indexing) and Googlebot Desktop, and runs an evergreen Chromium renderer. in robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. are excluded. Failed, non-HTML, truncated, and non-2xx responses stay in the separate unknown state.
How is lastmod chosen?
Only a valid HTTP Last-Modified header, visible time datetime, or JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal. dateModified/datePublished value is emitted. The tool never stamps every page with today’s date.
Feature requests for Xml Sitemap Generator
Upvote what you want most. New ideas can be submitted from the floating Feedback menu; requests appear here once approved, and the most-wanted rise to the top.
You won't be emailed about that request anymore.
Loading…
➕ Request a feature
New requests are reviewed before they appear here.
Where this tool helps
Common use cases
Separate excluded URLs
Review noindex, off-canonical, failed, and uncertain pages instead of silently putting them in the sitemap.
Create evidence-based lastmod values
Emit lastmod only when the page provides a defensible date rather than inventing one from crawl time.
Preflight sitemap coverage
Inspect the generated set and exclusions before publishing or submitting the file to search engines.
Watch the full workflow
XML Sitemap Generator walkthrough
Read the transcript
XML Sitemap Generator
A useful X-M-L sitemap should list canonical, indexable pages—not every U-R-L a crawler happens to find. I’ll show you how to set the crawl boundary, how robots rules and page evidence control inclusion, how to read included, excluded, and unknown states, when last-modified dates appear, what the crawl cannot guarantee, and how to validate and deploy the output.
Step 1
Use this tool for a small site, a section-level audit, or a sitemap seed when no trustworthy inventory exists. It follows same-site links, respects robots rules, and includes only successful H-T-M-L pages that are not noindex and do not canonicalize elsewhere.
Step 2
Enter the full starting U-R-L and select a cap of twenty-five, fifty, one hundred, or two hundred pages. The cap is a safety boundary. If discoverable U-R-Ls remain queued when it is reached, the result explicitly says the crawl is partial.
Step 3
At most three page requests run concurrently. Each response has byte and time limits, and the server rate-limits each target host. This reduces load and prevents runaway crawling, but it also means the tool is a bounded sitemap seed—not a complete enterprise crawler.
Step 4
Try an example fills a safe starting U-R-L but does not pretend a crawl has already happened. For a real site, select Crawl and generate. The next screens use clearly labeled fictional pages to explain the resulting report without depending on external network state.
Step 5
This illustrative report processed seven fictional U-R-Ls: four included, two excluded with evidence, and one unknown. Unknown is intentionally separate. A failed, truncated, non-H-T-M-L, or timed-out response is never silently treated as indexable or excluded.
Step 6
A page enters the sitemap only after a successful H-T-M-L response, an allowed Googlebot robots decision, no noindex directive in headers or metadata, and no canonical pointing to another U-R-L. The crawler follows same-origin links only.
Step 7
Review the generated X-M-L and eligible count before downloading. Every loc should be an absolute canonical U-R-L you want indexed. The generator omits priority and change-freq because Google ignores those hints.
Step 8
Last-modified appears only when supported by a valid H-T-T-P Last-Modified header, a visible time element, or J-S-O-N-L-D dateModified or datePublished value. The tool never stamps every page with today’s date, which would make the signal untrustworthy.
Step 9
Review excluded U-R-Ls and their reasons. Robots blocks, noindex directives, and off-canonical pages can be correct—or reveal a configuration mistake. Fix the source rule when the page should be indexable; do not force an ineligible U-R-L into the sitemap.
Step 10
Unknown items need another check. Confirm response status, content type, redirects, rendering requirements, authentication, timeout behavior, and whether the U-R-L is meant to be H-T-M-L. A crawler limitation should not become an unsupported indexability conclusion.
Step 11
The crawl can miss orphan pages, JavaScript-discovered links, authenticated content, alternate hosts, or U-R-Ls beyond the cap and discovery guards. Robots failures stop the crawl rather than defaulting to permission. Compare results with your C-M-S, analytics, logs, and existing sitemap inventory.
Step 12
Download the X-M-L, follow the validator link, and reconcile the file with your intended canonical inventory. Publish it at a stable public U-R-L, submit it to search-engine webmaster tools, and monitor submitted-versus-indexed trends. Sitemap inclusion supports discovery; it does not guarantee crawling or indexing.
Generate a seed—validate before submission.
Review every exclusion and unknown state, compare the generated count with your known canonical inventory, and validate the X-M-L. Publish it at a stable U-R-L, reference it in robots dot t-x-t when appropriate, submit it in Search Console and Bing Webmaster Tools, then monitor discovery and indexing without treating submission as a guarantee.
Common issues & how to fix them
- Warning Noindex page is excluded from the sitemap Fix: Remove noindex if the page should be indexed; otherwise keep it excluded from the sitemap.
- Warning Non-200 page is excluded from the sitemap Fix: Restore a direct 200 response for the canonical page or leave the non-200 URL out of the sitemap.
- Warning Page canonicalized elsewhere is excluded Fix: Include only the canonical destination and keep the URL canonicalized elsewhere out of the sitemap.
- Information Duplicate URL is removed Fix: Keep one normalized canonical URL entry and remove duplicate spellings or parameter variants.
- Warning Invalid URL is excluded Fix: Correct the malformed absolute URL before adding it to the sitemap.
- Warning Cross-host URL is excluded Fix: Generate a separate sitemap for the other verified host and keep this sitemap host-specific.