Incomplete site analysis: why your verdict is partial

In brief

This signal does not describe a defect in your pages: it says the monitoring could not analyse them all, so this crawl's verdict does not cover the whole site. While it is open, read "no regression detected" as "no regression detected on the part that was analysed".

CriticalP3 — Quality

What is it?

Seogard retrieved the list of pages from the sitemap but could not complete the analysis on all of them. Every missing page is tied to the cause that explains it, and pages no counter explains are reported separately.

Why it hurts SEO and AI

The risk is not the missing page, it is the conclusion. A report saying "no regression" computed on a fraction of the site reads as a green light while nothing was checked elsewhere. Google and answer engines do see the pages the monitoring missed.

When it is NOT a problem

Your firewall deliberately blocks every external robot: partial coverage is a deliberate choice, not a surprise. You can mute the rule in that case.
A handful of pages are missing out of several thousand on a site that changes during the crawl: the alert stays informational and closes by itself on the next crawl.

Before

# Crawl finished, verdict shown
7,442 pages in the sitemap — no regression detected
# ... but only 1,024 pages were analysed end to end

After

# The crawler is allowed through the firewall
7,442 pages in the sitemap — 7,442 analysed
# the verdict now covers the whole site

The figure shown before the fix was not wrong, it was incomplete — and nothing said so. That missing signal is what this rule restores.

How to fix it

Open the alert: it lists each cause separately with its own page count. Two causes are never added together, and the largest one tells you where to start.
If pages are blocked by a firewall, allow the monitoring crawler through your WAF or CDN, by User-Agent or by IP range.
If pages are not retrieved, check response times and server errors on the URLs concerned: the crawler gives up on a page that does not answer.
If pages show up as unexplained, report it: that is a limitation of our instrumentation, not of your site.
Run another crawl and check that the alert closes by itself.

This scan checks technical compliance: viewport, charset, HTTPS, hreflang

Is this issue on your site?

Can a robot analyse your site end to end? Enter a URL: Seogard attempts the HTTP fetch then the JavaScript render, and tells you what it could actually see.

By clicking Scan, I certify that I own this site or have permission to crawl it.

No credit card
Result in ~30 s

What you get back

The next crawl's verdict covers the whole site. The value is not a better score, it is knowing what your report is based on.

Seogard catches this regression automatically — through its continuous SEO monitoring.

Frequently asked questions

Does this mean my site has an SEO problem?

Not directly. This signal is about the measurement, not your pages. It does have a real SEO consequence though: while it is open, a regression may exist on the unanalysed pages without anyone seeing it.

Why are some pages counted as "unexplained"?

Because we refuse to assign them a cause we did not measure. A missing counter is shown as such rather than folded into a plausible explanation.

Do redirects count as missing pages?

No. A page that redirects does not need to be rendered: it leaves the calculation instead of being counted as a failure.

Can this alert block a deployment?

Yes, by design. In strict mode, a check that did not cover the whole site is not a check that passed. If your site is permanently only partially analysable, mute the rule or pick a less strict mode.

Updated July 10, 2026