Site blocked automated access

What this means

Levri attempted to load your page but was blocked before it could access the real content. Rather than pretend to score a page it never actually saw, the run is halted — and the credit is refunded.

This is almost always a configuration at the edge, not a problem with the page itself. A normal browser visit will load fine; an automated request gets a different response, often a 403 challenge page or a redirect to a login.

Why it happens

Edge-protection products are tuned to keep scrapers, credential stuffers, and abusive crawlers out. Helpful bots — search engines, link previewers, analysis tools like Levri — sometimes get caught in the same net.

• Cloudflare or WAF protection
• Bot detection systems
• Login walls or gated content

Fix it

1. 01
   Retry once

   Some blocks are temporary — a single retry often clears a one-off challenge.
2. 02
   Upload screenshot

   Analyse the rendered experience instead. Levri's vision model evaluates the same CRO signals from a full-page PNG.
3. 03
   Whitelist Levri

   If it's your site, allow access. Reach out via chat and we'll point you at the exact rule to add.

If you manage the site

Whitelisting Levri turns the page back into something you can scan on demand. That's useful when you're iterating on copy or layout and want to compare scores between revisions — once allowed through, the page becomes scannable any time without retries or screenshot uploads.

Why this matters

If Levri can't reach your page, neither can a lot of other useful machines — search engine crawlers, link previewers, and the AI agents your future customers will increasingly use to compare options. A page invisible to automation is increasingly invisible to acquisition.