Create an XML sitemap from a list of page URLs. Prepare a simple sitemap without crawling your site or adding unverified page data.
How to use
Enter one full URL per line, using the same origin. Generate the XML and save it as a sitemap file. Exact duplicate URLs are removed.
Example
List https://example.com/ and https://example.com/guide on separate lines to create two URL entries.
FAQ
Does a sitemap guarantee indexing?
No. Include canonical, indexable URLs that return useful content. The generator does not check response codes, redirects, robots rules, or page quality.
Related tools
A practical task
Prepare the list from canonical pages that should be discoverable. Leave out internal search results, private notes, and obsolete redirected addresses. The generator serializes your list; it cannot decide the editorial purpose or indexability of each page.
Another useful question
Must the sitemap include every URL?
No. Include the appropriate canonical public pages rather than every technical address. Keep its URLs consistent with the site's actual linking and redirect rules.
Details for interpreting the result
| Detail | Explanation |
|---|---|
| Crawling and indexing | Crawling is fetching a resource; indexing is including information about it in search. A crawl rule does not provide authentication. A blocked address can still be known through links even if its content is not fetched. |
| Robots rule scope | A path rule can match more than the single URL a person had in mind. Review trailing slashes, prefixes, and broad exclusions before deploying robots.txt. Private information needs access control rather than a crawler promise. |
| Sitemap purpose | A sitemap is a list of URLs offered for discovery. It does not repair inaccessible pages, remove duplicate content, or guarantee indexing. Keep the list focused on the versions you want search engines to consider. |
| Canonical signals | A canonical tag indicates a preferred URL among duplicate or similar pages. It is a signal rather than a command. Internal links, redirects, sitemaps, and actual content should agree about the preferred address. |
| URL components | A URL contains structure such as scheme, host, path, query, and fragment. Characters that separate those parts differ from characters inside a value. Encode the right component rather than transforming the full address blindly. |
| Query values | Query separators connect parameter names and values. An ampersand inside a value must not be confused with the separator between parameters. Build the URL with correct component encoding before sharing it. |
| URL fragments | A fragment points to a location within a resource and is normally not sent as part of the server request. It differs from a query parameter. Changing it does not necessarily create a different document for canonical selection. |