agentspeed.

rust-lang.org

scanned 7/25/2026, 8:40:28 PM · cached · refresh in 20h · rubric 2026.07.4
Built with Webflow
robots.txt present: failrobots.txt allows AI agents: passContent-Signal directives: failllms.txt present: warnSitemap present: failLink response headers: failCanonical URL: failMCP server card: failOAuth authorization metadata: failOAuth resource metadata: failAPI catalog / OpenAPI: failWeb Bot Auth: failMarkdown negotiation: failText-to-markup ratio: passContent without JavaScript: skipHeading hierarchy: passCookie wall blocks content: passPage title: passMeta description: passJSON-LD present: failStructured data validates: skipSchema type coverage: passPaywall / login wall: passAgent Skills manifest: failWebMCP actions: failPrimary action reachable: passReachability: passTime to first byte: passFull render time: skipPage weight: pass64/ 100 · D
Needs work

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

Discoverability
20
Readability
88
Structured data
33
Actionability
75
Performance
100

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

failCanonical URLDiscoverability

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

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

failrobots.txt presentDiscoverability

No reachable robots.txt at the site root. Publish one so agents can discover your crawl policy and sitemap.

Fix: Add a `/robots.txt` file at the site root. Even an allow-all file signals intent to agents.

warnllms.txt presentDiscoverability

Found /llms.txt but missing H1 header and 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.

Don’t lose this report

Get it in your inbox now — and a heads-up whenever rust-lang.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 an llms.txt
Publish this at https://rust-lang.org/llms.txt
# Rust Programming Language

> A language empowering everyone to build reliable and efficient software.

## Key pages
- [Home](https://rust-lang.org/)
- [Rust](https://rust-lang.org/)
- [A language empowering everyone to build reliable and efficient software.](https://rust-lang.org/)
- [Why Rust?](https://rust-lang.org/)
- [Build it in Rust](https://rust-lang.org/)
- [Rust in production](https://rust-lang.org/)
- [Get involved](https://rust-lang.org/)

## About
Describe what rust-lang.org 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
Rust Programming Language Install Learn Playground Tools Governance Funding Community Blog Language English (en-US) Español (es) Français (fr) Italiano (it) 日本語 (ja) Português (pt-BR) Русский (ru) Türkçe (tr) 简体中文 (zh-CN) 正體中文 (zh-TW) Rust A language empowering everyone to build reliable and efficient software. Get Started Version 1.97.1 Why Rust? Performance Rust is blazingly fast and memory-efficient: with no runtime or garbage collector, it can power performance-critical services, run on embedded devices, and easily integrate with other languages. Reliability Rust’s rich type system and ownership model guarantee memory-safety and thread-safety &mdash; enabling you to eliminate many classes of bugs at compile-time. Productivity Rust has great documentation, a friendly compiler with useful error messages, and top-notch tooling &mdash; an integrated package manager and build tool, smart multi-editor support with auto-completion and type inspections, an auto-formatter, and more. Build it in Rust In 2018, the Rust community decided to improve the programming experience for a few distinct domains (see the 2018 roadmap ). For these, you can find many high-quality crates and some awesome guides on how to get started. Command Line Whip up a CLI tool quickly with Rust’s robust ecosystem. Rust helps you maintain your app with confidence and distribute it with ease. Building Tools WebAssembly Use Rust to supercharge your JavaScript, one module at a time. Publish to npm, bundle with webpack, and you’re off to the races. Writing Web Apps Networking Predictable performance. Tiny resource footprint. Rock-solid reliability. Rust is great for network services. Working On Servers Embedded Targeting low-resource devices? Need low-level control without giving up high-level conveniences? Rust has you covered. Starting With Embedded Rust in production Hundreds of companies around the world are using Rust in production today for fast, low-resource, cross-platform solutions. From startups to large corporations, from embedded devices to scalable web services, Rust is a great fit. Get involved Read Rust We love documentation! Take a look at the books available online, as well as key blog posts and user guides. Read the book Watch Rust The Rust community has a dedicated YouTube channel collecting a huge range of presentations and tutorials. Watch the Videos Contribute code Rust is truly a community effort, and we welcome contribution from hobbyists and production users, from newcomers and seasoned professionals. Come help us make the Rust experience even better! Read Contribution Guide Thanks Rust would not exist without the generous contributions of time, work, and resources from individuals and companies. We are very grateful for the support! Individuals Rust is a community project and is very thankful for the many community contributions it receives. See individual contributors Corporate sponsors The Rust project receives support from companies through the Rust Foundation. See Foundation members Get help! Documentation Rust Forge (Contributor Documentation) Ask a Question on the Users Forum Language English (en-US) Español (es) Français (fr) Italiano (it) 日本語 (ja) Português (pt-BR) Русский (ru) Türkçe (tr) 简体中文 (zh-CN) 正體中文 (zh-TW) Terms and policies Code of Conduct Licenses Logo Policy and Media Guide Security Disclosures Privacy Notice All Policies Social Maintained by the Rust Team. See a bug? File an issue! Web site built every day at 22:00 UTC

Show your score

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

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

Track this score

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

Full breakdown

12 pass1 warn14 fail3 skip
Discoverability
fail
robots.txt present
No reachable robots.txt at the site root. Publish one so agents can discover your crawl policy and sitemap.
0/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
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
pass
Text-to-markup ratio
Visible text is 19.2% of HTML weight (3564/18594 bytes). Healthy.
88/100
skip
Content without JavaScript
Browser pass unavailable; cannot measure JS dependency.
—
pass
Heading hierarchy
Hierarchy is well-formed (1 H1, no skipped levels, 22 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 (25 chars).
100/100
pass
Meta description
A well-sized meta description is present (72 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 ("Rust programming language") with price/CTA ("Get Started").
100/100
pass
Reachability
HTTP 200.
100/100
Performance
pass
Time to first byte
TTFB 58ms. Healthy.
100/100
skip
Full render time
Full-render time unavailable (browser pass skipped or failed).
—
pass
Page weight
Initial document is a lean 18 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