Readiness pre-check

Before Lokrix spends a single credit on an engine call, every scan passes through a readiness gate. It confirms the property is analysable and the run can complete cleanly — catching problems while they are cheap to fix, not after a partially-billed run.

What the gate checks

Readiness pre-check: can AI crawlers reach you?An AI crawler reaches a gate that checks whether robots.txt and the sitemap allow access; the gate branches to a pass state (AI crawlers can reach you) or a fail state (blocked — fix robots or sitemap). A badge notes it costs no credits and needs no property.no credits · no property neededAI crawlerGPTBot, etc.robots +sitemap OK?Reachable — passBlocked — fix it
  • URL reachable — the property URL resolves and returns crawlable content, so brand and feature signals can be extracted.
  • Brand detected — the brand/industry has been identified, which anchors mention and citation detection during scoring.
  • Prompt universe present — the property has a generated set of prompts to run. See The prompt universe.
  • Engines configured — at least one engine is selectable. AI Overviews and AI Mode stay disabled until a SERP provider key is connected.
  • Credits available — the workspace has enough credit balance to cover the planned live runs. Predictive-only scans need no credits.

Pass, warn, block

A green gate lets the scan proceed. A warning (for example, only predictive coverage is possible, or AIO/AI Mode are unavailable) lets the scan run with reduced scope and records the limitation on the result. A blocking failure stops the scan before any billable call and tells you exactly which check failed and how to resolve it.

When a run is credit-blocked, top up on the Credits & metering page, or run a predictive scan instead.