Free Sitemap URL Extractor

The result is a clean list of the pages a site asks search engines to index. Each row holds the URL exactly as the sitemap writes it, and the lastmod date if the sitemap gives one. The table shows the first 500 rows; the copy button and both downloads hold every URL collected.

• A CSV file with two columns, loc and lastmod, ready for a spreadsheet or a crawler.
• A TXT file with one URL per line, for scripts and tools that take a plain list.
• A count of how many sitemaps were read, how many duplicate URLs were removed, and any sitemap that could not be read and why.

Nothing is sampled or estimated. If a sitemap fails to load, refuses our checker or holds broken XML, the result names it, and the list is marked as not complete instead of quietly missing those pages.

Enter a bare domain such as example.com and the tool works as a website URL extractor. It first finds the site's sitemaps the way search engines do: it reads robots.txt for Sitemap: lines, then tries the addresses that site builders and SEO plugins use, such as /sitemap.xml, /sitemap_index.xml and /wp-sitemap.xml. Every sitemap it finds is read and its URLs are merged into one list.

This gives you the URLs the site owner wants indexed, which is usually the useful set. A crawler that follows links finds a different set: it also picks up filtered category pages, session URLs and old pages that are still linked, and it misses pages nothing links to. Comparing the two lists is one of the fastest ways to find orphan pages and pages that should not be in the sitemap at all.

If the site has no sitemap at robots.txt or the common addresses, the result says so. Some sites keep their sitemap at an unusual address; if you know it, enter that URL directly.

Large sites split their URLs across many sitemaps and list those files in a sitemap index. The extractor reads the index, then fetches each child sitemap once, four at a time, and keeps the URLs in the order the sitemaps list them. An index that lists another index is followed too, even though the sitemap protocol does not allow nesting, because the goal here is the URL list, not a validation.

A URL listed in more than one sitemap appears once in the result, with the lastmod from the first sitemap that lists it, and the duplicate count tells you how many repeats were removed. Repeats across sitemaps are common on WordPress sites, where the same page can sit in a page sitemap and a category sitemap.

• Check them in bulk: paste the TXT file into a crawler to find URLs that answer 404, redirect or carry a noindex tag. A sitemap should list only pages that answer 200.
• Plan a migration: the CSV is the starting column of a redirect map, one row per URL that needs a new home.
• Study a competitor: sort by lastmod to see which pages they updated most recently, and count URLs per folder to see where their content effort goes.
• Compare with Search Console: URLs in the sitemap that Google reports as not indexed are the pages to improve or remove first.

Lastmod dates are worth a second look. Google uses them only when they match real changes to the page, so a sitemap where every URL shows today's date is telling search engines nothing useful.

One run reads up to 50 sitemaps beyond the first, up to 10 MB of each after unzipping, and collects up to 50,000 distinct URLs, the most one sitemap file may list. The whole run has a time limit of about a minute, which is usually enough for an index of 50 child sitemaps on a responsive server.

When any of these limits is reached, the result is marked as partial and says exactly what was left out: how many sitemaps were left unread, how many listed URLs were past the 50,000, and which sitemaps were cut short. To get the rest of a very large site, run the extractor on individual child sitemaps from the index, one at a time.