svelte.dev

scanned 7/25/2026, 7:40:51 PM · cached · refresh in 19h · rubric 2026.07.4

Needs work

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

failSitemap presentDiscoverability

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

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

failCanonical URLDiscoverability

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

Fix: Add <link rel="canonical" href="…"> pointing at the primary URL of each page.

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).

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 2.4% of HTML weight (2131/90175 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%.

warnMeta descriptionReadability

Meta description is 34 characters; aim for 50–200 so it's neither thin nor truncated.

Fix: Add `<meta name="description" content="...">` to your primary pages. Agents frequently use it as a summary.

Don’t lose this report

Get it in your inbox now — and a heads-up whenever svelte.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 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": "Svelte • Web development for the rest of us",
  "url": "https://svelte.dev/",
  "description": "Web development for the rest of us"
}
</script>

What the agent receives

The agent’s-eye view

Svelte • Web development for the rest of us Skip to main content Docs Svelte SvelteKit CLI AI Tutorial Packages Playground Blog Svelte web development for the rest of us get started attractively thin, graceful and stylish Svelte is a UI framework that uses a compiler to let you write breathtakingly concise components that do minimal work in the browser, using languages you already know — HTML, CSS and JavaScript. It’s a love letter to web development. But don’t take our word for it. Developers consistently rank Svelte as the framework they’re most excited about using. used by companies you’ve heard of Watch the full Svelte Origins documentary join our friendly community Our sister organisation, Svelte Society , organises events around the globe. Find your chapter and join us in our Discord server . Photos by Marcel Cutts Backed by Vercel and countless donors, developed by full-time and part-time maintainers, Svelte is here to stay. Rich-Harris Conduitry dummdidumm trueadm tanhauhau paoloricciuti benmccann PuruVJ baseballyama gtm-nayan Ocean-OS 7nik elliott-with-the-longest-name-on-github Swatinem jacwright lukeed mrkishi DreaminDani adiguba mindrones pngwn ngtr6788 navorite geoffrich ekhaled ignatiusmb EmilTholin antony dominikg MathiasWP tivac jches zxbodya btk5h PaulBGD halfnelson pushkine GarrettGeorge btakita brunnerh FWeinb TehShrike evs-chris colincasey jamesbirtles bluwy jacobmischka fcrozatier Drips Datawrapper Vercel GitHub Sponsors Cohere Dabble Monogram Frontend Masters Hugging Face Threema Open Source Fund xyflow - React Flow | Svelte Flow Pintura Codesmith Raster Avast Jeff Moe WonderTax Labs INVISR Matt Sanity Metafy Changelog Kohei Yoshino Clancy Digital Kenoxa GmbH Level Up Tutorials The Pudding Jason Hetherington n8n.io - n8n GmbH Zev Averbach Donovan Dikaio Bun Hyunbin multi Evidence Scott Spence David Stevens 0+X Handsontable - JavaScript Data Grid Dong-won Jeffrey Lee Cain Voong Nicky Hajal Dean Papastrat Robert Balfre Sentry Cliff Johnson Emma Agering Tigris Data © 2026 Svelte contributors. Svelte is free and open source software released under the MIT license.

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

Track this score

Get this report by email, then a heads-up when svelte.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.

Full breakdown

11 pass2 warn14 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 (1673 bytes), H1 + at least one link present.

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

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 2.4% of HTML weight (2131/90175 bytes). Low. Markup may be crowding out agent-usable text.

18/100

skip

Content without JavaScript

Browser pass unavailable; cannot measure JS dependency.

—

warn

Heading hierarchy

Heading issues: 2 <h1> tags (expected 1).

75/100

pass

Cookie wall blocks content

No common consent-modal markers detected.

100/100

pass

Page title

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

100/100

warn

Meta description

Meta description is 34 characters; aim for 50–200 so it's neither thin nor truncated.

60/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 ("UI framework") with price/CTA ("get started").

100/100

pass

Reachability

HTTP 200.

100/100

Performance

pass

Time to first byte

TTFB 68ms. Healthy.

100/100

skip

Full render time

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

—

pass

Page weight

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