If your audit failed, timed out, or came back with almost nothing in it, one of five things happened. Work through these checks in order.
Check that an anonymous visitor can reach your site
Open your site in a private browser window, signed out. If you see a login screen, a country block, a CAPTCHA, or a "checking your browser" page, our crawler sees the same thing — and there's nothing for it to audit.
Note that this is the single most common cause of an empty report.
Check whether your site renders its content in JavaScript
View source on a page — the real HTML source, not the inspector — and search for a sentence you can see on screen. If it's not in the source, the content is built in the browser after the page loads. The crawler reads the HTML it's served, so a JavaScript-only site reads as thin or empty even though it looks fine to you.
Sites built as single-page applications are the usual case here.
Check whether the run hit the time limit
An audit crawls in legs of about 4 minutes each and checkpoints between them, so a big crawl continues automatically across up to 5 legs, and a background sweep picks up a run whose tab closed. A run that exhausts every resume shows up as a failure with nothing saved.
If that happens, re-run the audit. Note that a manual re-run starts over rather than resuming — only the automatic legs and the background sweep read the checkpoint.
Check whether your site is blocking our crawler
Some hosts and web application firewalls (WAFs) block anything that isn't a mainstream browser. When we get a 403 or a 503, we retry with browser headers, which clears most of these blocks. If your host is stricter, allowlist our crawler — or ask your host to.
Check your robots.txt too — a Disallow: / blocks us, as designed.
Check whether the data provider returned anything
Keyword and competitor data comes from a search data provider. A brand new domain, a very small niche, or an unusual market can genuinely have no data. That's a real answer, not a failure — the report says so instead of inventing numbers.
What looks like a failure but isn't
- A category shows a dash instead of a score. Nothing measurable was found for it on the crawled pages. It's not a zero, and it doesn't count against you.
- Off-page or Backlinks shows as not available. This is expected. Backlink data needs a paid subscription that isn't enabled, so the report marks the discipline as not measured instead of estimating it. Learn more about reading your report →.
- The AI presence tiles show sample data. Some AI-visibility panels are marked as samples because the data source behind them isn't enabled. They're labeled where that's the case.
- The report covers fewer pages than your site has. An audit crawls up to 500 pages (the depth picker's Deep setting is 200) and samples beyond that. The report states how many it read.
If you're still stuck
Email hello@searchblueprint.io, or open Ask anything in the app and press Escalate under the assistant's answer. Include your domain and roughly when you ran the audit. A person on the team gets the whole conversation and replies to your account's email address.
Did my failed audit spend a credit?
No. A credit is held when the run starts and only becomes permanent when it finishes — a failure releases the hold immediately, and if the process dies mid-run the hold expires on its own within 15 minutes.
Can I start a second audit while the first one is still marked as running?
No. A project with an audit in flight refuses a new start — two simultaneous runs would pay for data twice, and the later one would overwrite the first report. Give a stalled run a few minutes to be swept up or marked dead, then re-run.