Quick answer
The no-pages finding means NOTABIS completed its crawl attempt without measuring any crawlable HTML page and the audit was not classified as edge-blocked. This is a critical coverage failure for that run, not proof that the site has no pages. Check the submitted URL, redirects, status codes, authentication, robots policy, and network access first.
What the issue means
An audit needs at least one HTML response to inspect titles, links, content, and other signals. “No pages” can happen when the origin is down, the URL redirects to an inaccessible host, every response is an error or non-HTML resource, a login or bot challenge blocks the crawler, or a site policy prevents the queue from being populated.
Why it matters for SEO
Search engines also need access to public HTML before they can understand and index it. A failed audit does not change the site or prove that a search engine sees the same response. It does mean that this run provides no page-level evidence, so any score or remediation decision based on it would be premature.
How NOTABIS detects it
After processing the submitted URL, discovered links, and eligible sitemap URLs, NOTABIS checks whether the audit has created any measured pages. If the count is zero and edge_blocked is false, it creates the no-pages issue at audit scope and marks the audit as failed with limited confidence. The rule does not distinguish the underlying cause; the diagnostics and request evidence do that work.
How to check it yourself
Request the submitted URL from an external network and record the final status, content type, redirects, and body. Check DNS, TLS, CDN/WAF logs, authentication, rate limits, robots.txt, sitemap declarations, and whether the response is HTML. Try the exact public hostname rather than an internal alias, and compare a browser request with a plain GET.
How to fix it
Make the intended entry page publicly reachable to the permitted audit user agent, return a successful HTML response, and remove accidental redirect loops, login gates, or bot challenges. Correct DNS and certificate errors, then verify that robots and sitemap rules allow the pages you want measured. If the site is intentionally private, run the audit against an authorized public environment or treat the result as expected coverage failure.
Re-run the audit after the change and confirm that at least one real page, not a generic error or challenge body, appears in the crawl.
When this is intentional or does not need fixing
An internal staging site, maintenance window, or deliberately protected application may correctly produce no public pages. An edge-blocked audit has a different state and should be investigated through its own evidence. Do not make private pages public merely to make an audit complete.
Related issues
Compare edge and bot blocking and fetch failures with HTTP error responses and robots.txt availability.
Run a NOTABIS audit
NOTABIS reports when a run produced no crawlable HTML and records the coverage state needed to identify whether the cause is access, routing, or response content.