storybook.js.org

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

Built with Next.js

Needs work

This is how AI agents (not browsers) experience storybook.js.org. 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

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

failCanonical URLDiscoverability

No <link rel="canonical"> tag in <head>. Agents use canonical URLs to dedupe and cite.

Fix · Next.js: Set alternates.canonical in the Metadata API (generateMetadata) for each route.

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 · Next.js: Emit JSON-LD from a Server Component or the Metadata API: a <script type="application/ld+json"> with Organization / Article / Product for the page.

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 0.4% of HTML weight (5840/1497506 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%.

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.

failMCP server cardemergingDiscoverability

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

Fix: Publish an MCP Server Card describing the tools your site exposes. Agents discover capabilities via `/.well-known/mcp/server-card.json`. See modelcontextprotocol.io for the schema.

Don’t lose this report

Get it in your inbox now — and a heads-up whenever storybook.js.org’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 JSON-LD structured data

Paste inside <head>. Use Article/Product instead of Organization on those page types.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Storybook: Frontend workshop for UI development",
  "url": "https://storybook.js.org/",
  "description": "Storybook is a frontend workshop for building UI components and pages in isolation. Thousands of teams use it for UI development, testing, and documentation. It&#x27;s open source and free."
}
</script>

What the agent receives

The agent’s-eye view

Storybook: Frontend workshop for UI development Docs AI Addons Showcase Blog Visual Test Enterprise 90,610 Search docs Get Started Introducing MCP for React Build, test &amp; document components Storybook is a frontend workshop for building UI components and pages in isolation. Thousands of teams use it for UI development, testing, and documentation. It&#x27;s open source and free. Get Started npm create storybook@latest v 10 Latest version 80.23m Installs per month 2282 Contributors Version Development Development Interaction testing Visual testing Documentation localhost:6006 Find components Introduction Application ProductCard Documentation Default Expanded Added to cart Dashboard Homepage User Profile Sign In Design System ActivityList Form Avatar Button Footer Header Pagination Controls Interactions Addons Name Controls description * Introducing the Space Helmet X24: a sleek, durable motorcycle helmet with advanced ventilation, anti-fog visor, and stylish graphics. Experience ultimate protection and comfort for your rides. productTitle * Space Helmet X24 backgroundColor #D8DDDD outOfStock False True padding 0 40 selectedColor White Space Grey Yellow Develop durable user interfaces Storybook provides a workshop to build UIs in isolation. It helps you develop hard-to-reach states and edge cases without needing to run the whole app. Made for + 7 Build UI components and pages in isolation Implement components and pages without needing to fuss with data, APIs, or business logic. Why build UIs in isolation? Mock hard-to-reach edge cases as stories Render components in key states that are tricky to reproduce in an app. Then save those states as stories to revisit during development, testing, and QA. How to write a story Integrate with the tools you already use Storybook is incrementally adoptable and integrates with industry-standard tools. That means your team doesn&#x27;t have to change their workflow. Browse integrations 400+ Integrations 35M Downloads per week “Storybook is a powerful frontend workshop environment tool that allows teams to design, build, and organize UI components (and even full screens!) without getting tripped up over business logic and plumbing.” Brad Frost Author of Atomic Design Test UIs with less effort and no flake Stories capture the “known good” states of UI components. They&#x27;re a pragmatic, reproducible way to keep track of UI edge cases. Storybook uses them to power automated tests. Learn about UI tests Spot test Stories are tests you can debug in dev and QA. Learn about UI tests Visual test appearance Pinpoint UI changes down to the pixel. Interaction test behavior Simulate user behavior and assert in the browser. Accessibility tests Check stories for WCAG and ARIA issues. Coverage Reports Track how much of your frontend code is tested. Snapshot test markup Detect regressions in DOM markup. “The tool we use for editing UI is Storybook. It is the perfect place to make sure your work aligns with designs to the pixel across breakpoints.” Adam Neary Tech lead Document UI for your team to reuse Storybook brings together UI, examples, and documentation in one place. That helps your team and AI agents adopt existing UI patterns. Learn about search Find any component or page in your app Storybook is a single source of truth for UI. Learn about search Generate UI docs automatically Write Markdown and build custom docs. Reuse components across pages and apps Every story is a use case that you can reuse. Track component history and versions QA unexpected bugs by going back in time. “Storybook has made developing components more streamlined by allowing us to easily include technical documentation within our design system!” Taurie Davis Author of Building Design Systems Share how the UI actually works Stories show how UIs actually work not just a static design of how they&#x27;re supposed to work. That keeps everyone aligned on what&#x27;s currently in production. Publish Storybook to get sign off from teammates Publish Storybook as a website for stakeholders to reference. Your team can check that the UI looks right without touching code. Publishing also hosts your MCP server, giving your entire organization access to validated patterns for their coding agents. Publish Storybook Embed stories in wikis, Markdown, and Figma Embed stories to showcase your work to teammates and the developer community. Works with the oEmbed standard. Embed stories + and more “Storybook is my go-to when starting a new design system. It makes getting something in place quick and easy for both design and engineering.” Sarrah Vesselov Author of Building Design Systems Automate UI workflows Add Storybook as a CI step to automate the UI development workflow. That helps you and your team ship faster with less manual work. Learn how to setup Storybook in CI Made for frontend developers The top frontend engineering teams rely on Storybook to ship world-changing products. Join our open source community to learn new techniques and get support. Get involved Monday.com Microsoft D2IQ Drei Shopify kickstartDS Grommet JSTOR Polaris Psammead UI React Fluent UI Web Compnents Gutenberg Explorer 1 React Spectrum Join 2282 contributors building the future of UI development. Star on Github 2282 Contributors Chat with 19,344+ frontend developers. Join Discord server 19,344+ Server members Watch tutorials, feature previews, and interviews. Watch on YouTube 8,320+ Subscribers Get the latest news and updates from Storybook maintainers. Follow on BlueSky And X 24,200+ Followers Join the community Subscribe 7,044 developers and counting Why Why Storybook Component driven UI AI Docs Guides Tutorials Changelog Telemetry Community Addons Get involved Blog Showcase Explore About Open source software Maintained by Special thanks to Netlify .

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

Track this score

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

Full breakdown

14 pass0 warn13 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

pass

llms.txt present

Found /llms.txt (8719 bytes), H1 + at least one link present.

100/100

pass

Sitemap present

sitemap.xml reachable and referenced from robots.txt.

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

fail

Canonical URL

No <link rel="canonical"> tag in <head>. Agents use canonical URLs to dedupe and cite.

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

fail

Text-to-markup ratio

Visible text is 0.4% of HTML weight (5840/1497506 bytes). Low. Markup may be crowding out agent-usable text.

3/100

skip

Content without JavaScript

Browser pass unavailable; cannot measure JS dependency.

—

pass

Heading hierarchy

Hierarchy is well-formed (1 H1, no skipped levels, 12 headings total).

100/100

pass

Cookie wall blocks content

No common consent-modal markers detected.

100/100

pass

Page title

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

100/100

pass

Meta description

A well-sized meta description is present (184 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 ("Frontend workshop for UI component development") with price/CTA ("Get Started").

100/100

pass

Reachability

HTTP 200.

100/100

Performance

pass

Time to first byte

TTFB 209ms. Healthy.

80/100

skip

Full render time

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

—

pass

Page weight

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