SEO

Sitemap Checker

Verify sitemap availability and structure.

Enter a domain (example.com) or a full URL. The file is fetched at https://domain/sitemap.xml from the FKINFAST server — not from your browser — and the result is not stored.

Results appear here. Enter a domain or URL, then select Check sitemap.

Domain Health Report

This page checks one thing. The report checks thirteen — and tells you what to fix first.

A one-off €14.90 report, delivered by email in minutes. Every finding comes with a concrete fix, prioritized.

  • DNS records (A/AAAA)
  • Nameservers (NS)
  • Mail servers (MX)
  • SPF record and policy
  • DMARC record and policy
  • DKIM record (common selectors)
  • HTTPS availability
  • HTTP to HTTPS redirect
  • TLS certificate (issuer, validity, expiry)
  • Security headers (HSTS, CSP…)
  • CAA records
  • robots.txt availability
  • sitemap.xml availability
Get the Domain Report€14.90 · One-time payment. No subscription.

How the sitemap check works

  1. Enter a domain (example.com) or a full URL, and submit the form.
  2. The FKINFAST server requests https://domain/sitemap.xml, following up to 5 redirects, and reads the response.
  3. The result shows the HTTP status, the file size, the number of URLs declared and whether the document is a valid XML sitemap.

The check runs from FKINFAST's server, not from your browser. The domain is not stored and no resolved IP address is returned to this page.

Result states

PASS
The site answered with a valid XML sitemap, and the number of declared URLs is shown.
WARNING
No sitemap was found (4xx), or the response is not a valid XML sitemap (for example a compressed file or an HTML error page).
UNKNOWN
No clear answer was read: timeout, connection or TLS failure, an unfollowable redirect, a server error (5xx), or a rejected destination.

Page-level errors are separate from these results. A validation error, rate limit, busy response, unavailable service or network failure is shown as an error, not as a WARNING result.

URL rules and limits

  • Enter a domain or a URL; the file is always fetched at https://domain/sitemap.xml on the standard port.
  • Loopback, private, link-local, multicast and cloud metadata destinations are blocked before any connection is made.
  • Up to 5 redirects are followed, with a 15-second deadline.
  • The file is read up to 256 KiB and URLs are counted up to 10,000 entries.
  • Sitemaps must be served uncompressed: gzip or brotli-only responses cannot be parsed and are reported as invalid.
  • Limited to 10 checks per 60 seconds per client IP.

What the check does not do

The check reads and validates the sitemap document only. It does not fetch the listed URLs, does not verify that they return 200, does not check lastmod dates and does not submit the sitemap to search engines.

Sitemap checker FAQ

What is the difference between urlset and sitemapindex?

urlset lists the pages themselves; sitemapindex lists other sitemap files. Both are valid — the checker accepts and counts URLs in either form.

Why is my compressed sitemap reported as invalid?

The checker reads plain XML only, so a sitemap served exclusively as a .gz archive or with forced compression cannot be parsed. Serve sitemap.xml uncompressed, or provide the standard .xml alongside any compressed copy.

Does the URL count include duplicates?

The count reflects the number of <loc> entries present in the document, up to 10,000. Duplicate URLs inside the sitemap are counted as written — search engines may ignore them.

Is a missing sitemap a real problem?

Not necessarily. Sitemaps help discovery but are optional; a small site with clear internal links is fine without one. They matter most for large or frequently updated sites — and a sitemap referenced from robots.txt is a common convenience.

Related tools