Don't like ads? Go Ad-Free Today 

Sitemap XML Parser & URL Extractor

DataDeveloper

ADVERTISEMENT · REMOVE?

INPUT

Auto Process

Sitemap XML

Options

Output Format

Filter by lastmod

Sort by

Show validation warnings (missing fields, invalid priority, malformed dates)

OUTPUT

Client Side

Paste a sitemap above to extract URLs and metadata.

Extracted URLs

ADVERTISEMENT · REMOVE?

Guide

Sitemap XML Parser & URL Extractor

Paste any sitemap.xml or sitemap index file and instantly pull out every URL along with its lastmod, changefreq, and priority. The parser runs entirely in your browser using the native DOMParser, so nothing leaves the page. Filter by recency, sort by any column, export to Markdown, CSV, JSON, or a plain URL list, and catch invalid priorities or malformed dates before they reach search engines.

How to Use

Paste the contents of a sitemap into the input box, or upload an .xml file.
The tool detects whether the root element is <urlset> or <sitemapindex> and parses every entry.
Pick an output format — Markdown table for SEO docs, CSV for spreadsheets, JSON for scripts, or a plain URL list for quick crawling.
Use the lastmod filter to find pages updated in the last 7/30/90/365 days, or to surface entries that are missing a lastmod entirely.
Sort by URL, lastmod, priority, or changefreq to spot patterns or outliers.
Review the validation summary, then click Copy or Download to save the result.

Features

Auto-detects sitemap type – Handles both <urlset> sitemaps and <sitemapindex> nested indexes.
Full metadata extraction – Pulls loc, lastmod, changefreq, and priority for every entry.
Multiple output formats – Markdown table, CSV, JSON, or plain URL list, all generated on the fly.
Date filtering – Restrict results to entries updated in the last 7, 30, 90, or 365 days, or isolate entries missing lastmod.
Smart sorting – Sort by URL, lastmod (newest or oldest first), priority, or changefreq.
Built-in validation – Flags malformed URLs, invalid W3C Datetime formats, unknown changefreq values, out-of-range priorities, and entries exceeding the 50,000 limit per the sitemaps.org spec.
Client-side only – Uses the browser’s native DOMParser; your sitemap never leaves the page.
One-click examples – Load a sample urlset or sitemapindex to see the tool in action.

 FAQ

What is the difference between a sitemap and a sitemap index?

A regular sitemap (root element <urlset>) lists individual page URLs that you want search engines to crawl. A sitemap index (root element <sitemapindex>) does not list pages directly — it lists pointers to other sitemap files. Indexes are used when a site has more than 50,000 URLs or when sitemaps are split by section (posts, pages, products, etc.), since the sitemaps.org spec limits a single sitemap to 50,000 URLs and 50 MB uncompressed.
What format does the lastmod field require?

The sitemaps.org protocol requires lastmod to use the W3C Datetime format, which is a profile of ISO 8601. The shortest valid form is a date like 2025-11-04; you can also include a time and timezone offset, for example 2025-11-04T15:30:00+00:00 or 2025-11-04T15:30:00Z. Other formats such as 11/04/2025 or Nov 4, 2025 are not compliant and may be ignored by crawlers.
What are valid values for changefreq and priority?

The changefreq element accepts one of these literal values: always, hourly, daily, weekly, monthly, yearly, or never. The priority element is a decimal between 0.0 and 1.0 indicating relative importance within your own site; the default if omitted is 0.5. Note that Google has publicly stated it largely ignores both fields when ranking, but they remain part of the spec and can be useful signals for other crawlers and for internal SEO audits.
Do search engines actually use the priority and changefreq values?

Google has confirmed that it ignores both priority and changefreq for ranking and crawl scheduling. Bing and other search engines treat them as hints at best. The lastmod element, however, is widely used as a signal of content freshness, provided it is accurate and not set to today's date for every URL. Many SEO audit workflows still inspect priority and changefreq internally to verify a site's own sitemap generation logic, even when those values do not directly influence search behavior.
Why does my XML fail to parse even though it looks correct?

Most parse errors come from a few sources: an unescaped ampersand in a URL (must be &), a UTF-8 byte order mark or whitespace before the <?xml ?> declaration, mismatched or unclosed tags, or an encoding declaration that does not match the actual file encoding. The DOMParser used by this tool follows the same rules as browsers, so any XML that fails to validate here will also fail in a strict crawler. Pasting the offending block into an XML validator and trimming the file in halves is the fastest way to localize the error.