▸ reading the site the way an agent does
▸ fetching html …
▸ reading robots.txt …
▸ checking llms.txt …
▸ probing structured data …
▸ estimating agent-visible content …
▸ converting → clean markdown …
▸ scoring
www.sparkcapital.comD
NEEDS WORK
agent-readiness
#Agent-Readiness Report — https://www.sparkcapital.com
>Score 48/100 (D). Generated by machineview from the site's public surface. robots.txt is the site's declared policy, not observed traffic.
-URL: https://www.sparkcapital.com/
-Title: Spark Capital
-Generated: 2026-08-19T22:14:57.527Z
##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: unspecified
-OAI-SearchBot: unspecified
-ChatGPT-User: unspecified
-ClaudeBot: unspecified
-anthropic-ai: unspecified
-Claude-SearchBot: unspecified
-Claude-User: unspecified
-Claude-Web: unspecified
-Google-Extended: unspecified
-Google-CloudVertexBot: unspecified
-GoogleOther: unspecified
-PerplexityBot: unspecified
-Perplexity-User: unspecified
-CCBot: unspecified
-Applebot-Extended: unspecified
-Applebot: unspecified
-Amazonbot: unspecified
-Meta-ExternalAgent: unspecified
-Meta-ExternalFetcher: unspecified
-FacebookBot: unspecified
-Bytespider: unspecified
-cohere-ai: unspecified
-MistralAI-User: unspecified
-DuckAssistBot: unspecified
-YouBot: unspecified
-Diffbot: unspecified
-Timpibot: unspecified
-Omgilibot: unspecified
-PetalBot: unspecified
-Unknown / other: unspecified
###✓ content delivery
Content is server-rendered: 30KB of HTML carries 1.1k tokens of clean text.
363 words remain once chrome, scripts and boilerplate are stripped away.
###✕ structure
Structure gaps: 5 h1s, skipped heading levels, sparse alt text.
Engines split pages on the heading tree and separate content from chrome. These gaps make the page harder to quote.
###▲ semantic clarity
3 of 5 identity signals present.
Missing or thin: JSON-LD, canonical. These are what tell agents who you are and how to cite you.
###✕ navigability
Agents can traverse from here: 4 internal links.
Publish a sitemap.xml and link your key pages so agents can find more than this one page.
##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 — 13/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 — 14/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 — 12.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 — 6.5/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 — 2/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
-Add JSON-LD structured data (Organization, Product, Article…) so agents can extract entities and facts reliably. Pages with valid structured data are 2.3× likelier to surface in AI answers.
-This page has 5 h1 tags. Use exactly one so the heading tree has a clear root.
-Fix skipped heading levels (e.g. h2 → h4) so the outline is well-formed.
-Publish a sitemap.xml and reference it in robots.txt, so agents can discover every page instead of just the ones they stumble onto.
-Add descriptive alt text to your images. Agents cannot see pixels; the alt text is all they get.
-Give links descriptive text instead of “click here” or bare URLs. Anchor text is how agents decide where a link goes.
-Set <link rel="canonical"> so crawlers do not split you across duplicate URLs.
-Add more internal links with descriptive text. Agents traverse the link graph to reach the rest of your site.
-Publish an llms.txt, a curated markdown map of your key pages for agents (llmstxt.org). machineview can generate one for you.
machineview commands
Search commands or paste a URL