Sitemap to URLs
Enter a sitemap address and get every page URL in it as a plain list. Sitemap indexes are followed into each child sitemap, and .xml.gz files are unpacked for you.
Not sure where the sitemap is? Most sites list it on a Sitemap: line in /robots.txt, or serve it at /sitemap.xml or /sitemap_index.xml.
What you get
Every <loc> that names a page, in the order the sitemap lists them, with its <lastmod> date when there is one. Image, video and news extension URLs inside an entry are skipped, because they point at files, not pages. Duplicates across child sitemaps are counted and removed.
Filter the list by any text in the URL, such as /blog/ or ?lang=, then copy it or download it as TXT, or as CSV with the last-modified date and the child sitemap each URL came from.
Questions
- How big a sitemap can it read?
- Up to the protocol limit of 50,000 URLs per file, and up to 200 child sitemaps in an index. A file larger than about 25 MB uncompressed is read up to that point and marked as cut short, so you know the list is incomplete.
- Why does it ask for a quick check before the first fetch?
- Because a public tool that fetches any address on request is easy to abuse. One check covers the next fifteen minutes, so a sitemap index with many children only asks once.
- Does it store my sitemap or the URLs?
- No. The server fetches the file, reads it and sends the list back to your browser. Nothing is saved, and the filtering and downloads happen in your browser.
- Some of my URLs are missing. Why?
- Most often the sitemap index points at a child sitemap that returns an error or redirects to a page that is not a sitemap; those children are listed with the reason. A sitemap can also be generated per request and differ from what your CMS shows you.
- Can it read a sitemap behind a login or on an internal network?
- No. It fetches public addresses only, as any visitor would, and it identifies itself as
sitemaptourlsrather than as a search engine.