Figma

← board · figma.com · #36 of 80

Ready with a few material gaps

82/ 100
B
Grade
61
Agent readiness
Board average 77
Scanned 14 hours ago

Every outstanding fix in one prompt for your coding agent. Rescan →

Task

What does figma.com do and how do I use it? A fetch-only agent finds out.

12 fetches7 found5 missing

home
  • /robots.txt/sitemap.xml
  • /llms.txt/llms-full.txt
  • /pricing
  • /docs
  • /openapi.json
  • mcp.jsonMCP initialize
  • /privacy · /terms
404 probe

every path the scanner fetched · replayed deterministically, no LLM

Evaluator notes

A fetch-only agent reached figma.com over HTTPS in 1006 ms and identified it from its title as “Figma: The collaborative canvas for design, code, and AI”. The copy is readable without JavaScript (1,387,557 chars of visible text, 82.7% of HTML). It found pricing and docs. It looked for an OpenAPI spec and an MCP server and found none.

Critical access needs attention

Whether an ordinary agent can enter, read, and operate the public site.

  • ~
    Agents can reach the site

    Crawler access and bot defenses.

    3 / 4 passed
  • Core content is available

    Useful content remains accessible without a fragile browser-only path.

    2 / 2 passed
  • Navigation fails safely

    Redirects and missing pages give agents a recoverable path.

    2 / 2 passed
  • Controls are understandable

    Forms and interactive controls expose usable names and structure.

    2 / 2 passed

Fix these gaps first

Critical access gaps come first, then the biggest remaining points.

  1. 01
    OpenAPI spec discoverableAgent-ready

    Publish your OpenAPI spec at /.well-known/openapi.json so agents can call you without reading docs.

    +7 pts
  2. 02
    Meta description 50–160 charactersMetadata

    Add a meta description between 50 and 160 characters.

    +5 pts
  3. 03
    Machine-readable pricingAgent-ready

    Publish prices as text on /pricing (not in images) and add an Offer to your JSON-LD.

    +3 pts
  4. 04
    Agent manifest (MCP, A2A or ai-plugin)Agent-ready

    Publish an MCP server manifest or A2A agent card under /.well-known/ so agents can find your tools.

    +2 pts
  5. 05
    llms.txt says what you are and links outAgent-ready

    Start llms.txt with an H1 and one-paragraph summary, then link docs, pricing and API.

    +2 pts

Audit the checks behind the score

Grouped by what they measure. Not-applicable checks are excluded from scoring.

Crawlable5 of 5 passed · 19/19 pts
  • Served over HTTPS5/5

    https://www.figma.com/

  • Responds in under 1.5s5/5

    1006 ms to first byte

  • robots.txt present2/2

    User-Agent: Fasterfox Disallow: / User-Agent: Nutch Disallow: / User-Agent: spoc…

  • sitemap.xml present2/2

    /sitemap.xml → 200

  • Homepage is indexable5/5

    HTTP 200

Metadata6 of 7 passed · 19/24 pts
  • Title tag 10–70 characters5/5

    "Figma: The collaborative canvas for design, code, and AI" (56)

  • Meta description 50–160 characters0/5

    "Figma is the canvas where design, code, and AI come together. From first idea to shipped product — g…" (164)

    Add a meta description between 50 and 160 characters.

  • Canonical URL set3/3

    https://www.figma.com/

  • Exactly one H14/4

    1 × <h1>: "The intelligent canvas for infinite creativity"

  • Mobile viewport set3/3

    width=device-width, initial-scale=1

  • Language declared2/2

    <html lang="en">

  • Favicon declared2/2

    https://static.figma.com/app/icon/2/icon-128.png

Shareable3 of 3 passed · 14/14 pts
  • Open Graph title, description and image8/8

    title, description, image

  • Twitter/X card type set3/3

    twitter:card = summary_large_image

  • Links to X or LinkedIn3/3

    1 social link(s)

Converts3 of 3 passed · 17/17 pts
  • Clear call to action8/8

    5 CTA(s), e.g. "Get started"

  • Pricing page linked6/6

    → https://www.figma.com/pricing/

  • HTML under 2 MB3/3

    1639 KB of HTML

Measured1 of 1 passed · 6/6 pts
  • Analytics installed6/6

    detected: mixpanel

Agent-ready10 of 19 passed · 28/46 pts
  • Structured data (JSON-LD)4/4

    @type: Organization

  • Machine-readable pricing0/3

    /pricing exists but no price found in its HTML

    Publish prices as text on /pricing (not in images) and add an Offer to your JSON-LD.

  • llms.txt present0/1

    no /llms.txt

    Publish /llms.txt: a short markdown summary of the product, pricing and docs links for AI agents.

  • llms-full.txt present0/1

    no /llms-full.txt

    Publish /llms-full.txt with the full docs inlined, so agents can read everything in one fetch.

  • AI crawlers allowed in robots.txt1/2

    blocked: GPTBot, ClaudeBot, Google-Extended, CCBot

    Remove Disallow: / rules for GPTBot, ClaudeBot, PerplexityBot and friends, or agents cannot read you.

  • No noai / TDM reservation2/2

    no opt-out signals

  • Serves markdown on request0/1

    Accept: text/markdown → text/html; charset=utf-8

    Return text/markdown when the Accept header asks for it; agents skip the HTML entirely.

  • OpenAPI spec discoverable0/7

    no /openapi.json or /.well-known/openapi.json

    Publish your OpenAPI spec at /.well-known/openapi.json so agents can call you without reading docs.

  • Agent manifest (MCP, A2A or ai-plugin)0/2

    no manifest at /.well-known/{mcp,agent,ai-plugin}.json

    Publish an MCP server manifest or A2A agent card under /.well-known/ so agents can find your tools.

  • Docs or API link from the homepage3/3

    homepage links to docs / API

  • Content readable without JavaScript3/3

    1,387,557 chars of visible text, 82.7% of HTML

  • Semantic landmarks (main, single H1)3/3

    <main> present, 1 × <h1>

  • Images have alt text2/2

    90/90 images have alt

  • Form fields are labelledn/a
  • Descriptive link text2/2

    0/141 links say "click here" / "learn more"

  • Agent-friendly 404s2/2

    nonexistent path → HTTP 404

  • Trust pages (privacy, terms, security)2/2

    found: /privacy, /security

  • Organization schema complete2/2

    Organization has name, url, logo, sameAs

    Give the Organization JSON-LD a name, url, logo, description and sameAs links.

  • llms.txt says what you are and links out0/2

    no /llms.txt

    Start llms.txt with an H1 and one-paragraph summary, then link docs, pricing and API.

  • Contact route discoverable2/2

    mailto:, /contact or /support link found

APIn/a
  • Spec parses and declares a versionn/a
  • Operations have summaries and operationIdsn/a
  • Error responses documentedn/a
  • Auth scheme declaredn/a
  • Versioned paths or serversn/a
  • Spec within a model context budgetn/a
MCPn/a
  • Server answers initializen/a
  • Tools listedn/a
  • Tools carry descriptionsn/a
  • Tool parameters have schemasn/a

Fixed something? Scan again.

One scan per site every 10 minutes. Snapshot 2026-08-24T13:49:06.985Z.

← Back to the board