Sitemap URL extractor
Extract all page URLs from a sitemap.xml or sitemap index URL, then copy or export the list to CSV for SEO audits.
Extract from sitemap
Fetches the sitemap over HTTPS and follows sitemap index files. Up to 10,000 URLs and 50 nested sitemaps; each file is capped at 2 MB.
URLs
Enter a sitemap URL and extract to list every page URL.
What is an XML sitemap?
An XML sitemap is a machine-readable URL list that helps search engines discover canonical pages. Standard sitemap files use a <urlset> with <loc> entries, while large sites often use a sitemap index that points to many child sitemap files.
Sitemaps support discovery, but they do not guarantee indexing. They are still one of the fastest ways to build a URL inventory for audits, migrations, and coverage checks.
Why use a sitemap URL extractor?
Manual XML copying is slow and error-prone on large sites. A sitemap extractor gives you a flat URL list you can sort, filter, and map in spreadsheets or scripts within minutes.
SEO teams use exports to compare sitemap coverage with indexed pages, prepare redirect maps, and audit architecture changes. Content teams use them to organize update workflows by URL pattern.
How to extract URLs from sitemap.xml
Paste a public HTTPS sitemap URL and click Extract URLs. The tool fetches the XML, reads <loc> entries, and if the source is a sitemap index, follows child sitemap URLs recursively.
Results are deduplicated and returned to your browser as a plain list. You can copy the list directly or download CSV for Excel, Google Sheets, Screaming Frog, or migration checklists.
Current guardrails: 10,000 URLs max, 50 nested sitemap files, depth 4, 2 MB per XML response, and 8-second fetch timeout. If a guardrail is hit, the result is marked truncated.
Sitemap index vs URL set
A <urlset> sitemap contains page URLs directly. A <sitemapindex> file contains links to other sitemap files. Many CMS platforms publish an index at /sitemap.xml and split URLs into post, page, product, and category sitemaps.
If extraction returns no URLs, open the same URL in your browser first, confirm the response is XML, then check robots.txt for alternate Sitemap: locations.
Privacy, limits, and verification workflow
This tool only accepts public HTTPS sitemap URLs and blocks localhost or private-network targets. Exported URL lists are not stored after the response is sent.
After export, compare the URL list with your Search Console data. Prioritize URLs with impressions but weak CTR, and pages missing from sitemap exports that should be canonical.
Frequently asked questions
How do I get a list of all URLs from a WordPress sitemap?
Use the sitemap URL from robots.txt or try common paths like /sitemap.xml, /sitemap_index.xml, or /wp-sitemap.xml. Paste that HTTPS URL here and run extraction. The tool follows nested indexes and returns one deduplicated URL list you can copy or export as CSV.
How do I convert sitemap.xml to CSV for Excel or Sheets?
Paste the live HTTPS sitemap URL and click Extract URLs. Then use Download CSV to save a one-column URL file that opens directly in Excel, Google Sheets, or Numbers. You can also copy and paste the URL list into any sheet.
How can I find a website sitemap URL quickly?
Start with /sitemap.xml. If it is missing, open /robots.txt and look for one or more Sitemap: lines. Common variants include /sitemap_index.xml and /wp-sitemap.xml. Submit the final HTTPS sitemap URL to this extractor.
Can I extract URLs from a competitor sitemap?
Yes, if the sitemap is publicly accessible over HTTPS and not blocked. Teams often use this for competitor structure audits and content gap reviews. Always follow each site's terms and legal access boundaries.
Does this sitemap extractor support nested index files?
Yes. When you submit a sitemap index, the extractor follows child sitemap links recursively, deduplicates URLs, and returns a combined list until configured URL, file-count, or depth limits are reached.
Why does extraction stop or return truncated results?
This tool caps extraction at 10,000 URLs, 50 nested sitemap files, depth 4, and 2 MB per XML fetch. If any limit is reached, results are flagged as truncated. Very large sites may require staged extraction or crawler-based workflows.
Why is my sitemap URL failing in the extractor?
Common causes include wrong URL path, 4xx/5xx errors, blocked fetch requests, HTML error responses, and non-HTTPS links. Open the exact URL in an incognito window and confirm raw XML renders before retrying.
Is it safe to parse staging or confidential sitemap URLs?
Use this only for public HTTPS sitemap URLs. The server performs a one-time fetch to return URLs and does not retain your exported list after response. Avoid submitting internal, staging, or confidential paths unless they are intentionally public.
Sitemap extractor vs Google Search Console: what is different?
Google Search Console reports indexing and sitemap processing for verified properties. This extractor simply parses public sitemap XML and exports URLs without account connection. Use this tool for list building and Search Console for index diagnostics.
Related tools
Google SERP snippet preview
Google SERP simulator to test title tags, meta descriptions, and mobile truncation before publishing.
JSON-LD / Schema.org extractor
Extract JSON-LD from any public HTTPS page and review schema types in seconds.
OG image generator
Free OG image maker with 1200×630 templates, X header variants, and instant download.
Related reading
What Google Sees: A Deep Dive into JSON-LD Metadata Harvesting
Analyze Git Repositories in GitHub Actions Using Gitingest
