Four sections covering technical access, AI visibility, content, and reputation.
This is more than a crawl audit. We measure where your buyers go to find you, what AI says when they ask, and what's missing from your story.
RankBee scored 5 BetBrain pages against the live SERP for each page's buyer queries. BetBrain wins on tennis and casino bonus content, finishes a close 3rd on Premier League, and ranks mid-pack on the homepage.
10 odds-comparison buyer prompts run live across all 5 engines (ChatGPT, Gemini, Perplexity, Claude, Google AI Overviews) via Bright Data SERP API + direct Anthropic API. BetBrain appears in 4 of 50 cells; Oddschecker, OddsPortal and Oddspedia together dominate citation share.
robots.txt is permissive — every AI/search bot is Allowed. But at the CDN/WAF, 8 of 15 bots time out (every OpenAI bot, every Perplexity bot, both Googlebots, Bing Copilot). Only ClaudeBot, Bingbot and the Claude search/user agents complete a fetch.
Across the 4 buyer-intent clusters BetBrain is overwhelmingly ABSENT — not negatively framed, just missing. When AI does surface the brand (homepage-anchored only), the tone is neutral-positive: 'long-standing odds comparison platform', 'real-time betting odds'. Recommendations almost always go to OddsChecker, OddsPortal or Oddspedia.
Content scorecard — page vs page vs live competitor URLs
RankBee scored each BetBrain page against every URL that ranks for its target queries. Tennis and casino-bonus win outright; Premier League finishes a close 3rd; homepage drops to mid-pack; the about page wouldn't even fetch through our scoring pipeline (a tell in itself).
Content quality leaderboard
iRankings — citations per engine, per prompt
10 buyer-intent prompts (vendor evaluation, match-level, bonus-hunting, trust/methodology) run live across 5 AI engines (ChatGPT, Gemini, Perplexity, Claude, Google AI Overviews). BetBrain appears in 4 of 50 cells. The top three brands by citation coverage — Oddschecker,...
AI Coverage Leaderboard
iCrawlability — what AI bots can actually fetch
BetBrain's robots.txt is welcoming, but the edge is hostile. 53% of the AI/search bots that drive answer-engine citations time out at the CDN — even though they're explicitly allowed. Result: AI indexes BetBrain through stale prior knowledge and third-party data brokers...
Sentiment — what AI says about BetBrain to buyers
Across 50 cells (10 prompts × 5 engines) BetBrain is cited in 4 cells. Where the brand does surface, the tone is neutral-to-positive — capability-focused rather than critical. The dominant pattern is absence, not negative framing.
Sentiment leaderboard
Frequently asked
What is a GAIO Audit Report?
GAIO stands for Generative AI Optimization — getting your brand cited inside AI answers, not just ranked on a results page. The Deficit Report is RankBee's diagnostic: across leading AI engines (ChatGPT, Gemini, Perplexity, Claude, and Google AI Overviews) and a tailored prompt set, it shows which answers your brand is missing from, which competitors take the citation in your place, and the technical and content reasons why.
Who is this for?
Anyone whose audience now turns to ChatGPT, Gemini, Perplexity or Claude before making a decision. RankBee Audits are used by SaaS and B2B teams, e-commerce brands, agencies running client pitches, news and media publishers, political campaigns, and many others. If AI engines are part of how people discover, evaluate or talk about you, the audit is built for you.
How is this different from a traditional SEO audit?
A site can hold position 1 on Google and be completely absent from ChatGPT, Gemini and Perplexity answers for the same query — because the two systems use entirely different signals to decide what to surface. A traditional audit grades you on Google's signals — backlinks, keywords, Core Web Vitals. RankBee grades you on what large language models actually reason about: entities, attributes, answer-first structure, citation-worthiness, and crawlability through the bot stack AI assistants use today (GPTBot, ClaudeBot, PerplexityBot, Google-Extended and 20 more). Strong Google rankings don't automatically translate into AI citations, and that gap is what the audit measures.
How does the audit work?
Four sections, each grounded in real data. Crawlability runs five technical phases: robots.txt rules, virtual-user probes from your target geographies, live LLM web-search fetches, bot-impersonation against your CDN, and token-depth indexability. Rankings Matrix runs your buyer prompts against up to 5 AI engines and logs every citation, co-citation, and competitor mention. Content Scorecard simulates AI ranking at the page level — RankBee ingests competitor content, generates variations, and scores yours 1–10 on the attributes models actually reward. Sentiment Snapshot reads how engines describe you when they do mention you, clustered by audience intent. The Rankings Matrix also shows every buyer question your brand is missing from — and which competitor takes the citation in your place, across each of the five AI engines tested.
Where do the prompts come from?
RankBee discovers them for you. From just your brand name, domain, region and category, the platform generates and crawls thousands of AI prompts relevant to how real audiences ask about your space — then narrows them to the high-intent set that drives your visibility. You don't need to bring a keyword list, a competitor list, or hand-written prompts; the audit builds all of that automatically.
What does "invisible to AI" actually mean?
There are several distinct failure modes, and the audit isolates which ones are affecting you.
- Uncrawlable. Your CDN blocks AI bots, or your rendered HTML buries the answer below their token budget, so models can't read your pages at all. This is the most common silent failure: robots.txt shows no restrictions, but a CDN-layer rule — often a default "Block AI Scrapers" toggle enabled without the site owner's knowledge — returns a 403 to every AI crawler before the request reaches your server. The audit runs bot-impersonation probes that replicate the exact request signature of GPTBot, ClaudeBot, and PerplexityBot against your live CDN to catch this.
- Crawlable but uncited. Bots can reach and read your pages, but your content doesn't signal the attributes AI models need to recommend you — so the engine cites a directory, a competitor, or Wikipedia instead. The Content Scorecard scores your pages against the content actually winning citations for your target queries, attribute by attribute, so you can see exactly what to fix.
- Cited but mis-framed. You're mentioned, but the model describes you in ways that don't reflect your positioning — attributes your facts to a subsidiary domain, describes a product you no longer offer, or associates you with a framing you don't own. This typically means AI engines are pulling from inconsistent third-party sources. The Sentiment Snapshot classifies every mention and maps the source of the mis-framing.
- Locked out of live retrieval. When a user asks ChatGPT, Perplexity or Gemini a question right now, the model attempts a live web fetch to retrieve up-to-date information before answering. Many sites pass robots.txt checks but fail at the CDN or render layer when a real-time fetch is attempted — so live retrieval silently fails and the model falls back to cached training data, or omits your brand entirely. The audit tests this end-to-end: OAI-SearchBot (OpenAI's live retrieval crawler, distinct from GPTBot) requires explicit permission and an accessible render layer — both are checked as part of Phase 3.
- Excluded from training data. Your robots.txt and bot policies determine whether AI training crawlers — GPTBot, ClaudeBot, Google-Extended, CCBot — are allowed to ingest your content for model training and refinement. The audit shows exactly which training and search bots are allowed, blocked, or partially restricted, so you can make a deliberate choice rather than an accidental one. For reference: Cloudflare's managed robots.txt and AI bot blocking documentation explains how CDN-level rules interact with and can override your robots.txt directives.
How long does it take, and what do I need to provide?
Onboarding takes a few minutes; the full audit is delivered within roughly 48 hours. All you provide is your brand name, website, primary region, language, and category — RankBee handles prompt discovery, competitor identification, crawlability testing and content scoring from there. Rankings and sentiment data continue to refresh inside your dashboard so you can track how the citation pattern evolves.
What happens after the report — does it fix the issues?
The audit diagnoses; remediation happens in the rest of the platform. Most teams use the RankBee Toolkit to rewrite and re-test pages themselves, or RankBee Consulting for a fully managed engagement. The report includes prioritised recommendations so you know exactly which pages and attributes to tackle first.
Can I share the report with my team and stakeholders?
Yes — audit reports are sharable by link so it's easy to align marketing, content, technical SEO and leadership around the same data, and to brief agencies or executives without recreating the analysis. Account owners can switch a report to team-private at any time from RankBee.
How do I get a full audit?
BetBrain's pages already win the scoring comparison. The next 90 days are about *being seen* — at the edge, in third-party content, and in AI answer surfaces.
Three moves change the picture: (1) Open the WAF for OpenAI, Perplexity and Googlebot user-agents — robots.txt is already permissive, the edge is the breaking layer. (2) Rebuild /about-betbrain as an entity-anchor page (ownership disclosure, founding date 2000, methodology, named editorial team) to capture the high-intent 'is X trustworthy / independent' prompt class where BetBrain is currently 0/10. (3) Earn co-citation in the 6 third-party roundups AI keeps quoting (Similarweb competitor pages, Punter2Pro, Mike Cruickshank, OLBG, BettingSites.co.uk, Reddit r/algobetting) — those six sources together dominate the 'best odds comparison site' and 'Oddschecker alternatives' SERPs.