Generate an XML sitemap from a website
Crawl linked HTML pages on one website to create sitemap.xml. Review URLs before publishing; a sitemap helps discovery but does not guarantee indexing.
Crawl the website and create a file
From a starting URL to sitemap.xml
- Enter a public URL. Start from a page that links to important pages. Choose a 50–1,000 page limit; the crawler follows HTML links on the same website up to three levels deep.
- Review crawl results. Check URLs and any incomplete-crawl notice. To add or remove URLs, fix website links and recrawl, or edit the downloaded XML. Videos without thumbnails are omitted from XML.
- Download and publish. Inspect the XML, upload it to a URL you control, then submit that file URL in Search Console. The Search Console link only opens the console; it does not submit the sitemap.
Review the file before submitting it
| What you see | What to do |
|---|---|
| Important page is missing | Check HTML links from the starting URL, crawl depth, login requirements, and content loaded only after JavaScript. For larger sites, use a sitemap generated by the CMS or server. |
| URL should not be indexed | Review canonicals, response codes, URL parameters, and robots rules. The crawler skips HTML meta noindex, but does not validate canonicals, X-Robots-Tag, or the target site’s robots.txt. |
| lastmod, changefreq, or sample robots.txt appears | lastmod comes from the HTTP Last-Modified header when present; verify it against actual content changes. Google ignores changefreq. Add the Sitemap line to your existing robots.txt after confirming the file URL; do not overwrite current rules. |
A sitemap helps search engines discover URLs; it does not confirm indexing or improve rankings. After submission, monitor the Sitemaps report and use URL Inspection for individual pages. Google’s sitemap guide.
Crawl scope and data
KitoTool’s server fetches public HTML over HTTP/HTTPS on ports 80 or 443, with time and size limits. Crawl results are cached for about five minutes by URL and options. Your browser uses that result to build the preview and downloadable file; the target page’s JavaScript is not executed. Localhost, private network addresses, and URLs containing credentials are rejected.
For videos, the tool uses the page title as the XML title and description. Edit that metadata in the downloaded file if it does not describe the video accurately.
Comments & feedback
Loading ratings…
Write a commentNo account needed