Sitemap Checker

A sitemap checker fetches an XML sitemap, or a text or RSS one, and checks its structure. It reads every page address in the file, follows an index to the child files and can request each listed URL to record its status code. The sitemap itself is a file that tells search engines which pages and files you consider important. It is a discovery aid, not a ranking boost.

Sitemap rules in plain English. Google keeps the rules short, which makes them easy to break by accident. URLs must be absolute and UTF-8 encoded. One sitemap can hold up to 50,000 URLs or 50 MB uncompressed. Bigger sites split the list into several files and tie them together with a sitemap index. Google reads XML, RSS and text sitemaps and has no favourites among them.

Two optional fields get less attention than people expect. Google ignores priority and change frequency. It uses the last modified date only when the dates are consistently accurate, so a build timestamp does more harm than good. Put the file at the site root. A sitemap in a subfolder only affects the URLs in that folder.

A sitemap checker is useful whenever discovery matters:

• After a migration, to confirm that new URLs are listed and old ones are gone.
• On a new site, where few outside links point to the pages yet.
• On a large catalogue, where navigation alone cannot reach every page.
• After a CMS or plugin update changes how the file is built.
• When Search Console reports sitemap errors or fewer discovered URLs.
• Before a campaign, to make sure the landing pages sit in the file Google reads.

It is also a smart first check when a page is live but has never shown up in search.

Every good sitemap check comes down to a few plain questions.

Is the file valid? A missing closing tag or a wrong namespace is easy to miss by eye. Malformed XML or an unreachable file can stop Google from reading the list at all.

Are the URLs absolute? Relative paths break the rules, and the file can still return a 200 while hiding the problem.

Do the listed pages work? A sitemap can be valid and still point at hundreds of redirects, 404 pages or noindex pages. Every entry should return a 200 and be allowed in search.

Which version do you prefer? Listing a URL is a weak canonical signal. It nudges Google toward that address, but it does not override a redirect or a canonical tag.

Is the list within the limits? A file over 50 MB or 50,000 URLs needs to be split, or part of it may be ignored.

Accurate last modified dates help Google schedule crawls. Unreliable dates are ignored, and priority and change frequency are ignored too. Traffsite turns those rules into a list of specific entries to fix.

The aim of a sitemap checker is a file that describes the site accurately and survives a Google fetch. Every listed URL is canonical, returns 200 and is allowed to be indexed. The file stays within the size limits, is encoded correctly and is reachable at the address you submitted.

That gives you:

• Faster discovery of new pages, especially on a large or recently launched site.
• Cleaner reporting, because the sitemap matches the URLs you want in search.
• Fewer wasted crawls on redirects, duplicates and error pages.
• A sitemap index that keeps large sites within the limits.
• A last modified date that reflects real content changes rather than a build timestamp.

The result is not a promise of indexing. It is a reliable map that gives Google a clear starting point.

Why use a sitemap checker instead of opening the file in a browser? A few reasons stand out.

• It validates structure. A missing closing tag or a wrong namespace is easy to miss by eye.
• It checks the listed URLs. A sitemap can be valid XML and still point at hundreds of error pages.
• It follows an index. Large sites rarely have one file, and the checker can walk the whole set.
• It counts entries. The 50,000 URL limit is easy to cross without noticing.
• It is fast and needs no setup. One sitemap takes seconds, which helps during a release.
• It creates a record. A before and after report shows what changed and what remains.

Traffsite does not decide which pages belong in the sitemap. It shows whether the current list is healthy.

Run your first sitemap check in six steps.

1. Paste the full sitemap address into the Traffsite box. It is often your domain followed by sitemap.xml.
2. Let the tool parse the file. If it is an index, confirm that every child sitemap loads.
3. Compare the URL count and file size with the limits. Split the file if either is close.
4. Scan the status of the listed URLs, then remove or redirect anything that returns a 4xx or 5xx.
5. Drop noindex pages and duplicates, so only canonical URLs remain.
6. Submit the fixed file in Search Console or reference it in robots.txt. Then run the sitemap checker again.

The tool suits anyone responsible for helping search engines find pages.

• SEO specialists use it during audits, migrations and index investigations.
• Developers use it to verify the output of a sitemap generator.
• Content editors use it to check that new articles or products are listed.
• Site owners use it after a relaunch to confirm the new pages are discoverable.
• Agencies use it to compare sitemap health across the sites they manage.

You do not need to read the sitemap protocol to use the result. A valid file, a healthy list and a successful submission cover the essentials.