bvp.com · agent-readiness

#Agent-Readiness Report — https://www.bvp.com

>Score 88/100 (B). Generated by machineview from the site's public surface. robots.txt is the site's declared policy, not observed traffic.

-URL: https://www.bvp.com/

-Title: Home

-Generated: 2026-08-19T22:14:04.565Z

##Findings

###✓ crawl access (POLICY)

All AI crawlers are allowed, with no index or snippet restrictions.

The stance below comes from robots.txt. It's the site's declared policy, not traffic we observed.

-GPTBot: allow

-OAI-SearchBot: allow

-ChatGPT-User: allow

-ClaudeBot: allow

-anthropic-ai: allow

-Claude-SearchBot: allow

-Claude-User: allow

-Claude-Web: allow

-Google-Extended: allow

-Google-CloudVertexBot: allow

-GoogleOther: allow

-PerplexityBot: allow

-Perplexity-User: allow

-CCBot: allow

-Applebot-Extended: allow

-Applebot: allow

-Amazonbot: allow

-Meta-ExternalAgent: allow

-Meta-ExternalFetcher: allow

-FacebookBot: allow

-Bytespider: allow

-cohere-ai: allow

-MistralAI-User: allow

-DuckAssistBot: allow

-YouBot: allow

-Diffbot: allow

-Timpibot: allow

-Omgilibot: allow

-PetalBot: allow

-Unknown / other: unspecified

###✓ content delivery

Content is server-rendered: 92KB of HTML carries 5.5k tokens of clean text.

1,612 words remain once chrome, scripts and boilerplate are stripped away.

###✓ structure

Clean structure: one h1, 18 headings, semantic landmarks.

A parser can segment and quote this without guesswork.

###✓ semantic clarity

Machine identity is complete (webpage, imageobject, breadcrumblist).

Agents can name you, cite you, and attribute your content correctly.

###✓ navigability

Agents can traverse from here: sitemap (11 URLs), 92 internal links.

A sitemap and a dense internal-link graph let agents reach the rest of the site.

##Scoring — the rulebook

Five MECE pillars modelling a JS-blind crawler: reach, receive content, parse structure, understand, traverse. Graduated so table-stakes lands mid-band and 90+ needs genuine optimization. Blocking a citation crawler / noindex, or JS-injected content, caps the report at 40.

###Crawl access — 14.5/15

-*Measures:* Whether your robots.txt and page directives let AI crawlers fetch, index, and quote the page.

-*Why:* Block the bots that answer questions, or tag the page noindex, and nothing else you do matters. Most sites clear this, so it works as a gate rather than a place to earn points.

-*Scoring:* Full marks: every answer-engine and agent crawler allowed, no noindex or nosnippet in robots.txt, the robots meta tag, or the X-Robots-Tag header, on a clean single-hop HTTPS fetch. Blocking a citation crawler or a noindex caps the whole report at 40.

-*Evidence:* Opting out of OAI-SearchBot removes you from ChatGPT search results (OpenAI docs).

###Content delivery — 28/30

-*Measures:* How much of the real content sits in the raw HTML, before any JavaScript runs.

-*Why:* AI crawlers read the HTML and stop; they don't run JavaScript. Anything injected after load is invisible to them. It's also the hardest pillar to fake, because the only way to pass is to actually server-render.

-*Scoring:* Scores the text-to-markup yield and how early the content appears, paired against script weight so an empty shell cannot fake it. A JS-injected mount point caps this near zero; a heavy bundle is fine as long as the text is really in the HTML.

-*Evidence:* ~69% of AI-crawler requests execute no JavaScript (Vercel, 2024–26).

###Structural legibility — 20.5/25

-*Measures:* Whether the content is structured so a parser can cleanly segment and quote it.

-*Why:* Answer engines strip nav and footer, chunk on heading boundaries, and lift tables almost verbatim. Div-soup with no heading tree flattens into unusable text even when every word is present.

-*Scoring:* Graded on heading hierarchy, semantic landmarks, real tables and lists, descriptive link text, and image alt coverage. Presence earns a floor; a clean, chunkable structure earns the rest.

-*Evidence:* 44% of ChatGPT citations come from the first 30% of a page, and ~85% of page content is never used (Zyppy, ~1.2M answers).

###Semantic clarity — 15/18

-*Measures:* Whether structured data and metadata state who you are and agree with the visible content.

-*Why:* Engines read JSON-LD facts before prose and use them for the brand and dates shown with a citation. It only helps when it's specific and matches the page. Contradictions cost points.

-*Scoring:* Rewards specific, field-complete JSON-LD, a right-sized title and description, OpenGraph, and a self-referential canonical. Generic or thin schema earns little; schema that contradicts the visible content is docked.

-*Evidence:* Valid structured data makes a page 2.3× likelier to appear in AI Overviews (Semrush, 2025).

###Navigability — 9.5/12

-*Measures:* Whether an agent can move past this page to discover the rest of your site.

-*Why:* Reading one page isn't using a site. Agents follow the sitemap and internal links to finish a task. This pillar carries the least weight because most of it is cheap to add, and the much-hyped llms.txt is still ignored by answer engines.

-*Scoring:* Rewards a real sitemap.xml, a dense graph of unique internal links, breadcrumbs, and a genuinely curated llms.txt. Declared files are capped so they cannot buy the score.

-*Evidence:* 97% of llms.txt files received zero AI requests in 2026 (Ahrefs).

##Recommendations

-Publish an llms.txt, a curated markdown map of your key pages for agents (llmstxt.org). machineview can generate one for you.

machineview commands

How agents see www.bvp.com