figma.com
This is how AI agents (not browsers) experience figma.com. The score weights five categories of machine-readability; the ticks on the arc are the 31 individual checks behind it.
Top fixes
1 access agent(s) blocked: Claude-SearchBot — these keep your site out of AI answers. 6 training-data crawler(s) blocked (GPTBot, anthropic-ai, Google-Extended, CCBot, cohere-ai, FacebookBot) — a licensing choice, not scored.
Fix · Next.js: Allow GPTBot, ClaudeBot, and PerplexityBot in robots.txt (or remove the blanket Disallow).
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.
Visible text is 0.3% of HTML weight (3989/1579761 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%.
Browser pass unavailable; HTML looks like a JS-shell (e.g. #__next / #root). Likely JS-dependent.
Fix · Next.js: Render primary content on the server: use Server Components (App Router) or getServerSideProps/SSG (Pages Router). Avoid fetching above-the-fold content in a client useEffect, since agents don’t run it.
Page looks like Article|BlogPosting|NewsArticle; missing JSON-LD type(s): Article|BlogPosting|NewsArticle.
Fix: Align JSON-LD type to page purpose. Product pages without Product markup are skipped by agent shopping flows.
<html lang="en"> is valid, but 20 hreflang alternate(s) are malformed ("es-es", "es-ar", "es-bo"). Malformed alternates are ignored by consumers, so those translations are invisible to agents routing users by market.
Fix: Add `lang` to your `<html>` element (`<html lang="en">`, `<html lang="de-DE">`). If you publish translations, declare them with `<link rel="alternate" hreflang="..." href="...">` using BCP 47 tags — language[-Script][-REGION], hyphens not underscores.
Get it in your inbox now — and a heads-up whenever figma.com’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.
This scan shows whether an agent can read the site. One free probe asks a real assistant a real buying question and records who it cited.
This graded your homepage. Your pricing, docs, and checkout live on other pages — the ones assistants actually quote when they recommend you — and a 69/100 here means agents are already missing things on the page you polish most. The $29 Deep Scan audits the whole site against all 31 checks, then emails a PDF with every failing check and its exact fix, ranked by what costs you the most visibility. One-time, delivered in minutes, no subscription.
What the agent receives
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/figma.com"><img src="https://agentspeed.com/badge/figma.com" alt="AgentSpeed agent-readiness score" height="56"></a>Track this score
Get this report by email, then a heads-up when figma.com’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 figma.com. AI traffic analytics says whether one actually came — and which pages turned it away.
Full breakdown
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.