What it does
This tool generates a sitemap by crawling a website that you provide. You enter or paste a web address, configure the crawl using the Crawl Depth: and Max Pages: controls, and the tool returns discovered pages as XML along with a list of the pages it found. The XML is the intended output for a sitemap, while the Page List gives a readable inventory of the URLs included in the result.
The crawl is not performed entirely in your browser. Although the tool marks local processing as a capability, the implementation details also state that the tool calls the backend endpoint /api/tools/sitemap-generate. In practical terms, the submitted address and crawl settings are sent to that backend to produce the result. The implementation uses plain browser APIs and no third-party libraries, and the page does not remember its state between visits. Output does not update as you type; you must press the tool’s action control to generate a sitemap. That control’s wording is not included in the available interface labels.
When to use it
- Create a sitemap for a small public website. Enter the site’s starting URL, choose a suitable Max Pages: value, and generate an XML sitemap from the pages the crawler can reach.
- Inspect how many pages are reachable from a starting point. Use the Page List after generation to review the URLs discovered during the crawl.
- Check the effect of a crawl-depth setting. Change Crawl Depth: and run another crawl to compare the resulting set of pages with a deeper or shallower traversal.
- Limit a broad crawl to a manageable number of URLs. Adjust Max Pages: when the starting site is large and you only need a bounded sitemap.
- Produce XML that can be copied elsewhere. Select Copy XML to place the generated XML on the clipboard for transfer to another system.
- Download the generated result for later use. The tool provides a file-download capability, allowing the generated sitemap output to be saved rather than copied manually.
- Test the workflow with built-in sample data. The shipped example uses https://example.com, which provides a safe starting point when no particular site has been selected yet.
How to use it
- Enter the full address of the site you want to crawl in the URL field. The tool’s sample value is https://example.com. A complete URL with a valid scheme and host is required.
- Set Crawl Depth: to the depth you want the crawl to explore. A shallow setting is appropriate for a limited view of the site, while a deeper setting allows the crawler to follow more levels from the starting URL. The tool does not publish a numeric maximum or minimum for this control.
- Set Max Pages: to the greatest number of pages you want the crawl to return. This is useful for preventing a large site from producing an unnecessarily large result. No published numeric limit is provided for the permitted value.
- Press the tool’s action control to run the crawl. The available labels do not include the wording of this button, so it should not be identified by an invented name. The tool does not run automatically when the URL or settings change.
- Review the discovered URLs in Page List. This area shows the pages reached by the crawl, which is useful for confirming that the starting URL was accepted and that the configured depth and page cap produced the intended scope.
- Inspect the generated XML. Select Copy XML to copy it to the clipboard, or use the download control to save the generated result. The source does not specify the download filename or a separate file-format choice.
Worked example
Suppose you want to generate a sitemap for a documentation site whose starting address is https://docs.example.org. Enter that address in the URL field. Set Crawl Depth: to 2 and Max Pages: to 50, then press the action control.
Assume the crawl can reach the home page, an overview page at /overview, a guide at /guides/getting-started, and a reference page at /reference. The exact set depends on what the site exposes to the crawler at the time of the request. The expected result is an XML sitemap representation of the pages found, together with a Page List containing their URLs. With the illustrative settings above, the crawl is intended to explore up to two levels and return no more than 50 pages. If the site exposes more than 50 reachable pages within that depth, the page cap constrains the result; if it exposes fewer, the crawl ends because it has no further pages to process within the configured scope.
You can then select Copy XML to copy the generated XML, or use the download capability to save it. There is no file-upload step and no need to open a local HTML or text file: this tool begins with a URL rather than with local content. Likewise, the output is not regenerated while you edit the settings. If you change Crawl Depth: or Max Pages:, you must run the action again to obtain a new result.
For the built-in example, the same process begins with https://example.com. The sample is useful for confirming that the interface and backend are operating, but the pages returned will reflect the site as it exists when the crawl runs. The tool does not promise a fixed example sitemap or a fixed set of sample URLs.
Limitations and edge cases
- There is no file input. The tool cannot crawl a local HTML file, accept a directory, or read a sitemap from your computer. If your source material exists only on disk, use a different tool that can process local files.
- Processing requires a backend. The implementation calls /api/tools/sitemap-generate, so the tool is not a fully offline browser utility. A network or backend problem can prevent a crawl even when the URL itself is valid.
- No numeric limits are published. The source does not state minimum or maximum values for Crawl Depth: or Max Pages:. The tool also does not state a maximum number of pages, output size, or crawl duration.
- The result is bounded by crawl behavior. A sitemap includes only pages the crawler reaches under the selected settings. Pages blocked from crawling, linked in a way the crawler cannot follow, or located beyond the configured scope may be absent. If you require guaranteed coverage of a large or complex site, use a dedicated site-auditing crawler instead.
- There is no automatic run. Editing the URL or controls does not update the output. You must explicitly press the action control, which can add a step when comparing several configurations.
- No state is retained between visits. The tool does not use local storage, so previously entered URLs, crawl settings, results, and clipboard state are not documented as being restored later. Record any needed values or downloaded output yourself.
- There are no alternative modes or extracted format choices. The tool has a single sitemap-generation workflow. It does not offer separate robots.txt, search-engine submission, image-sitemap, video-sitemap, or other format modes.
Troubleshooting
- Problem: The tool shows “Please enter a valid URL (e.g., https://example.com)”.
Fix: Enter a complete URL using the supported web form, including https:// and a valid hostname. The built-in example is https://example.com. - Problem: The result contains fewer pages than expected.
Fix: Check Page List, then review Crawl Depth: and Max Pages:. Increase the relevant setting if the desired pages were outside the configured crawl scope. - Problem: The crawl stops before the site has been fully explored.
Fix: Confirm that Max Pages: is high enough for the number of pages you need, and that Crawl Depth: is deep enough. For comprehensive auditing of a large site, use a crawler with explicit coverage and site-size reporting. - Problem: You want to submit a local HTML file or directory.
Fix: This tool has no file input and cannot read local files. Publish or expose the content through a reachable web URL, or use a local sitemap-generation utility. - Problem: The output does not change after you alter a setting.
Fix: Press the action control again. The tool does not run automatically and does not update its output live as you type. - Problem: A crawl cannot be completed while disconnected from the network.
Fix: Restore network access and retry because the tool calls a backend endpoint. Use a separate offline crawler if offline operation is a requirement.
Frequently asked questions
Does the tool upload files? No. It has no file input and no drag-and-drop support. You work with a URL that you enter or paste, not with a local file.
Is the crawl performed entirely in my browser? No. The implementation explicitly calls the backend endpoint /api/tools/sitemap-generate. The browser handles the interface and output actions, but the sitemap generation workflow requires backend processing.
What output does it produce? It produces sitemap XML and a Page List of discovered pages. You can select Copy XML or download the generated result. No separate output-format choices are provided.
What are the limits for Crawl Depth and Max Pages? The tool does not state a numeric limit for either control. Use the available values to bound the crawl, but consult a dedicated crawler if you need documented ceilings, large-scale coverage, or precise reporting.
Does it remember my URL and settings? No. The implementation does not use local storage, and state is not remembered between visits. Save the generated output and record the settings you need to keep.
Can I use the built-in sample? Yes. The tool ships with the sample URL https://example.com. It is a convenient way to exercise the workflow, although the tool does not guarantee a particular set of returned pages.
Does it generate results automatically while I type? No. It does not have an auto-run capability or live output. Press the action control after entering the URL and choosing the crawl settings.
When should I use a different tool? Use a different solution for local-file processing, fully offline generation, comprehensive large-site audits, fixed numeric guarantees, or sitemap types not represented by this tool’s single XML-generating mode.