Parseur XML de Sitemap et extraiteur d'URL

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.

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 ou 2025-11-04T15:30:00Z. Other formats such as 11/04/2025 ou Nov 4, 2025 are not compliant and may be ignored by crawlers.

Le changefreq element accepts one of these literal values: always, hourly, daily, weekly, monthly, yearly, ou never. La 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.

Google has confirmed that it ignores both priority et 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 et changefreq internally to verify a site's own sitemap generation logic, even when those values do not directly influence search behavior.

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.