An XML sitemap generator turns a plain list of page URLs into one standards-based sitemap.xml file that you can publish on your website. The list-to-XML sitemap generator takes URLs you have already collected from a CMS export, an analytics report, or a manual review and writes each one as a entry inside a valid document. It runs entirely in the current browser tab, so nothing is uploaded to a remote service, and it produces a downloadable file rather than submitting anything to a search engine on your behalf. For someone who has never built a sitemap before, this approach is the simplest path because it does not require crawling, server access, or knowledge of canonical tags, redirect chains, or robots.txt directives. You paste, you generate, you download. Everything else on this page is about making those three steps produce a clean file the first time.
What the Sitemap Generator Actually Does
An XML sitemap is a small text file that lists the pages you want search engines to discover on your site, along with optional hints about when each page was last updated and how often it changes. A browser-based sitemap generator takes a list of page URLs you already trust and writes that file for you in the exact format the sitemaps.org protocol describes. The tool takes one absolute URL per line, applies the official schema, deduplicates in first-seen order, and gives you a downloadable file called sitemap.xml.
Two things make this approach friendly to first-time users. First, the tool never crawls your website, so you do not need to install anything, expose staging areas, or worry about it accidentally indexing private pages. Second, all parsing, normalization, deduplication, XML escaping, and file creation happen locally in the tab you have open. That removes a common worry beginners have about online SEO tools: the URLs you paste and the file you generate never leave your device.
What the tool is not matters just as much. It does not check whether each URL returns a 200 status code, does not read canonical tags, does not detect redirects, does not follow links, and does not submit the file to Google or Bing. The output is only as accurate as the list you paste, so the editorial work happens before you open the generator, not inside it.
What to Put Together Before You Open the Tool
The only required input is a list of absolute page URLs, one per line, each starting with http:// or https://. A typical list might come from a CMS export, a column in a spreadsheet, a crawl you ran elsewhere, or a deduplicated set pulled from your analytics tool. Two rules matter most for beginners: every line must be a complete URL (no bare hosts like example.com/blog, no relative paths like /about), and every URL in a single file must share one host plus any non-default port.
The single-host rule is the one beginners trip over most often. example.com and shop.example.com are two different hosts and need two separate sitemap files. example.com and example.com:8443 are also two different hosts because a non-default port becomes part of the serialized host. HTTP and HTTPS for the same host, however, are allowed in one file because the protocol rule is about the host, not about the origin. The generator is built around a single serialized host per file, so URLs from two different hosts belong in two separate sitemap files rather than being silently combined.
Decide now whether you will add optional fields. The three optional fields — lastmod, changefreq, and priority — apply one shared value to every URL in the file. They are not required, and leaving them blank produces a valid loc-only sitemap that search engines accept without complaint. Add them only when you have one truthful value that genuinely fits every entry on the list.
How to Generate sitemap.xml From Your URL List
- Open the sitemap generator in your browser and paste one absolute URL per line into the input box, using one host plus any non-default port per file. Do not add trailing whitespace, leading whitespace, blank lines with stray spaces, or extra commentary on the same line.
- Leave the optional fields blank when you are not certain the same value fits every page. A loc-only file is a valid sitemap and is the safer starting point for someone new to the protocol.
- If you do supply an optional field, make sure the value is truthful. lastmod accepts a real YYYY-MM-DD date or a complete date-time with seconds and a Z or valid UTC offset. changefreq accepts only always, hourly, daily, weekly, monthly, yearly, or never. priority accepts a decimal from 0.0 through 1.0.
- Click Generate. The tool validates every line, serializes each URL through the WHATWG browser URL parser, deduplicates in first-seen order, escapes XML entities, and measures the final UTF-8 byte size. If any line is invalid, the whole generation fails rather than silently dropping it.
- Review the completed XML and the counts shown on the result. Confirm every URL you expected is present, the duplicate count reflects what you intended, and no error message appears above the file.
- Click Download to save sitemap.xml to your device. The file is created as a local Blob download tied to the current result and is never uploaded anywhere.
If you want a longer walk-through of the same flow, the practical guide on how to create an XML sitemap covers the publishing side of the workflow once you have the file in hand.
Optional Fields Beginners Often Skip (and When to Add Them)
The XML sitemap protocol makes lastmod, changefreq, and priority optional on purpose. None of them are ranking signals, and none are crawl commands — search engines treat them only as hints. Beginners usually get the cleanest result by leaving all three blank and letting the protocol's entries speak for themselves.
Add lastmod only when one date fits every URL on the list. For a brand-new site with pages all launched in the same week, a single shared date is honest. For a mixed archive of old and new posts, a shared date is misleading, and leaving the field blank is more accurate than guessing. Add changefreq only when the schedule genuinely applies — for example, "daily" for a news front page or "yearly" for an about page. Priority is the field beginners overuse; a flat 0.5 across every URL carries no information, and search engine documentation treats priority as a relative hint that rarely changes crawl behavior.
If any optional field is malformed — an impossible calendar date, an unknown changefreq value, a priority outside 0.0–1.0, or stray whitespace around the input — the tool fails the whole generation rather than quietly substituting a default. That strict behavior protects you from publishing a sitemap with metadata you did not intend to send.
Limits and Rules Beginners Trip Over
The browser-based generator uses lower budgets than the protocol maxima so it can show the complete XML in the result panel and still build a download Blob in memory. The protocol allows up to 50,000 URLs and 52,428,800 uncompressed bytes per file; this tool accepts up to 10,000 unique URLs and exactly 10,485,760 UTF-8 bytes. Every limit is all-or-nothing. The 10,000th unique URL succeeds; the next one fails. The exact 10,485,760-byte boundary succeeds; one additional byte fails. No preview is truncated, no ellipsis is added, and no partial download is returned.
Duplicate lines do not consume output slots, so cleaning your list beforehand can save room for genuine URLs. URL length is checked after serialization: a normalized location must contain fewer than 2,048 characters, with 2,047 accepted and 2,048 rejected. The protocol also forbids credentials in any entry, and the generator enforces the same rule so a username or password cannot accidentally be copied into a public file.
The table below shows the inputs beginners most often paste and how the generator treats each one.
| What you paste | What happens |
|---|---|
| https://example.com/about | Accepted; serialized to the canonical form. |
| https://example.com:8443/about | Accepted; the non-default port becomes part of the host. |
| example.com/about | Rejected — bare host without scheme. |
| /about | Rejected — relative path, not an absolute URL. |
| https://user:[email protected]/about | Rejected — credentials must never appear in a public sitemap. |
| https://example.com/about#team | Rejected — fragments are not sent to the server and must not create separate entries. |
| https://EXAMPLE.com/About | Accepted; host lowercased and path normalized, duplicates merged with the first-seen form. |
| https://example.com/about (with surrounding spaces) | Rejected — leading or trailing whitespace is an error, not a silent trim. |
| ftp://example.com/file | Rejected — only HTTP and HTTPS are accepted. |
The single-host rule and the rejection of credentials and fragments come straight from the sitemaps.org protocol. For the protocol-level background, the Google Search Central guide on building a sitemap explains why crawlers treat each as a fetched resource rather than a typed address.
What the Result Panel Tells You
After a successful generation, the result panel shows the complete sitemap.xml, the number of unique locations it contains, and a duplicate count for any lines that were merged into an earlier entry. The XML begins with a UTF-8 declaration and a element using the official http://www.sitemaps.org/schemas/sitemap/0.9 namespace. Each entry contains and ; optional , , and tags only appear when you supplied them. Locations are XML-escaped after URL normalization, so ampersand, apostrophe, quotation mark, greater-than, and less-than characters in a path become named XML entities, with ampersand escaped first to avoid double-escaping generated entities.
The download button at the bottom of the panel creates a local Blob and serves the file through a temporary Object URL owned by that result. Editing the URL list or any option immediately revokes the previous download and clears the old XML, the download link, and any error message. Generating again does the same before validation starts, so no stale Blob is ever served from a previous attempt. If Blob creation or the Object URL itself fails, the result is cleared rather than leaving a broken download behind.
When validation fails, the panel shows an error message in place of the XML and does not offer a download. The whole generation fails rather than skipping bad lines or silently dropping valid ones, so you cannot accidentally publish a partial sitemap. Reading the error message carefully usually points to a specific line number or input shape, which makes fixing the list a quick step before the next attempt.
下載 sitemap.xml 之後
下載的檔案應放置於其所代表主機的根目錄。針對 https://example.com/ 的網站地圖通常位於 https://example.com/sitemap.xml，這樣爬蟲就能在不進行身分驗證或附加路徑段的情況下請求該檔案。接著，您可以在 robots.txt 中以一行 Sitemap: 來引用它，或直接透過搜尋引擎的網站管理員工具提交該網址。
在發布之前，請對網址清單本身進行一次編輯上的審查。移除重新導向、標準化複本、被封鎖的網頁、staging（測試環境）的網址，以及任何位於登入後的頁面。生成器無法為您檢查這些屬性——它僅轉換您所給定的清單。若您貼上的部分網址實際上是重複的，結果頁面上的重複計數會告訴您合併了多少行。
產生並下載網站地圖只是技術部分的工作；讓爬蟲找到它則屬於發布部分的工作。更完整的通訊協定檢查清單，請參閱關於從網址清單建立時的 sitemap 通訊協定規則的文章。