Quick answer
NOTABIS reports only what its crawl could measure within the audit's page, request, and browser limits. The coverage panel shows measured HTTP pages, queued and skipped URLs, blocked pages, sitemap URLs, and rendered-browser measurements. A partial or blocked report is useful evidence, but it should not be read as a complete statement about every page on the site.
What the issue means
Coverage is the relationship between the URLs the crawler discovered and the URLs it was able to request and inspect. Discovery can come from the submitted origin, internal links, and applicable sitemap sources. A page can be discovered but remain unmeasured because the page limit was reached, a request failed, an edge service blocked the crawler, or the URL was outside the crawl scope.
HTTP coverage and browser coverage are separate. A page measured from its response HTML is not necessarily measured again with rendered DOM evidence, and a browser limit may be lower than the HTTP page limit.
Why it matters for SEO
A finding based on one reachable sample cannot describe pages outside that sample. Missing a high-value template can hide an issue; measuring only a subset can make a clean report less conclusive. Coverage also explains why a later audit can change without a code change when the discovered URL set, blocking, or crawl limits differ.
Search engines have their own crawling systems and resources. Improving NOTABIS coverage helps your investigation, but it does not replicate Googlebot or guarantee indexing.
How NOTABIS detects it
The report records http_pages, page_limit, urls_queued, urls_skipped, blocked_pages, sitemap_urls, browser_pages_measured, and browser_pages_limit. It assigns confidence from the crawl result: HIGH when the run completes without the listed limiting conditions, MEDIUM when sitemap access is unavailable, PARTIAL when the page limit is reached, LIMITED when no pages or too many requests fail, and BLOCKED when edge protection stops the crawl.
If no crawlable HTML pages are measured, the audit fails and cannot produce a valid page report. The exact limits depend on the account and audit configuration shown in the report; do not infer a universal limit from another site.
How to check it yourself
- Read the confidence label and its reason.
- Compare HTTP pages with Page limit used and review queued and skipped counts.
- Check blocked pages, request failures, and the sitemap summary.
- Compare rendered-browser pages with the browser-page limit.
- Inspect the sitemap and navigation for important URLs that do not appear in the measured set.
- Re-run a focused audit or a higher-capacity audit when you need more evidence, then compare the discovered URL sets.
A crawl reaching its page limit is not proof that the remaining pages are broken. It is a reason to qualify conclusions about them.
How to fix it
Make important pages discoverable through stable internal links and accurate sitemaps. Remove redirect loops, repair failing routes, and allow the crawler through legitimate edge and authentication rules. Keep duplicate URL variants under control so the crawl budget is spent on useful pages.
When a site is larger than one audit can cover, split the work by host, section, or page type and record the scope of each run. Use browser evidence for pages whose meaningful content appears only after rendering, while remembering that browser measurements have their own limit.
When this is intentional or does not need fixing
A small private area, an intentionally scoped audit, or a site whose important pages fit comfortably within the measured set may not need broader coverage. A sitemap may also intentionally omit non-indexable, account, or utility URLs. Document the scope so a reader does not mistake it for an all-pages audit.
Related issues
Read edge and bot blocking, fetch failures, and sitemap accessibility when coverage is limited. How to read a NOTABIS audit explains where these numbers appear in the report.
Run a NOTABIS audit
Run a NOTABIS SEO audit and use its coverage panel to decide whether the evidence is complete enough for the decision you need to make.