Sometimes a site blocks direct crawling. When that happens, the report runs in limited-data mode — and says so, rather than pretending.
When it happens
- The site sits behind a firewall/bot-wall (Cloudflare challenge, a login wall).
- It's a JavaScript-only app whose content doesn't render for a simple fetch.
- The page times out or returns an error.
What we do instead of faking it
When our own fetch is blocked, we fall back to signals Google fetched (PageSpeed data often gets through where a direct crawl doesn't), and we produce a speed-led audit from what we can measure — rather than inventing SEO or content scores we couldn't actually check.
How you'll know
The report shows a limited-data banner. Any dimension we couldn't measure is marked as such instead of getting a made-up near-zero score. This matters: a WAF-blocked site is not the same as a genuinely broken one, and the report won't confuse the two.
What to do
If you own the site, the fullest audit comes from a publicly reachable page. If you're auditing a prospect, a limited-data report is still useful — the speed findings alone are usually enough to open a conversation.
Related: reading your report.
Audit a prospect. See what your email could say.
Drop in any prospect's URL. In about two minutes you'll see the report they'd receive and the angle your email would open with. No card, no signup.
Free · no card · bulk CSV campaigns inside the app