Skip to main content
v1.1.0 · Published 2026-04-05 · Updated 2026-06-03

AVR Framework

AI Visibility Readiness, a transparent, tiered audit methodology for measuring whether your site is readable, recommendable, and citeable by traditional and AI-powered search systems. Every check ships with an evidence label.

Retrieval header

For AI extraction
What this is
AI Visibility Readiness audit framework, plus the chudi.dev architecture pattern it scores.
Primary entity
AVR Framework
Secondary entities
chudi.dev (case study), citability.dev (audit tool), AI-Visible Web Architecture (upstream pattern)
Question answered
How do you measure whether a website is readable, recommendable, and citeable by AI search?
Updated
2026-04-18
Evidence type
Methodology with first-party case study (chudi.dev)
Related
citability.dev, upstream pattern repo, case-study post

How does AVR label evidence?

AVR does not invent composite scores for things it cannot measure. Every check in the framework is tagged with how much you can trust the result. Verifiable checks are reproducible against a free API or CLI tool. Best-effort checks measure a point-in-time sample whose confidence is labelled explicitly per round.

[VERIFIED]

Objective, reproducible, backed by a free API or CLI tool. Anyone can run the check and get the same result.

[BEST-EFFORT]

Measurable in a point-in-time sample but varies by session, query phrasing, and platform state. Confidence labelled explicitly.

What does AVR v1.1.0 audit?

AVR v1.1.0 runs eight audit sections against a target URL. Sections 1 through 5 cover the traditional SEO foundation, AI infrastructure files, live citation polling, AI visibility testing, and a calibration receipt. Sections 6 through 8 are the v1.1.0 additions for Agent Readiness, Fact-Block Density, and Citation Decay Rate.

§1

SEO Foundation

[VERIFIABLE]

The baseline AI search systems depend on. If organic search cannot find you, AI search never sees you.

  • Core Web Vitals
  • Technical Crawlability
  • Schema Validation
  • E-E-A-T Signals
  • Content Depth
  • Internal Link Graph
§2

AI Infrastructure

[VERIFIABLE]

The AI-specific files that declare your intent to crawlers. llms.txt reclassified to optional/documentation-only per Google I/O 2026; Lighthouse 13.3 flags it as ERROR by default.

  • robots.txt (9 AI agents)
  • ai.txt
  • .well-known/llms.json
  • Organization + Person schema (sameAs depth)
  • Article datePublished freshness
  • Open Graph images
§3

Citation Monitoring

[BEST-EFFORT]

Does AI link to your URL when asked about your topics? 20 queries across ChatGPT, Perplexity, Claude, Gemini. Single rounds are LOW confidence.

  • 5 brand queries
  • 5 topic queries
  • 5 long-tail queries
  • 5 competitor queries
  • Citation rate per platform
  • Trend over rounds
§4

AI Visibility

[BEST-EFFORT]

Does AI know you exist and recommend you? Brand recognition + concept attribution + recommendation signals. With AI Mode at 1B+ monthly users and AI Overviews dropping CTR 58%, this is now the primary arena.

  • Brand recognition (17 queries)
  • Concept attribution
  • Recommendation rate
  • Cross-platform Entity Authority (§2.6 Wikipedia + Wikidata + sameAs)
  • Multimodal Readiness flag (16%+ multimodal queries)
§5

Calibration Receipt

[VERIFIABLE]

Pre-flight smoke test proving the audit tool was working correctly when it produced the numbers. The forensic trail unit that makes the deliverable defensible.

  • Test prompt with known-good citation
  • Per-engine connectivity
  • Sample-size discipline
  • Test-to-live haircut applied
§6

Agent Readiness (NEW in v1.1.0)

[VERIFIABLE]

Does your site expose tools to AI agents? WebMCP manifest + A2A AgentCard + wire-protocol probe. The browser-level standard shipping in Chrome 146 Canary; W3C draft co-authored by Google + Microsoft.

  • /.well-known/webmcp manifest valid
  • /.well-known/agent.json AgentCard valid
  • Tool list completeness
  • Declared endpoint resolves (W3 probe)
  • JSON-RPC 2.0 dispatcher available
§7

Fact-Block Density (NEW in v1.1.0)

[VERIFIABLE]

Is your content shaped for citation? Five weighted checks score 0-100. Patel's first-sentence-of-every-H2 rule + AI SEO Engineering Standards 40-60w direct-answer band. The proximate driver of citation selection.

  • F1: H2 first-sentence standalone-answer (weight 30)
  • F2: First-200-tokens direct-answer (20)
  • F3: 40-60 word direct-answer band per H2 (20)
  • F4: H2/H3 question-format rate (20)
  • F5: FAQ section present (10)
§8

Citation Decay Rate (NEW in v1.1.0)

[VERIFIABLE]

How long do you HOLD a citation? The moat metric no other AI visibility tool tracks. Consumes Bing AI Performance CSV; computes half-life, decay slope, displacement events, retention rate.

  • Citation Decay Rate per window
  • Citation half-life (sustained 4-week below-50%)
  • Decay slope (linear regression)
  • Displacement event count (1.5σ drops)
  • Citation Retention Rate (latest 30d / earliest 30d)

How does AVR decide the verdict tier?

The framework collapses the eight section verdicts into one of three tiers. No fake composite score, just the honest read on where the site lives today. AI-READY requires foundation plus AI infrastructure plus measurable citations. Foundation-ready means infrastructure mostly in place with gaps. Not-ready means foundation itself fails and AI work is premature.

AI-READY

Sections 1+2+6+7 PASS + measurable citations (>0% per round) within last 30 days + EXTRACTABLE Fact-Block + GROWING/STABLE Citation Decay

FOUNDATION-READY

Sections 1+2 PASS + Sections 6+7 PARTIAL. Infrastructure in place; gaps in agent-readiness or content extractability.

NOT-READY

Section 1 FAIL OR Section 2 FAIL. AI infrastructure is upstream; foundation must come first.

What does an AVR run look like?

chudi.dev runs its own AVR v1.1.0 audit in public, because transparency is the differentiator. The site lands AI-READY overall, with AGENT-READY 3 of 3 on Section 6 and a verified 100 of 100 EXTRACTABLE on Section 7 Fact-Block Density. The numbers below are this page's own most recent AVR run.

chudi.dev: AVR v1.1.0
Section 1: SEO Foundation 6/6
Section 2: AI Infrastructure 6/6
Section 3: Citations 30.0%
Section 4: Visibility 64.9%
Section 6: Agent Readiness AGENT-READY 3/3
Section 7: Fact-Block Density 100/100
Section 8: Citation Decay GROWING
> Verdict AI-READY

Why does AVR exist?

After spending 106 hours and $10K on AEO infrastructure that produced zero AI citations, the lesson was clear. The infrastructure was correct. The SEO foundation underneath it did not exist. AVR exists so the next site builder runs the checks in the right order and skips the same mistake.

The framework enforces the right order: foundation first, then AI readiness, then live AI testing. Running visibility tests before the foundation is in place is premature.

What changed in AVR v1.1.0?

Material changes to AVR are versioned, editorial fixes and link updates are not. The v1.1.0 release adds three new audit sections (Agent Readiness, Fact-Block Density, Citation Decay Rate) and reclassifies llms.txt from required to optional per Google I/O 2026 guidance. The earlier v1.0 to v1.1.0 jump on 2026-04-18 added Section 4 separately.

  1. v1.1.0 2026-05-22

    Sections 6 (Agent Readiness, WebMCP + A2A AgentCard), 7 (Fact-Block Density, content extractability scoring), and 8 (Citation Decay Rate, the moat metric) added. llms.txt reclassified to optional/documentation-only per Google I/O 2026.

  2. v1.1.0 (early) 2026-04-18

    Section 4 (AI Visibility) added. Concept attribution and recommendation rate now scored separately from raw citation count. Reflects the gap between "AI knows the brand" and "AI cites the URL."

  3. v1.0.0 2026-04-05

    Initial release. Three sections (SEO Foundation, AI Infrastructure, Citation Monitoring) plus three-band verdict.

Frequently asked questions

The five questions every prospect asks about AVR v1.1.0 before running it on their site.

How do I run an AVR audit on my own site?
Clone github.com/ChudiNnorukam/avr-pipeline, install scripts/requirements.txt, and run python3 scripts/run_audit.py YOUR_URL --skip-lighthouse --full-v11. Free audit covers Sections 1, 2, 6, 7, 8 at zero API cost. Add --live-test with brand and topics for the paid Sections 3, 4, 5 (about two dollars in API spend per audit).
What does AGENT-READY 3 of 3 actually mean?
Section 6 checks three things on a site. First, /.well-known/webmcp exists and validates as JSON with at least one tool declared. Second, /.well-known/agent.json exists with required AgentCard fields. Third, each endpoint the manifests declare resolves to a non-404 response. Three of three means all pass. chudi.dev and citability.dev both reach this verdict.
Why is Section 7 Fact-Block Density different from other content scoring tools?
Other tools score readability or keyword density. Section 7 scores extractability for AI engines. Five weighted checks measure whether each H2 opens with a standalone-answer sentence, whether the first 200 tokens directly answer the page query, whether H2 paragraphs land in the 40 to 60 word band, whether headings are question-shaped, and whether an FAQ section exists. Output is 0 to 100 with three verdict bands.
How is Citation Decay Rate computed?
Section 8 ingests the Bing AI Performance Report CSV exported from Microsoft Webmaster Tools. It computes citation half-life (days from peak to sustained four-week below-50%), decay slope (linear regression of citations per day), displacement events (week-over-week drops greater than 1.5 standard deviations), and citation retention rate (latest 30 days divided by earliest 30 days). All metrics are tested in a 12-case pytest regression suite.
Where can I see a real AVR audit deliverable?
chudi.dev exposes its own audit at /api/webmcp/avr-self-audit?format=full as live JSON. A walkthrough of the same audit is at /blog/avr-v1-1-0-case-study-audit. The reproducible source files for both runs live in the avr-pipeline GitHub repo under sample-audits.

How do I run AVR on my site?

The tool powering citability.dev runs AVR v1.1.0 against any URL. The free scan covers eight v1.1.0 sections at zero API cost. The full audit adds live AI engine polling across OpenAI, Perplexity, Claude, Gemini, plus a calibration receipt for the audit, costing about two dollars per run.