New content waits in line
When a sitemap returns 404 or 5xx, Google falls back to what it already knows. Published and updated pages are discovered on the crawler’s schedule, not yours.
Sitemaps are how you hand search engines the list of URLs you want crawled. When one breaks, the Sitemap: line still sits in robots.txt and the site still loads — the only symptom is slower indexing, weeks later.
Danger severity: you get the alert within the hour, not in tomorrow's digest.
Nothing on the site breaks. Your newest pages simply wait far longer to be discovered.
When a sitemap returns 404 or 5xx, Google falls back to what it already knows. Published and updated pages are discovered on the crawler’s schedule, not yours.
A missing XML declaration or a structure that fails protocol validation can make a crawler reject the entire sitemap — not just the bad line. Every URL inside goes unsubmitted.
The protocol stops at 50 MB and 50,000 URLs. Generators rarely warn you when a file crosses the line, and the entries that fall off the end are usually the newest.
Three steps, running every day, on something nobody looks at twice a year.
The first crawl saves every sitemap declared in your robots.txt as it should be. That value is what every later run is compared against.
Each sitemap and every child of a sitemap index is requested, parsed against the sitemaps.org protocol and measured.
Danger-level findings go out right after the crawl batch. Milder ones wait for the daily digest, so the urgent one stands out.
The stored value is your desired state, not a guess. When a later run differs you get both versions side by side — and if the change was intentional, one click adopts it as the new baseline.
This one reaches you within the hour, because the damage starts before the next digest would arrive. Every test's severity can be overridden per site, so your inbox stays useful.
Pick the frequency and the user agent Wygard should send, switch on JS rendering if your pages need it, and the rest needs no attention.
Three checks run against every sitemap declared in robots.txt, including each child of a sitemap index.
| Test | What it catches | Scope | Severity |
|---|---|---|---|
| SitemapGroup — status code | A sitemap that was 200 now returns 404 or 5xx, or a child of the index is unreachable. |
Web · Basic | Danger |
| SitemapGroup — validity & format | A malformed XML declaration, or a file that fails sitemaps.org protocol validation. | Web · Basic | Danger |
| SitemapGroup — size & limit | The file passes 50 MB or 50,000 <loc> entries, so the tail may stop being read. |
Web · Basic | Heads-up |
What the checks do, and what they don’t.
Every sitemap your robots.txt declares, plus each child sitemap referenced by a sitemap index.
Update the Sitemap: line in robots.txt. The robots.txt live sitemap check catches the case where the file moved but the old URL is still declared.
No. These checks confirm the sitemap itself is reachable, parseable and within the protocol limits. Individual URLs are watched by the per-URL tests you add.
“This app has completely transformed how we manage our SEO. The real-time alerts ensure we never miss an issue. It's a game-changer for protecting our rankings!”
Trust, but verify. You build the site — Wygard makes sure your key SEO elements work as intended.
How quickly would you notice if your canonical tags changed? We catch it for you.
Don't waste time on massive crawls and endless data. With 15 years of hands-on SEO experience, we know how to focus on what really matters.
You don't have to be an SEO expert — your site still deserves expert monitoring. That's exactly what our tool delivers.
Every online business deserves protection. No matter the size.
The checks that most often break for the same reason.
Availability, size, syntax, sitemap references and content of the file crawlers read first.
See the checksThe status code of every monitored URL and the full redirect chain behind it.
See the checksThe meta robots tag that decides whether a page can be indexed at all.
See the checks