How this tool works
Paste XML, choose a local XML file or explicitly fetch a public HTTPS sitemap that permits browser access. The parser recognizes urlset and sitemapindex separately and extracts only their direct loc and lastmod children. It excludes image and video extension locations and does not recursively fetch child files.
Direct sitemap loc entries → distinct page or child-sitemap rows; extension image URLs are excludedA worked example
The sample urlset contains two unique HTTPS page URLs on example.com. An index with two sitemap records instead reports two child sitemap files, not two indexed pages. Repeated locations remain visible and contribute to the separate duplicate count.
Good to know
Up to 2,000,000 pasted characters or 2 MB fetched/local files and 10,000 records per analysis. Fetching is direct and can fail because the remote site does not allow CORS; paste or local-file mode remains available. DTDs, entity declarations and malformed XML are rejected. An extracted URL is not evidence of search indexing.
Reference: Official reference (opens in a new tab) ↗
Sitemap entries and indexed pages are different counts
A sitemap is a discovery document published by a website. Search engines independently decide whether to crawl and index each page. Comparing the list with a Search Console export can reveal missing intended URLs, but this tool has no access to an engine’s current index.
A sitemapindex points to other sitemap files. Counting those file locations as article pages creates a misleading total. The XML sitemap generator and editor performs the inverse task: it creates a page-list document from explicitly entered URLs rather than extracting URLs from an existing file.
Inspect the namespace before mixing different loc fields
Image and video extensions may also contain elements called loc. Their namespace and position distinguish an asset location from a page URL. The extractor reads the direct protocol entry rather than grabbing every element with a familiar name from anywhere in the document.
Remote fetches use the browser’s ordinary cross-origin rules and no public scraping proxy. A source that opens in a browser tab can still disallow a script on another origin from reading it. Download its XML manually and use the local file control when you are authorized to inspect it; no upload to our server is needed.
A few questions, answered
Why can a sitemap open in a tab but fail Fetch here?
The source may not permit cross-origin script access. Use paste or the local XML file option.
Does a sitemapindex record represent one indexed article?
No. It points to a child sitemap file, which can contain many URLs.