vitest.dev

scanned 7/26/2026, 12:41:09 AM · cached · refresh in 21h · rubric 2026.07.4

Built with Webflow

At risk

This is how AI agents (not browsers) experience vitest.dev. The score weights five categories of machine-readability; the ticks on the arc are the 30 individual checks behind it.

✉ Email me this report + alert me when it changes ↓

Top fixes

failSitemap presentDiscoverability

No reachable sitemap.xml. Publish one and reference it in robots.txt.

Fix · Webflow: Publish /sitemap.xml and reference it from robots.txt with a Sitemap: line.

failJSON-LD presentStructured data

No JSON-LD blocks found. Add a <script type="application/ld+json"> with a schema.org type for this page.

Fix · Webflow: Add JSON-LD in Page Settings → Custom Code (inside <head>) for the page’s type.

warnllms.txt presentDiscoverability

Found /llms.txt but missing markdown links.

Fix · Webflow: Publish /llms.txt at your domain root. Build a spec-compliant one at /tools/llms-txt-generator.

failLink response headersDiscoverability

No HTTP Link: response headers. Emit canonical/alternate/describedby relations so HEAD-only or stream-rendering agents get them without parsing HTML.

Fix: Emit `Link:` headers for canonical, alternate-language, and describedby relations. Agents that fetch HEAD-only or stream-render rely on these.

failText-to-markup ratioReadability

Visible text is 3.0% of HTML weight (1832/61441 bytes). Low. Markup may be crowding out agent-usable text.

Fix: Heavy ad or navigation markup crowds out agent-usable text. Aim for a text-to-DOM ratio above 15%.

warnContent without JavaScriptReadability

Browser pass unavailable; HTML looks like a JS-shell (e.g. #__next / #root). Likely JS-dependent.

Fix · Webflow: Webflow exports static HTML. Bind CMS content in the Designer rather than injecting it through custom-code embeds, which agents won’t run.

Don’t lose this report

Get it in your inbox now — and a heads-up whenever vitest.dev’s agent-readiness score changes. Free, unsubscribe anytime.

Fix it

Generated, ready-to-ship files for the gaps above — copy them or download and drop them into your repo.

Add an llms.txt

Publish this at https://vitest.dev/llms.txt

# Vitest | Next Generation testing framework

> Next generation testing framework powered by Vite

## Key pages
- [Home](https://vitest.dev/)
- [Next Generation Testing Framework](https://vitest.dev/)
- [Fast. Lightweight. Integrated.](https://vitest.dev/)
- [Start testing with Vitest](https://vitest.dev/)

## About
Describe what vitest.dev does, who it's for, and the primary action you want an
agent to be able to complete. Keep it factual and current.

What the agent receives

The agent’s-eye view

Vitest | Next Generation testing framework Main Navigation Guides API Config Blog v4.1.10 v4.1.10 Releases Notes Contributing Team unreleased v3.x v2.x v1.x v0.x Search ⌘ Ctrl K English 简体中文 English 简体中文 Are you an LLM? View /llms.txt for optimized Markdown documentation, or /llms-full.txt for full documentation bundle By Next Generation Testing Framework A Vite-native testing framework. It&#39;s fast! Get Started View on GitHub Why Vitest The Vite Native Test Runner Learn more Vitest was created to make testing just work for Vite apps. By building on top of Vite, Vitest natively understands your Vite config and is able to reuse the same resolve and transform pipelines. You can also use Vitest even if you are not using Vite. It is Jest-compatible and works for backend code too. Learn more Fast. Lightweight. Integrated. Vite Powered Reuse Vite &#39;s config and plugins - consistent across your app and tests. But it&#39;s not required to use Vitest! Jest Compatible Expect, snapshot, coverage, and more - migrating from Jest is straightforward. Smart &amp; instant watch mode Only rerun the related changes, just like HMR for tests! ESM, TypeScript, JSX Out-of-box ESM, TypeScript and JSX support powered by Oxc . See full features list Free &amp; open source Vitest is free and open source, made possible by wonderful sponsors. Become a Sponsor Special Vercel Chromatic Zammad Platinum Sponsors Bolt Latitude Gold vital Mailmeteor Liminity Kraken Tech Aerius Ventilation Start testing with Vitest Supercharge your tests with unparalleled performance made for the modern web Get started Vitest Guides API Config Resources Team Blog Releases Versions Unreleased Docs Vitest v3 Docs Vitest v2 Docs Vitest v1 Docs Vitest v0 Docs Social GitHub Discord Bluesky © 2026 VoidZero Inc. and Vitest contributors.

Show your score

Embed this badge on your site. It links back to this live scan and updates on every rescan.

<a href="https://agentspeed.com/scan/vitest.dev"><img src="https://agentspeed.com/badge/vitest.dev" alt="AgentSpeed agent-readiness score" height="56"></a>

Track this score

Get this report by email, then a heads-up when vitest.dev’s agent-readiness actually changes — a check regressing, or the composite dropping.

Two things never trigger an email: a score change caused by us publishing a new rubric, because that is a different instrument rather than a change to your site, and movement explained only by timing-derived checks, which shift run to run on a site nobody touched.

Want it on your own schedule, with Slack or a webhook instead of email? Score-drift monitoring is on every paid plan.

This score says whether an AI agent could read vitest.dev. AI traffic analytics says whether one actually came — and which pages turned it away.

Full breakdown

7 pass2 warn13 fail8 skip

Show only failures

Discoverability

pass

robots.txt present

A robots.txt is reachable at the site root.

100/100

pass

robots.txt allows AI agents

All 8 answer-time access agents allowed.

100/100

fail

Content-Signal directivesemerging

No Content-Signal directives. Add e.g. `Content-Signal: ai-train=no, ai-summarize=yes` to declare granular AI usage policy beyond binary allow/disallow.

0/100

warn

llms.txt present

Found /llms.txt but missing markdown links.

60/100

fail

Sitemap present

No reachable sitemap.xml. Publish one and reference it in robots.txt.

0/100

fail

Link response headers

No HTTP Link: response headers. Emit canonical/alternate/describedby relations so HEAD-only or stream-rendering agents get them without parsing HTML.

0/100

skip

Canonical URL

Check could not run.

—

fail

MCP server cardemerging

No valid MCP Server Card at /.well-known/mcp/server-card.json. Publish one so agents can discover your tools without HTML scraping.

0/100

fail

OAuth authorization metadataemerging

No RFC 8414 metadata at /.well-known/oauth-authorization-server. Agents that act on behalf of users need this to discover your authorization endpoints.

0/100

fail

OAuth resource metadataemerging

No RFC 9728 metadata at /.well-known/oauth-protected-resource. Publish it so agents can discover required scopes without hand-coded credentials.

0/100

fail

API catalog / OpenAPIemerging

No /.well-known/api-catalog (RFC 9727) and no /openapi.json|yaml. Publish one so agents that integrate with APIs can discover your endpoints.

0/100

fail

Web Bot Authemerging

No Web Bot Auth JWKS at /.well-known/http-message-signatures-directory.json. Publish one to allow trusted agents while keeping a default-deny posture for the rest.

0/100

Readability

fail

Markdown negotiationemerging

Accept: text/markdown returns HTML, not markdown. Serve a markdown variant of primary content when requested; agents summarize and cite it more reliably.

0/100

fail

Text-to-markup ratio

Visible text is 3.0% of HTML weight (1832/61441 bytes). Low. Markup may be crowding out agent-usable text.

22/100

warn

Content without JavaScript

Browser pass unavailable; HTML looks like a JS-shell (e.g. #__next / #root). Likely JS-dependent.

50/100

skip

Heading hierarchy

Check could not run.

—

skip

Cookie wall blocks content

Check could not run.

—

skip

Page title

Check could not run.

—

skip

Meta description

Check could not run.

—

Structured data

fail

JSON-LD present

No JSON-LD blocks found. Add a <script type="application/ld+json"> with a schema.org type for this page.

0/100

skip

Structured data validates

No JSON-LD blocks present; nothing to validate (covered by structured_data.jsonld_present).

—

pass

Schema type coverage

Page intent unclear; no specific schema.org type expected.

100/100

Actionability

skip

Paywall / login wall

Check could not run.

—

fail

Agent Skills manifestemerging

No Agent Skills manifest at /.well-known/agent-skills.json. Enumerate the tasks agents can perform (search, add-to-cart, contact-support) so they pick the right one without scraping.

0/100

fail

WebMCP actionsemerging

No WebMCP detected. On pages with first-class actions (cart, support, account), embed a WebMCP server so on-page agents invoke tools directly.

0/100

pass

Primary action reachable

Primary offering identified ("Next generation testing framework") with price/CTA ("Get Started").

100/100

pass

Reachability

HTTP 200.

100/100

Performance

pass

Time to first byte

TTFB 41ms. Healthy.

100/100

skip

Full render time

Full-render time unavailable (browser pass skipped or failed).

—

pass

Page weight

Initial document is a lean 60 KB.

100/100

Beyond the scan

Running AI agents of your own? AgentSpeed also monitors them in production — every run, its latency, cost, and failures, with alerts when something breaks. Free for 10,000 events a month, no credit card.

Start watching free →See plans