XML Sitemap Generator
From A List To Valid XML
Paste one URL per line and this XML sitemap generator writes valid XML as you go. It tidies the list on the way through, so repeats disappear and tracking parameters get stripped before they reach the output.
- FreePrice
- 50,000Address limit
- NoneCrawling
- NoneUploads
XML Sitemap Generator
One address per line becomes one entry in the file
- Entries
- 0
- Skipped
- 0
- Size
- 0 B
Ready. Paste your addresses and the XML builds as you go.
When An XML Sitemap Generator Helps
A sitemap is a list, not a map. It tells a search engine which addresses exist, and roughly when each one last changed.
Crawlers find most pages through links anyway. However, a sitemap reaches the pages your navigation forgot, and it reaches them faster.
New sites benefit most of all. Since nobody links to them yet, a sitemap is often the only route in.
Big sites benefit for the opposite reason. Because deep pages sit many clicks from the homepage, a flat list saves the crawler a long walk.
Search engines treat a sitemap as advice they may ignore. Google's guide to building a sitemap says what it will and will not do.
Which Tags Search Engines Still Read
Four tags exist in the protocol. Only two of them earn their place today.
Google reads loc, obviously, and it reads lastmod when the dates look honest. Meanwhile changefreq and priority have been ignored for years.
So leave those two out, or set them and stop worrying. Either way they change nothing, whatever an old guide told you.
Only Canonical Addresses Belong Here
A sitemap is a recommendation about what to index. Therefore every address in it should be one you would happily see in search results.
Leave out redirects, error pages and anything carrying a canonical tag that points elsewhere. In fact, listing those contradicts the signal you already sent.
Tracking parameters cause the same problem quietly. Because /page/ and /page/?utm_source=mail look like two addresses, the tool strips those parameters as it reads.
The Fifty Thousand Line
One sitemap file holds 50,000 addresses and 50 megabytes, uncompressed. Above that, split the list into several files and write a small index file naming them. Most sites never come close, so treat the limit as a ceiling rather than a target.
A smaller file has a quiet advantage anyway. Since problems are easier to spot in a short list, many teams split by section instead of waiting for the cap. One file for articles, one for products, one for everything else.
Building a Sitemap File With Denwix
Paste, tidy, save. Because nothing gets crawled, the whole thing finishes in seconds.
- 1
Gather your addresses
Export them from your CMS, or copy them out of a crawl report. One per line is all the format there is.
- 2
Type it in, paste it, or open a saved file
Drop the list into the box, or load a .txt or .csv from your disk. The XML appears beside it immediately.
- 3
Choose your tidying
Drop repeats, strip tracking parameters and sort alphabetically. Each switch takes effect while you watch.
- 4
Save and upload
Download
sitemap.xml, upload it to the top folder of your site, then mention it in robots.txt.
Why Build A Sitemap This Way
Crawler-based builders take an email address and an hour. Instead, this one takes a list and about four seconds.
No crawl, no waiting
You already know your addresses, so nothing needs discovering. As a result there is no queue and no report to collect later.
Tracking junk removed
Seventeen common parameters come off automatically, from utm_source to fbclid. Therefore one page stays one address.
Repeats collapse
Exports duplicate addresses constantly. Since a repeat helps nobody, the tool keeps the first and counts the rest as skipped.
Characters escaped correctly
An ampersand inside an address breaks raw XML. So the output escapes them properly, and the file parses first time.
Bad lines reported
Anything that is not an http address gets counted as skipped. Then you can see at a glance whether the export was clean.
Your list stays private
Unpublished addresses often sit in these lists. Because the work happens in this tab, none of them reaches a server.
Keeping A Sitemap Useful
A stale sitemap is worse than none, because it spends crawl budget on nothing. A few routines keep the file current.
- List canonical addresses only. Every entry should be a page you want indexed. Otherwise the sitemap argues with your canonical tags.
- Keep lastmod honest. Search engines learn whether your dates mean anything. So a file that claims everything changed today gets ignored.
- Match the protocol exactly. Addresses must be absolute and on the same host as the sitemap itself. A relative path is simply skipped.
- Mention its address in robots.txt. One Sitemap line tells every crawler where to look. Meanwhile Search Console submission covers Google specifically.
- Split large lists. Past 50,000 addresses, break the file up and add an index. Then each part stays small enough to parse quickly.
- Rebuild after big changes. A migration or a bulk delete leaves dead entries behind. Therefore regenerate the file once the dust settles.
Where Sitemaps Go Wrong
These three are common, and all three waste the crawling you were trying to encourage.
Listing blocked pages
A sitemap entry that robots.txt blocks sends two opposite signals. So decide which one you meant, then remove the other.
Chasing priority numbers
Priority has never moved a ranking anywhere. Rather than tune it, spend the time on the pages themselves.
Letting it go stale
Deleted pages linger in old files for months. As a result crawlers keep asking for addresses that return 404.
Sitemap Questions Answered
Which folder should hold the file?
In the top folder of the site, for example example.com/sitemap.xml. A sitemap may only cover URLs in its own folder or deeper, so placing it at the root is simplest. Then add the Sitemap line to your robots.txt.
Will a sitemap lift my positions in search?
No, and be wary of any claim that says it does. It helps discovery, which is a different job. In short, it gets pages found sooner, then the pages have to earn their own results.
Are changefreq and priority worth filling in?
Google skips both tags and has stated so more than once. Leave them out if you like tidy files. Still, they break nothing, so keeping them costs you only a few bytes.
How frequently should I make a fresh sitemap?
Whenever the list of pages changes meaningfully. A blog that posts weekly can rebuild weekly. Meanwhile a shop with daily stock changes is better off generating the file automatically.
Will the generator add image or video entries?
Those need the image and video extensions, which this tool does not write. It produces a standard urlset of page addresses, which is what most sites actually need. If you run a gallery or a video library, a plugin that reads your media library will serve you better.
Is my list of addresses uploaded?
No. The parsing, the tidying and the XML all happen inside your browser. Because these lists often contain pages you have not published yet, that matters more than it sounds.
Your Next Moves Once the Sitemap Is Live
Each tool handles a separate piece of the crawl work. That keeps every one of them free.
Robots.txt Generator
Write the file that points crawlers at your sitemap.
Open tool →HTTP Status Code Checker
Confirm an address answers with 200 before you list it.
Open tool →Schema Markup Generator
Describe a page in JSON-LD so search engines understand it.
Open tool →
Turn That List Into A Sitemap
Paste the addresses, pick your tidying, then download the file. No crawl queue to wait in and no account to make.