Sitemap URL Extractor
How to use Sitemap URL Extractor
- 1
Provide your sitemap
Paste the raw XML of your sitemap into the XML box, or enter a sitemap URL to fetch it automatically.
- 2
Extract the URLs
Click 'Extract URLs' for pasted XML, or 'Fetch and Extract' to download and parse a sitemap from its URL.
- 3
Review the results
Every link found inside <loc> tags is listed in the results area along with the total count.
- 4
Copy or download
Use 'Copy to Clipboard' or 'Download as Text File' to save the extracted URL list.
Working with XML Sitemaps: Extraction and Auditing
What an XML sitemap is
An XML sitemap is a structured file that lists the URLs you want search engines to know about, wrapped in a urlset element where each page is a url entry. The only required child of each entry is the loc tag, which holds the page's absolute URL; optional tags like lastmod, changefreq, and priority provide hints about freshness and importance. Search engines treat the sitemap as a discovery aid and a set of suggestions, not commands, so listing a URL does not force it to be crawled or indexed, but it does make the URL much easier to find.
Because the loc tag is where every real URL lives, extracting the contents of all loc tags gives you a clean, complete inventory of the pages a site is advertising to search engines. That inventory is the starting point for a wide range of SEO and migration tasks, which is exactly what this extractor produces.
Sitemap index files and nested sitemaps
Large sites rarely use a single flat sitemap. Instead they use a sitemap index file, a sitemapindex element whose entries each point to another sitemap file rather than to a page. A typical setup might have one index that references separate sitemaps for posts, pages, products, and images. When you extract URLs from an index file, the loc tags you get back are the URLs of the child sitemaps, not of individual pages, so you may need to extract from each child sitemap in turn to reach the actual page URLs.
Recognizing whether you are looking at an index or a leaf sitemap is half the battle. If the extracted URLs all end in .xml or .xml.gz, you are holding an index and should drill down one level. If they point to normal HTML pages, you have reached the real content.
The 50,000 URL and 50 MB limits
The sitemap protocol caps a single sitemap file at 50,000 URLs and 50 MB uncompressed. Sites that exceed either limit must split their URLs across multiple sitemap files and tie them together with a sitemap index, which is the main reason large sites use index files at all. Knowing these limits helps you sanity-check what you extract: if a single sitemap is returning far more than 50,000 URLs it is malformed, and if a big site exposes only one small sitemap it is probably incomplete and missing pages.
These ceilings also shape how you audit. When you pull a full URL list and the count lands suspiciously near a round number like 50,000, that is a strong signal the site has hit the limit and additional URLs are stranded in sitemaps you have not yet extracted.
Gzipped sitemaps
To stay under the size limit and save bandwidth, many sitemaps are served gzip-compressed with a .xml.gz extension. A gzipped sitemap is just a normal XML sitemap that has been compressed; search engines decompress it transparently. When you fetch one through this tool, the server handles the download, but if you are inspecting a .gz file by hand you will see binary gibberish rather than readable XML until it is decompressed. If pasting content directly, paste the decompressed XML, not the raw compressed bytes.
Compression is purely a transport optimization and changes nothing about the structure inside. Once decompressed, a gzipped sitemap has the same urlset, url, and loc elements as any other, and the same extraction logic applies.
Why extracting sitemap URLs is so useful
A flat list of every URL a site publishes is the backbone of practical SEO work. During a site migration, you extract the old site's sitemap to build a complete redirect map so that no URL is left to 404. For a content audit, the list feeds a crawler or a spreadsheet where you can check status codes, titles, and word counts page by page. For indexing checks, you can compare the URLs you submit against what Search Console reports as indexed, and the gap tells you which pages Google is ignoring.
The list is also the input to bulk tooling. You can pipe extracted URLs into a crawler like Screaming Frog, into a link checker, into a performance auditor, or into a script that probes each URL's HTTP headers. Starting from the canonical sitemap list, rather than crawling blindly, ensures you are auditing exactly the pages the site intends to expose.
Common pitfalls when extracting
The most frequent surprise is extracting an index file and thinking the site only has a handful of pages, when in fact those few URLs are child sitemaps each containing thousands of pages. Always check whether your results are sitemaps or actual pages before drawing conclusions. A second pitfall is assuming the sitemap is exhaustive: many content management systems generate sitemaps that omit certain page types, paginated archives, or recently published content, so a sitemap is a floor on a site's URLs, not a complete census.
Other gotchas include stale lastmod dates that do not reflect real changes, URLs in the sitemap that no longer return 200 (orphaned or deleted pages that were never pruned), and protocol or host mismatches where the sitemap lists http URLs while the site has moved to https. Extracting the URLs is the easy part; the value comes from cross-checking that list against what the server actually serves.
Fitting extraction into an SEO workflow
A clean repeatable workflow looks like this: find the sitemap, usually linked from robots.txt or located at the conventional /sitemap.xml path; extract the URLs, drilling through any index files until you reach real pages; export the list to a text file; then feed it into whatever audit or migration tool you are using. Because this extractor can both parse pasted XML and fetch a sitemap by URL, you can move from a raw sitemap to a usable URL list in seconds without writing any code.
Run extraction periodically rather than once. Comparing today's URL list against last month's surfaces newly published pages, quietly removed pages, and structural changes to the site, all of which are useful early signals for both SEO health and content governance.
Frequently asked questions
How does the sitemap URL extractor find links?
Can I paste XML or load a sitemap from a URL?
What if my XML is invalid or has no URLs?
Can I export the extracted URLs?
Is the tool free and is my data private?
Related tools
Keep going with these handy tools