XML sitemap validator

The sitemaps.org protocol (checked 14 November 2026) allows at most 50,000 URLs and 50 MB uncompressed per file. Google's Search Central docs give the same limits. For a bigger site, split the URLs over several sitemaps and list them in a sitemap index.

The W3C datetime format: a date like 2026-11-14, or a full time with a time zone like 2026-11-14T09:30:00+00:00. A date like 14/11/2026, or a time with no zone, is not valid. Set lastmod to when the page content last really changed, not to the time the file was built.

It is not required, but it helps. A line like "Sitemap: https://example.com/sitemap.xml" in robots.txt lets any crawler find the file without being told. You can also submit the sitemap in Google Search Console and Bing Webmaster Tools.

No. Under the sitemaps.org protocol, a sitemap index lists sitemaps, and those files must be normal <urlset> sitemaps. If a child is itself an index, crawlers may not read the URLs inside it. This tool flags that as a nested index.

A sitemap should list the pages you want indexed, at their final address. A URL that redirects costs an extra request. A URL with noindex, or with a canonical pointing to another page, sends a mixed signal: the sitemap says "index this" while the page says "do not" or "index that one instead".

Twenty URLs spread evenly across the sitemap: always the first and the last, and the rest at equal steps between them. That catches problems in old and new sections, not just at the top. URLs on another host, or blocked by your robots.txt, are listed but not fetched.

Google's Search Central docs (checked 14 November 2026) say Google ignores priority and changefreq, and uses lastmod only when it is consistently accurate. This tool does not score priority or changefreq. It checks lastmod format and future dates.

At most 30 requests: your robots.txt, the sitemap (or up to two default paths when you enter a domain), up to 6 child sitemaps and 20 sampled pages. If your robots.txt blocks crawlers like ours, we stop and tell you. No AI model is used.

No. AI answer engines change their output frequently, and no vendor — including Leadee — can guarantee a ranking or a mention. Leadee publishes confidence intervals on every metric so you can see how much a result can vary run to run.

Leadee runs your prompt set against each AI engine on a weekly to daily schedule, depending on plan, through official vendor APIs (OpenAI, Gemini, Perplexity, Anthropic, DataForSEO) — never by scraping consumer chat interfaces — and reports mention rate, citation rate, average position, share of voice and sentiment with a 95% confidence interval.

Email support@leadee.ai or use Talk to an expert at https://leadee.ai/contact-sales — the Netbase JSC team behind Leadee replies by email or WhatsApp — or WhatsApp the CEO directly at https://wa.me/84937869689.