playwright.dev

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

Needs work

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

Discoverability

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

Top fixes

Checks tagged “emerging” are 2026 agent-protocol standards most of the web hasn’t adopted yet — adopting early is an edge, not a defect.

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: Add a <script type="application/ld+json"> describing the page (Organization, Article, Product, FAQPage).

warnllms.txt presentDiscoverability

Found /llms.txt but missing H1 header and markdown links.

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

warnSitemap presentDiscoverability

sitemap.xml reachable but not referenced from robots.txt, so agents may miss it.

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

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.

warnHeading hierarchyReadability

Heading issues: 4 skipped level(s).

Fix: Use a single H1 and avoid skipping heading levels (H1 → H3).

failContent-Signal directivesemergingDiscoverability

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.

Fix: Add `Content-Signal:` directives to your robots.txt. This is the emerging standard (Cloudflare-driven) for declaring fine-grained AI usage policy beyond a binary allow/disallow.

Don’t lose this report

Get it in your inbox now — and a heads-up whenever playwright.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://playwright.dev/llms.txt

# Fast and reliable end-to-end testing for modern web apps | Playwright

> What playwright.dev offers, in one or two sentences an AI agent can quote.

## Key pages
- [Home](https://playwright.dev/)
- [Playwright enables reliable web automation for testing, scripting, and AI agents.](https://playwright.dev/)
- [Built for testing](https://playwright.dev/)
- [Built for AI agents](https://playwright.dev/)
- [Powerful tooling](https://playwright.dev/)
- [Chosen by companies and open source projects](https://playwright.dev/)

## About
Describe what playwright.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

Fast and reliable end-to-end testing for modern web apps | Playwright Skip to main content Playwright Docs MCP CLI API Node.js Node.js Python Java .NET Search Playwright enables reliable web automation for testing, scripting, and AI agents. One API to drive Chromium, Firefox, and WebKit — in your tests, your scripts, and your agent workflows. Available for TypeScript , Python , .NET , and Java . Get started Star 93k+ Playwright Test Full-featured test runner with auto-waiting, assertions, tracing, and parallelism across Chromium, Firefox, and WebKit. npm init playwright@latest Testing documentation Playwright CLI Token-efficient browser automation for coding agents like Claude Code and GitHub Copilot. Skill-based workflows without large context overhead. npm i -g @playwright/cli@latest CLI documentation Playwright MCP Model Context Protocol server that gives AI agents full browser control through structured accessibility snapshots. npx @playwright/mcp@latest MCP documentation Built for testing Auto-wait and web-first assertions Playwright waits for elements to be actionable before performing actions. Assertions automatically retry until conditions are met. No artificial timeouts, no flaky tests. Test isolation Each test gets a fresh browser context — equivalent to a brand new browser profile. Full isolation with near-zero overhead. Save authentication state once and reuse it across tests. Resilient locators Find elements with selectors that mirror how users see the page: getByRole , getByLabel , getByPlaceholder , getByTestId . No brittle CSS paths. Parallelism and sharding Tests run in parallel by default across all configured browsers. Shard across multiple machines for faster CI. Full cross-browser coverage on every commit. Built for AI agents Accessibility snapshots, not screenshots Agents interact with pages through structured accessibility trees — element roles, names, and refs. Deterministic and unambiguous, no vision models required. MCP server Drop-in Model Context Protocol server for VS Code, Cursor, Claude Desktop, Windsurf, and any MCP client. Full browser control through standard tool calls. CLI for coding agents Token-efficient command-line interface with installable skills. Purpose-built for Claude Code, GitHub Copilot, and similar coding agents that need to balance browser automation with large codebases. Session monitoring Visual dashboard with live screencast previews of all running browser sessions. Click any session to zoom in and take control. Powerful tooling Test generator Record your actions in the browser and Playwright writes the test code. Generate assertions from the recording toolbar. Pick locators by clicking on elements. Trace Viewer Full timeline of test execution with DOM snapshots, network requests, console logs, and screenshots at every step. Investigate failures without re-running. VS Code extension Run, debug, and generate tests directly in the editor. Set breakpoints, live-inspect locators in the browser, and view full execution traces in the sidebar. Any browser. Any platform. Chromium, Firefox, and WebKit on Linux, macOS, and Windows. Headless and headed. Also available for Python , .NET , and Java . Chosen by companies and open source projects Learn Getting started Playwright Training Learn Videos Feature Videos Community Stack Overflow Discord X LinkedIn More GitHub YouTube Blog Ambassadors Microsoft Privacy Statement Copyright © 2026 Microsoft

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/playwright.dev"><img src="https://agentspeed.com/badge/playwright.dev" alt="AgentSpeed agent-readiness score" height="56"></a>

Track this score

Get this report by email, then a heads-up when playwright.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 playwright.dev. AI traffic analytics says whether one actually came — and which pages turned it away.

Full breakdown

13 pass3 warn11 fail3 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 H1 header and markdown links.

60/100

warn

Sitemap present

sitemap.xml reachable but not referenced from robots.txt, so agents may miss it.

70/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

pass

Canonical URL

Canonical points to self: https://playwright.dev/.

100/100

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

pass

Text-to-markup ratio

Visible text is 16.7% of HTML weight (3455/20699 bytes). Healthy.

83/100

skip

Content without JavaScript

Browser pass unavailable; cannot measure JS dependency.

—

warn

Heading hierarchy

Heading issues: 4 skipped level(s).

75/100

pass

Cookie wall blocks content

No common consent-modal markers detected.

100/100

pass

Page title

A concise <title> is present (69 chars).

100/100

pass

Meta description

A well-sized meta description is present (59 chars).

100/100

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

pass

Paywall / login wall

No paywall or login-wall detected on the landing URL.

100/100

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 ("end-to-end testing framework for web apps") with price/CTA ("Get started").

100/100

pass

Reachability

HTTP 200.

100/100

Performance

pass

Time to first byte

TTFB 54ms. Healthy.

100/100

skip

Full render time

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

—

pass

Page weight

Initial document is a lean 20 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