Sitemap URL Extractor

Read sitemap XML as urlset or sitemapindex data, keep core URLs separate from image-extension URLs, and review namespaces, dates, duplicates and file limits before exporting the rows you need.

Sitemap XML

Extract

Output

Sort

Include image extension URLsOnly affects All mode; Image mode always outputs images.Include metadata in exportsKeep lastmod/changefreq/priority/image counts where relevant.Dedupe output URLsPreserves the first occurrence while counts/findings still inspect source XML.Output HTTPS onlyA convenience filter, not a sitemap validity rule.

XML parsing happens on the pasted document in the browser. Child sitemaps are not fetched, URLs are not submitted, and HTTP status, canonical signals, robots rules, indexability and Google indexing are not checked. Site-wide analytics or advertising scripts, if enabled, are separate from the XML parsing itself.

A Sitemap URL Is the Direct Core <loc>, Not Every Element Named loc

Sitemap XML can contain extension namespaces for images, video, news and other metadata. Those extensions can also contain elements named loc. A simple “find every loc tag” search can mix image URLs into the primary page list. This parser reads direct core Sitemap children in the standard namespace, while image-extension URLs are kept in a separate set.

urlset and sitemapindex Answer Different Questions

A urlset lists content URLs. A sitemapindex lists sitemap files that must be fetched separately to discover the pages inside them. A child sitemap URL is therefore kept distinct from a content-page URL.

lastmod Should Describe Real Modification Time

A syntactically valid date is not automatically useful. lastmod should reflect meaningful modification of the URL or child sitemap, not the time your sitemap generator ran. Search engines can ignore unreliable dates.

50,000 Entries and 50 MB Are Per Sitemap File

The Sitemap protocol caps an uncompressed sitemap or sitemap index at 50,000 entries and 50 MB. Larger sites normally split URLs across multiple files and reference them from a sitemap index.

Pasted XML Cannot Prove the Original File Encoding or Location Scope

By the time XML is pasted into a textarea, the browser already has Unicode text. The byte count shown above is the UTF-8 size of that pasted text, not a forensic measurement of the original file bytes. The XML declaration can be checked for an encoding claim, but the original transfer encoding cannot be recovered from pasted text alone.

Sitemap placement also affects URL scope. Without the sitemap file's own URL, a pasted document can reveal mixed hosts or protocols, but it cannot prove whether every entry falls under the allowed path or a verified cross-site submission arrangement.

Extracted Does Not Mean Indexable

A URL can be perfectly valid sitemap XML while redirecting, returning 404, canonicalizing elsewhere, carrying noindex, being blocked from crawling or simply not being selected for indexing. Extraction is a data-inspection step, not an indexing verdict.

Google Ignores changefreq and priority

They remain part of the Sitemap protocol and are preserved in exports, but Google documents that it ignores those values. Do not spend maintenance effort tuning them as if they controlled crawl frequency or ranking priority.

Sitemaps.org protocol

Primary protocol reference for urlset/sitemapindex structure, loc, lastmod, limits and escaping requirements.

Google: Build and submit a sitemap

Google-specific sitemap guidance, including accepted formats and how Google treats optional fields.