AVR v1.1.0 Full 13-Section Audit: Cloudflare Radar Data Meets AI Visibility

What does a 13-section AI visibility audit actually look like?

AVR v1.1.0 expanded from 8 sections to 13 by adding 5 checks grounded in Cloudflare Radar data from May 2026. These are not theoretical checks. Each one measures your site against an empirical baseline drawn from traffic patterns across Cloudflare’s network. I ran the complete audit against chudi.dev to see what a real site looks like against these baselines.

What are the 5 new Cloudflare-derived checks?

Cloudflare Radar publishes weekly AI bot traffic data. The May 17-23, 2026 window shows that AI crawlers now represent a significant share of all bot traffic (Googlebot 26.2%, GPTBot 10.5%, ClaudeBot 9.3%), and that 8.7% of AI bot requests get blocked with 403 Forbidden. The 5 new AVR checks test whether your site falls in that blocked percentage or not.

Bot Response Code (§2.8) sends GET requests with ClaudeBot, GPTBot, Bingbot, and PerplexityBot user-agent strings and checks whether each gets a 200 OK or a 403/429 block. chudi.dev result: ACCESS-OPEN, 4/4 bots get 200.

Markdown Negotiation (§2.9) tests whether your server responds to Accept: text/markdown with actual markdown content. Cloudflare data shows only 5.3% of top sites support this, and the payload reduction is 93% (down to 7% of HTML size). chudi.dev result: MARKDOWN-READY. The server returns a curated markdown summary with recent posts, topics, and author info.

AI Rules in robots.txt (§2.10) parses your robots.txt for AI-specific user-agent directives. 79% of top domains have them, but many are incomplete (blocking GPTBot but not ClaudeBot, or vice versa). chudi.dev result: AI-RULES-COMPLETE, 3/3 checks pass. All major AI crawlers have explicit directives.

Agent Readiness Tier (§2.11) scores your site 0-4 across four agent infrastructure standards: robots.txt AI rules, XML sitemap, WebMCP manifest, and A2A AgentCard. WebMCP has 0% adoption among the top 200K domains scanned. chudi.dev result: AGENT-TIER-HIGH, 4/4. All four standards are implemented.

Crawl Signal (§2.12) tests response time under a ClaudeBot user-agent (under 3 seconds threshold), confirms robots.txt does not fully block major AI crawlers, and checks for aggressive rate limiting. chudi.dev result: CRAWL-ACCESSIBLE, 3/3 checks pass.

What did the full 13-section audit show?

Here is the complete chudi.dev audit from May 24, 2026 (infrastructure + live AI engine testing):

Section	Verdict	Score
§1 SEO Foundation	PASS	Lighthouse SEO 100, Perf 72, A11y 95, BP 100
§2 AI Infrastructure	PASS	All infrastructure checks green
§2.7 Agent Readiness (WebMCP)	AGENT-READY	3/3
§3 Citations	PARTIALLY_CITED	27.9% citation rate across 4 engines
§4 AI Visibility	HIGHLY_VISIBLE	Brand 95%, Topic 40.6%, Recommend 56.2%
§3 Fact-Block Density	EXTRACTABLE	100/100
§7 Citation Decay Rate	GROWING	HIGH confidence
§2.8 Bot Response Code	ACCESS-OPEN	4/4
§2.9 Markdown Negotiation	MARKDOWN-READY	1/2
§2.10 AI Rules in robots.txt	AI-RULES-COMPLETE	3/3
§2.11 Agent Readiness Tier	AGENT-TIER-HIGH	4/4
§2.12 Crawl Signal	CRAWL-ACCESSIBLE	3/3

Overall: AI-READY. The Cloudflare-derived checks (§2.8-§2.12) all pass. SEO Foundation passes with a perfect Lighthouse SEO score of 100/100. The site is ahead of the market on every agent standard that Cloudflare measures.

Live AI engine results

The live test queried ChatGPT, Claude, Perplexity, and Gemini with 20 brand-awareness queries and 32 topic/recommendation queries.

Brand Recognition: 95% (19/20). Nearly every AI engine correctly identifies Chudi Nnorukam and chudi.dev when asked directly. This is the strongest signal in the audit.

Active Recommendation: 56.2% (18/32). More than half of recommendation queries (“what tools should I use for X”) return chudi.dev or citability.dev. For a sub-DR-20 personal brand, this is unusually high and reflects the entity engineering work done over the past 3 months.

Topic Association: 40.6% (13/32). AI engines associate the brand with its topics (AI visibility, structured data, answer engine optimization) about 40% of the time. This is the biggest growth area. More topical cluster content and cross-platform publication should lift this score.

Citation Rate: 27.9%. About 1 in 4 queries that should cite the site actually include a link. This is the PARTIALLY_CITED verdict. The gap between brand recognition (95%) and citation (27.9%) is the core product thesis behind citability.dev: being known is not enough, you need to be citable.

Lighthouse breakdown

Category	Score
SEO	100/100
Accessibility	95/100
Best Practices	100/100
Performance	72/100

Performance at 72 reflects the SSR root page (switched from prerender for markdown negotiation). Vercel edge caching keeps TTFB low on repeat visits.

Fact-Block Density is 100/100 EXTRACTABLE. The root page passed all five checks (standalone answer, first-200-tokens, 40-60 word band, question-format headings, FAQ section) after the prior remediation arc converted H2s to questions and added FAQ sections.

Why does the Citation Decay Rate matter?

Citation Decay Rate is a first-to-market metric in AVR v1.1.0. No Semrush, BrightEdge, or Conductor product tracks it. The metric measures whether your citations are holding, growing, or decaying over time. chudi.dev shows GROWING with HIGH confidence, meaning AI engines are citing the site more frequently over time, not less.

This aligns with Cloudflare’s crawl-to-refer data: ClaudeBot’s ratio is 10,600:1 but declining 16.9%, meaning Claude is sending more referral traffic per crawl. The product thesis behind citability.dev is that making your content more citable leads to more AI-driven referrals. The Citation Decay Rate metric proves whether that is actually happening for a given site.

What does the citability.dev free scan show now?

The free scan at citability.dev now runs 15 checks (up from 10). The 5 new Cloudflare-backed checks are:

1. AI Bot Access - are ClaudeBot and GPTBot blocked?
2. Markdown Negotiation - does your server support Accept: text/markdown?
3. AI Rules in robots.txt - do you have AI-specific directives?
4. Agent Readiness Tier - robots.txt + sitemap + WebMCP + AgentCard (0-4 score)
5. Crawl Responsiveness - is your site fast enough for AI crawlers?

Every check runs against Cloudflare Radar baselines. When the scan says “8.7% of AI bot requests get 403 globally,” that is an empirical number from Cloudflare’s network, not a made-up benchmark.

What is next for AVR v1.1.0?

How does chudi.dev compare to enterprise SEO platforms?

I ran the same 15-check citability.dev free scan against three enterprise SEO platforms to see how they score on the same checks.

Check	chudi.dev	conductor.com	semrush.com	brightedge.com
robots.txt	PASS	PASS	PASS	PASS
sitemap.xml	PASS	PASS	PASS	PASS
Answer-First Content	PASS	PASS	PASS	FAIL
Content Freshness	PASS	PASS	FAIL	FAIL
Structured Data (JSON-LD)	PASS	PASS	PASS	FAIL
Meta Description	PASS	PASS	PASS	PASS
Canonical URL	PASS	PASS	PASS	PASS
HTTPS	PASS	PASS	PASS	PASS
Heading Hierarchy	PASS	PASS	PASS	PASS
Social Sharing	PASS	PASS	PASS	FAIL
AI Bot Access	PASS	PASS	PASS	PASS
Markdown Negotiation	PASS	FAIL	FAIL	FAIL
AI Rules in robots.txt	PASS	FAIL	FAIL	FAIL
Agent Readiness Tier	PASS	PASS	PASS	PASS
Crawl Responsiveness	PASS	PASS	PASS	PASS
Total	15/15	13/15	12/15	9/15

chudi.dev is the only site that passes all 15 checks. The two checks that every competitor fails are Markdown Negotiation and AI Rules in robots.txt. These are the frontier signals that the traditional SEO industry has not adopted yet. Cloudflare Radar confirms: markdown negotiation has 5.3% adoption, and while 79% of top sites have AI rules in robots.txt, these enterprise SEO platforms do not.

BrightEdge, the platform that coined “content performance marketing,” fails on answer-first content, content freshness, JSON-LD structured data, and Open Graph tags. The irony is instructive: the tools that audit other sites’ SEO are not optimized for AI visibility themselves.

What is next for AVR v1.1.0?

The framework now has 13 audit sections, a CI pipeline that enforces both Lighthouse scores and Fact-Block Density on every deploy, and live citation + visibility baselines from ChatGPT, Claude, Perplexity, and Gemini. The remaining work is expanding markdown negotiation to individual blog post routes and building Citation Decay Rate into citability.dev’s paid reporting tiers.

The audit scripts, the Cloudflare empirics glossary, and all 7 codex nodes are open source at github.com/ChudiNnorukam/ai-visibility-readiness.