CSV-to-Sitemap Converter
Paste or upload a CSV of URLs and get a valid XML sitemap. Map your columns, clean up the URLs, convert messy dates, skip invalid rows with a clear report, and split large lists with a sitemap index.
- Any CSV or TSV, with or without headers
- Fixes dates and URLs for you
- Reports every row it skipped
Want to check the result? Use the XML Sitemap Validator.
Which columns the converter understands
Only the URL column is required. The converter recognises common header names automatically and lets you pick columns by hand if it guesses wrong.
| Column | Required | Accepted values |
|---|---|---|
| URL (url, loc, link, address, page) | Yes | A full URL, or a path if you give a base URL |
| Last modified (lastmod, updated, date) | No | ISO dates, DD/MM/YYYY or MM/DD/YYYY, month names, Excel date numbers and Unix timestamps |
| Change frequency (changefreq, frequency) | No | always, hourly, daily, weekly, monthly, yearly or never |
| Priority (priority) | No | 0.0 to 1.0 (a 1 to 10 scale is converted) |
| Image URL (image, image_url) | No | A full URL: added as an image entry for that page |
Date formats the converter fixes for you
Sitemaps need W3C dates. Spreadsheets rarely have them. These are converted automatically.
| You have | It becomes |
|---|---|
| 2026-10-14 | 2026-10-14 (kept as is) |
| 14/10/2026 or 10/14/2026 | 2026-10-14 (day-first or month-first, your choice when ambiguous) |
| Oct 14, 2026 or 14 October 2026 | 2026-10-14 |
| 2026-10-14 09:30 | 2026-10-14T09:30:00Z (UTC assumed, and you are told) |
| 45943 (an Excel date number) | The matching calendar date |
| 1760400000 (a Unix timestamp) | The matching calendar date |
What usually goes wrong with spreadsheet sitemaps, and how it is handled
The converter checks every row and tells you what it did.
Relative or broken URLs
Paths are made absolute with your base URL. Rows that still aren't valid URLs are skipped and listed with the reason.
Duplicates
The same URL on several rows is kept once. Optionally, trailing-slash and tracking-parameter variants are merged too.
Wrong or missing dates
Unreadable dates are reported, and the row is still included without a lastmod unless you choose otherwise.
Special characters
Accents and symbols in URLs are encoded properly and & is escaped, so the XML stays valid.
Odd delimiters and quotes
Commas, semicolons, tabs and pipes are detected, and quoted fields with commas or line breaks are read correctly.
Too many rows
More than 50,000 URLs are split into several files with a sitemap index.
What a CSV to XML sitemap converter does and when to use one
URL lists usually live in spreadsheets: a CMS export, a crawler report, a database query or a migration plan. A CSV to sitemap converter turns that table into a valid XML sitemap. You map the column that holds the URLs, optionally map dates and other fields, and the tool writes the XML with the right structure, escaping and file splits.
The hard part is rarely the XML. It is the data. Spreadsheets mix date formats, leave out the domain, keep tracking parameters and repeat rows. CSV itself is loosely defined: RFC 4180 only documents the common format, and real files vary in delimiter, quoting and encoding. A good converter cleans these problems and reports what it changed or skipped.
The output must still follow the sitemaps.org protocol: absolute URLs, W3C dates and no more than 50,000 URLs or 50 MB per file. Use this tool when you already have the list. If you only have a site address, a crawl-based generator is the simpler route.
When to convert a CSV into a sitemap
Reach for this when the URL list already exists in a table and a crawl would be slower or less accurate.
From a CMS or database export
Export published pages, products or posts, with their update dates, and convert them directly. This often gives a more accurate list than a crawl, including pages with few internal links.
From a crawler report
Filter a crawl export down to indexable, canonical, 200-status pages, save those as CSV and convert. You control exactly which pages reach the sitemap.
During a migration
Once you have a final list of new URLs in a mapping sheet, convert the new-URL column into a sitemap to submit after launch. Keep old URLs out of it.
For very large catalogues
Lists above 50,000 URLs need several files and an index. The converter splits the rows and builds the sitemap index for you.
When dates are a mess
If your sheet mixes DD/MM/YYYY, month names and Excel date numbers, the tool converts them to the W3C format, so lastmod is valid instead of silently rejected.
When someone else gives you a list
A client or developer sends a spreadsheet of pages. Convert it, read the skipped-row report, and send back a list of problems along with the file.
Spreadsheet mistakes that break a sitemap
Most CSV problems come from how spreadsheet software treats data. Check these before you convert.
Ambiguous dates
What goes wrong: A date such as 03/04/2026 is 3 April in one country and 4 March in another. Converting it the wrong way gives every page a wrong, but valid-looking, lastmod.
The fix: Tell the converter whether your dates are day-first or month-first, and spot-check a few rows afterwards. If you cannot be sure, leave lastmod out.
Paths without a domain
What goes wrong: A column of /about and /contact values is not a valid sitemap entry. Sitemap URLs must be absolute and include the protocol.
The fix: Enter your site's address as the base URL so paths become full addresses, and make sure it matches the canonical protocol and host, including www or not.
Including pages that should not be indexed
What goes wrong: Exports often contain redirected, noindex, parameter and duplicate-content URLs. Converting the whole sheet puts all of them in the sitemap.
The fix: Filter the sheet to canonical, indexable, 200-status pages first. Then validate the finished sitemap to catch what slipped through.
Tracking parameters and trailing-slash variants
What goes wrong: The same page may appear as /page, /page/ and /page?utm_source=x. Duplicates in a sitemap conflict with your canonical choice.
The fix: Pick the one canonical form, and use the merge options to collapse variants. Keep only the version your canonical tag names.
Encoding and delimiter surprises
What goes wrong: Excel may save with a semicolon delimiter or a different encoding. Accented characters, or a byte order mark at the start of the file, can turn into garbage in the output.
The fix: Export as CSV in UTF-8, or paste the copied cells. Let the tool detect the delimiter, and read the report for rows it could not parse.
Ignoring the skipped-row report
What goes wrong: Rows with invalid URLs are left out so that the sitemap still builds. If you do not read the report, pages quietly go missing.
The fix: Check the list of skipped rows, fix the source data, and convert again. The report gives the row number, value and reason.
CSV and sitemap conversion terms explained
- CSV
- Comma-separated values: a plain-text table with one record per line. The format is loosely standardised, so delimiters and quoting can differ between programs.
- TSV
- Tab-separated values. Copying cells from Excel or Google Sheets and pasting them gives you tab-separated text, which the tool can read without conversion.
- Column mapping
- Telling the converter which column holds URLs, dates, change frequencies or image links, when header names are not recognised automatically.
- Base URL
- The site address, such as
https://example.com, added in front of relative paths so they become full URLs the sitemap can use. - W3C datetime
- The date format
lastmodrequires, such as2026-10-14. Values in other formats must be converted before they can go in a sitemap. - Byte order mark (BOM)
- Invisible bytes some programs add at the start of a UTF-8 file. A good CSV reader strips them so the first column name is not corrupted.
- URL normalisation
- Making variants of one address identical, for example by removing tracking parameters, so one page appears once in the file.
- Sitemap index
- A file that lists several sitemap files. It is created automatically when a list passes the 50,000-URL limit for a single file.
Related tools, guides and services
After the conversion, check the file and put it to work.
XML Sitemap Validator
Check the converted file for errors, redirects, noindex pages and blocked URLs.
ToolSitemap to URL List Converter
Go the other way and turn an existing sitemap into a spreadsheet-ready list.
ToolXML Sitemap Generator
Crawl your site instead when you do not have a URL list.
ToolRedirect Mapping Tool
Build the old-to-new URL map that often produces the list you convert here.
GuideRedesign SEO migration checklist
Where a new sitemap fits into the launch and post-launch checks.
ServiceSEO migration service
Get help planning URLs, redirects and sitemaps for a redesign or domain change.
Built by
Madhav Kushwaha
SEO, AEO, GEO & Digital Marketing Consultant in Kathmandu, Nepal, and trainer at ODcrU Academy and TechAxis Institute. I built this converter because URL lists usually live in spreadsheets: exports from a CMS, a crawler or analytics. Turning them into a valid sitemap should take a minute, not a script.
CSV-to-Sitemap Converter: Frequently Asked Questions
More free SEO tools
Crawling and indexing are connected: use these tools together to keep search engines pointed at the right pages.