XML Sitemap URL Extractor
Turn any sitemap or sitemap index into a clean, filterable list of URLs, and see at a glance how the site splits its pages across folders.
What the extractor reads from a sitemap
Each file is downloaded and parsed as XML. A sitemap index sends the extractor on to its child sitemaps, and their pages are collected into one list.
- Every page URL
- The loc of each url entry, with fragments removed and duplicates across files dropped.
- lastmod dates
- The last modified date declared for each URL, kept with its own entry rather than paired by position.
- Nested sitemap indexes
- Index files are followed level by level, up to three levels below the address you enter.
- Gzipped sitemaps
- Files ending in .xml.gz are unpacked before they are read.
- Per-sitemap status
- For each file: whether it is a urlset or a sitemapindex, how many entries it holds, its size, and any error such as HTTP 404, timed out or not a sitemap.
- Folder breakdown
- URLs counted by their first path segment, such as /blog or /product, sorted from largest to smallest.
- Skipped entries
- How many entries were invalid, repeated, or not followed because a limit was reached.
How to extract URLs from a sitemap
Find the sitemap address
Look for a Sitemap line in /robots.txt, or try /sitemap.xml or /sitemap_index.xml on the domain.
Paste it and run
Enter a sitemap or a sitemap index. Child sitemaps are fetched three at a time.
Check the sitemaps table
Any child sitemap with an error is a gap in what search engines receive. Fix those first.
Filter and export
Filter the URL list by any text, such as a folder or a product code, and download it as CSV for a crawler, spreadsheet or another tool.
One run reads up to 25 sitemap files and collects up to 2,000 URLs. Each file has about 15 seconds and may be up to 10 MiB, or 20 MiB once unpacked.
How to read the extracted list
- Sitemaps table
- Every file that was read, its depth, type, entry count and status. "OK" means it parsed cleanly.
- URL list with lastmod
- The pages the site asks to have crawled. Empty lastmod cells mean the site did not declare a date.
- Folder counts
- A quick picture of the site's structure. An unexpectedly large folder, such as /tag, often points to thin pages being submitted.
- Limit reached
- The run stopped at 2,000 URLs or 25 sitemaps. Paste a single child sitemap to read the rest of a large site in parts.
- Skipped: invalid, duplicate, not followed
- Invalid entries are not full http or https addresses. Duplicates appear in more than one place. Not followed means a limit or the depth cap stopped the extractor.
Sitemap problems it reveals
A child sitemap returns 404 or 500
Fix: Remove the dead entry from the sitemap index or fix the plugin or route that should generate it, then resubmit the index in Search Console.
Relative or malformed URLs in loc
Fix: Every loc must be a full absolute address with the protocol. Correct the generator so it writes https://example.com/page, not /page.
The same URL listed in several sitemaps
Fix: Pick one sitemap per URL. Duplicates are harmless but make coverage numbers in Search Console harder to read.
lastmod is the same date on every URL
Fix: That usually means the generator writes the build date. Use the real modified date of each page, or leave lastmod out, since Google only uses it when it is accurate.
Tag, author or filter pages flooding the sitemap
Fix: Exclude low-value archive types in your SEO plugin so the sitemap lists only pages you want in search.
The file is refused because it contains a DOCTYPE
Fix: Sitemaps should be plain XML starting with the xml declaration and a urlset or sitemapindex element. Remove the DOCTYPE line.
Who uses a sitemap extractor
- SEO auditors pulling a site's submitted URLs to compare against a crawl or Search Console.
- Content teams building a full inventory of posts before a cleanup or migration.
- Developers checking that a new sitemap plugin writes every section of the site.
- Marketers studying how a competitor organises products, categories and articles.
Compare the sitemap with what is indexed
A sitemap is the list of pages a site wants indexed, not proof that they are. Export the URLs, then check them against the Page indexing report in Search Console. URLs in the sitemap but not indexed point to quality, canonical or noindex problems. Indexed pages missing from the sitemap point to a generator that skips a section.
XML Sitemap Extractor FAQ
Short answers about the XML Sitemap Extractor.
Yes. It follows index files to their child sitemaps, up to three levels deep, and gathers all page URLs into one list.
2,000 URLs from up to 25 sitemap files per run. For bigger sites, run it on each child sitemap separately.
Yes. Gzipped sitemaps are unpacked and read, up to 20 MiB of unpacked XML per file.
Most sites declare it on a Sitemap line in robots.txt. Common locations are /sitemap.xml, /sitemap_index.xml and /wp-sitemap.xml.
Yes. Both the sitemaps table and the URL list can be filtered and downloaded as CSV.
The address you entered could not be read as a sitemap: it returned an error, was not XML, or was too large. Child sitemaps that fail do not stop the run, they are listed with their error.
Related SEO tools
Sitemap Generator
Crawl a site and get a ready XML sitemap.
1 free run a dayRobots.txt Analyzer
28 checks on a live robots.txt file.
1 free run a dayBulk Meta Extractor
Titles, descriptions and tags of 20 pages at once.
1 free run a daySite Audit Pro
Crawl up to 100 pages and get a technical health score.
1 free run a day