We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Extract URL lists from Sitemap XML code for SEO analysis, web scraping, or content auditing.
Enter Sitemap XML content to start extraction
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
Paste the XML text and the extractor lists the text found in <loc> elements, in document order, one value per line. A URL set uses <urlset> and its <loc> values identify pages. A sitemap index uses <sitemapindex>; its locations identify child sitemap files instead. The output is a flat list, so identify the document root before treating every result as a page address. The Sitemap protocol describes both structures and the role of <loc>. Sitemaps.org: XML format.
Paste the XML contents, not a sitemap URL. The tool reads text supplied in the page; it does not fetch the address, follow an index to child files, or retrieve each listed page. XML parsing returns location element text only. Dates and other sitemap metadata are not included in the result.
The extracted count tells you how many location values were found. It does not mean that those addresses are unique, publicly reachable, allowed by a site’s crawl rules, or present in a search index. Repeated entries can remain repeated in the output. No page request, HTTP status check, redirect check, robots review, or search-index lookup is performed.
The standard Sitemap protocol uses XML tags such as <urlset>, <url>, and <loc>; optional fields such as <lastmod>, <changefreq>, and <priority> convey other information and are not location values. This extractor is for collecting those location strings, not validating all protocol requirements.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Obtain the XML file contents from your site or a saved copy. This page accepts pasted text; entering only an address such as https://example.com/sitemap.xml does not make it download the file.
Use the example as a format reference or paste your document into the input. Include the opening and closing tags when available so you can catch incomplete copies and understand whether the root is <urlset> or <sitemapindex>.
Review the result panel for the number of extracted entries and scan the line-by-line output. If no locations appear, check whether the XML is complete and whether it contains unprefixed <loc> tags that can be read.
Copy the values into your text editor, spreadsheet, or local workflow. Apply your own duplicate checks, fetch tests, and index-status checks if those are part of the task.
For a <urlset>, each location is intended to identify a page. For a <sitemapindex>, the location points to a sitemap document that must be obtained and examined separately if you need its child page locations. The extractor does not recurse, so a list from an index is not the combined list of all pages under its child files.
Use cases
See how the tool fits into real work and everyday tasks.
A site owner pastes an exported URL set and copies the locations into a working sheet before separately checking status codes, canonical pages, or index coverage.
An analyst pastes sitemap-index XML to see its child sitemap addresses. The output helps locate files for a later review; the child files are not automatically opened.
A developer copies the newline-separated text as input to a local script or comparison. The copied values still need validation appropriate to that script and its purpose.
Q&A
Find concise answers to common questions and confusing cases.
No. Paste the XML document text. The page does not request a remote sitemap address.
No. It lists the index’s own <loc> values, which point to child sitemap files. The tool does not fetch or recursively parse those files.
The result contains location text only. Fields such as <lastmod>, change frequency, and priority are not part of the extracted list.
No. Extraction does not visit the listed locations or query a search engine. It only surfaces text from the pasted XML.
Notes
Review scope, result limitations, and important precautions before use.
<loc>...</loc> patterns, but this does not repair or validate the document.Related
Discover related tools, collections, and available API capabilities.