# Preparación para AI de figma.com

> Medido en la página de inicio. Calificación general: Aceptable.

Puntuación 67/100, nota Aceptable. Medido 2026-09-04T21:31:39.025+00:00, motor ax-audit@4.0.0.

## Comprobaciones

### Contenido — 78/100

#### Content Negotiation — 0/100

- **FAIL** Homepage does not serve Markdown via content negotiation
  Got text/html (HTTP 200) for "Accept: text/markdown"
  Serve a Markdown representation of your pages when agents request "Accept: text/markdown". Agents like Claude Code and Cursor ask for it, and Markdown cuts token usage by roughly 80% against HTML. Cloudflare ("Markdown for Agents") and Vercel can enable this without code changes.
  https://axrush.com/guides/content-negotiation#not-supported
- **WARN** No <link rel="alternate" type="text/markdown"> fallback found on the homepage
  If you cannot enable content negotiation, advertise a Markdown version with <link rel="alternate" type="text/markdown" href="/index.md"> so agents can discover it.
  https://axrush.com/guides/content-negotiation#no-alternate

#### Operabilidad para agentes — 100/100

- **PASS** 155/157 interactive elements have an accessible name
- **PASS** Method note: this reads markup, not a rendered accessibility tree
  Labels attached by script and roles computed at runtime are invisible here, so treat low proportions as a prompt to check the real tree rather than as a count. Every finding is also a plain accessibility defect.

#### Structured Data — 80/100

- **PASS** 1 JSON-LD block(s) found
- **PASS** @context references schema.org
- **WARN** No @graph array (single-entity only)
  Use an @graph array to define multiple entities in one JSON-LD block: { "@context": "https://schema.org", "@graph": [...] }
  https://axrush.com/guides/structured-data#no-graph
- **WARN** Only 1 key type found: Organization
  Consider adding: Person, WebSite, WebPage, ProfilePage
  Add more entity types to your @graph. AI agents use these to understand site structure. Common types: Person, Organization, WebSite, WebPage.
  https://axrush.com/guides/structured-data#few-types
- **WARN** No BreadcrumbList found
  Add a BreadcrumbList entity to help AI agents understand your site navigation hierarchy.
  https://axrush.com/guides/structured-data#no-breadcrumb
- **WARN** No author declared in structured data
  An assistant deciding whether to cite a page weighs where it came from. Add author as a Person or Organization, not a bare string.
  https://axrush.com/guides/structured-data#no-author
- **PASS** 6 sameAs link(s) tie your entity to external identifiers
  https://x.com/figma, https://www.linkedin.com/company/figma, https://www.instagram.com/figma, https://www.facebook.com/figmadesign
- **PASS** Organization carries disambiguating detail (registration, legal address or contact point)
- **WARN** No dateModified or datePublished in structured data
  Assistants weigh recency when they answer time-sensitive questions, and a page with no date cannot be weighed at all. Add dateModified to anything that changes.
  https://axrush.com/guides/structured-data#no-dates

#### HTML Rendering — 85/100

- **PASS** Server-rendered content detected (598 words, 3979 chars of visible text)
- **WARN** Low text-to-markup ratio (0.2%)
  Recommended minimum: 5%
  A very low text-to-markup ratio is a typical SPA-shell symptom. Inline more content directly into the HTML response.
  https://axrush.com/guides/html-rendering#low-ratio
- **PASS** Semantic landmarks present (main, article, section, header, footer, nav)
- **PASS** Single <h1> heading: "The intelligent canvas for infinite creativity"
- **WARN** Heavy JavaScript with no <noscript> fallback
  107 executable <script> tags
  Provide a <noscript> fallback that explains the site or links to a non-JS variant. This helps agents that disable JS.
  https://axrush.com/guides/html-rendering#no-noscript
- **PASS** 92/92 <img> tags have alt attributes

#### SEO Basics — 95/100

- **PASS** <title> length 56 chars: "Figma: The collaborative canvas for design, code, and AI"
- **WARN** Meta description is long (164 chars)
  Trim to 70-160 characters; longer descriptions get truncated.
  https://axrush.com/guides/seo-basics#long-description
- **PASS** Canonical URL: https://www.figma.com/
- **PASS** <html lang="en">
- **PASS** UTF-8 charset declared
- **PASS** Viewport meta present: "width=device-width, initial-scale=1"

### Acceso — 96/100

#### TLS / HTTPS — 100/100

- **PASS** Site is served over HTTPS
- **PASS** HTTP requests redirect to HTTPS
- **PASS** HSTS max-age=31536000
- **PASS** HSTS includes subdomains
- **PASS** HSTS preload-eligible

#### Agent Access — 100/100

- **PASS** All 10 core AI crawler user-agents receive the same page as a regular client

#### Directivas de IA — 100/100

- **PASS** Homepage is indexable
- **WARN** Google-Extended is disallowed, but this page is still eligible for AI Overviews
  robots.txt disallows Google-Extended; no nosnippet or max-snippet directive is set on the page.
  Google-Extended governs Gemini training and grounding in Gemini Apps and Vertex AI. AI Overviews and AI Mode follow Googlebot and the snippet directives instead. If the intent was to stay out of AI Overviews, use nosnippet or max-snippet. If the intent was to opt out of training, this is already correct.
  https://axrush.com/guides/ai-directives#google-extended-mismatch

#### Higiene HTTP — 80/100

- **WARN** A missing page redirects (301) instead of returning 404
  Location: https://www.figma.com/ax-audit-probe-68c6z87n
  A redirect on a nonexistent path hides the error. Return 404 or 410 so a client can tell the difference.
  https://axrush.com/guides/http-hygiene#soft-404-redirect
- **PASS** Homepage answers after 1 redirect
  301 → https://www.figma.com/
- **PASS** HEAD requests are supported
- **PASS** Content-Type: text/html with charset

#### Crawl Efficiency — 95/100

- **PASS** Response compressed with Brotli (br)
- **PASS** Cache validator present (ETag)
- **PASS** Conditional request returns 304 Not Modified
- **WARN** Homepage is on the large side (1.6 MB decompressed)
  Consider trimming inlined payloads to reduce crawl cost.
  https://axrush.com/guides/crawl-efficiency#large-page
- **WARN** Roughly 995 tokens of content in 418,360 tokens of response (100% markup)
  Estimated at four characters per token.
  An agent pays to receive the markup and then discards it. Serving Markdown on Accept negotiation is the direct fix.
  https://axrush.com/guides/crawl-efficiency#markup-overhead
- **PASS** Homepage responded in 95ms

### Descubrimiento — 53/100

#### LLMs.txt — 0/100

- **FAIL** /llms.txt not found
  HTTP 404
  Create a /llms.txt file at your site root following the llmstxt.org specification. It should be a Markdown file starting with "# Your Site Name" and include a description, sections, and links.
  https://axrush.com/guides/llms-txt#not-found

#### Robots.txt — 57/100

- **PASS** /robots.txt exists
- **WARN** 8/12 core AI crawlers configured
  Meta-ExternalAgent — Blocking it keeps your content out of Meta AI training and indexing.
Applebot-Extended — Opts your content out of Apple foundation-model training without affecting Siri or Spotlight.
Amazonbot — General crawler whose content may be used to train Amazon AI models.
Bytespider — Collects training data for ByteDance models. Compliance with robots.txt is disputed.
  Add explicit User-agent entries for the missing crawlers with Allow: / for each one.
  https://axrush.com/guides/robots-txt#missing-crawlers
- **WARN** 12 AI crawler(s) explicitly blocked
  GPTBot, ClaudeBot, CCBot, FacebookBot, Google-Extended, omgilibot, omgili, CHATGPT-User, OAI-SearchBot, PerplexityBot, Claude-SearchBot, Claude-User
  These crawlers have "Disallow: /" rules. If you want AI agents to access your site, change to "Allow: /" for each blocked crawler.
  https://axrush.com/guides/robots-txt#explicitly-blocked
- **WARN** 3 assistant search crawler(s) blocked — your site cannot be cited by those assistants
  OAI-SearchBot — Blocking it removes your site from ChatGPT search answers and citations.
PerplexityBot — Blocking it removes your site from Perplexity answers and citations. Not used for model training.
Claude-SearchBot — Blocking it removes your site from the index Claude cites when it searches the web.
  Search crawlers build the index an assistant cites from; they are separate from the training crawlers. If the intent was to opt out of training only, allow these and block the training tokens instead.
  https://axrush.com/guides/robots-txt#blocked-search-crawlers
- **PASS** 7 training crawler(s) blocked — recorded as a deliberate policy choice
  GPTBot, ClaudeBot, CCBot, FacebookBot, Google-Extended, omgilibot, omgili
- **WARN** 1 user-triggered fetcher(s) blocked in robots.txt that may ignore it
  CHATGPT-User — Since December 2025 OpenAI documents that robots.txt rules may not apply to this user-triggered fetcher.
  These clients fetch a page because a person asked for that URL, and their vendors document that robots.txt may not apply. Enforce at the edge if the block must hold.
  https://axrush.com/guides/robots-txt#blocked-user-fetchers
- **WARN** 1 robots.txt rule(s) target a retired or non-existent crawler token
  cohere-ai — Cohere states it operates no web crawlers.
  These rules have no effect. Remove them so the file reflects your actual policy.
  https://axrush.com/guides/robots-txt#legacy-tokens
- **PASS** Sitemap directive present
- **WARN** No Content-Signal directive found (optional)
  Declare how crawlers may use your content after access with the Content Signals Policy, e.g.: Content-Signal: search=yes, ai-train=no. Known signals: search, ai-input, ai-train, plus the optional use=immediate|reference|full. Generate yours at contentsignals.org.
  https://axrush.com/guides/robots-txt#missing-content-signals
- **PASS** 12/57 known AI crawlers have explicit rules

#### Meta Tags — 54/100

- **WARN** No AI meta tags (ai:*) found
  Add AI meta tags to your HTML <head>: <meta name="ai:summary" content="Brief description">, <meta name="ai:content_type" content="website">, <meta name="ai:author" content="Your Name">.
  https://axrush.com/guides/meta-tags#no-ai-meta
- **WARN** No rel="alternate" link to llms.txt in HTML
  Add to your <head>: <link rel="alternate" type="text/plain" href="/llms.txt" title="LLM-optimized content">
  https://axrush.com/guides/meta-tags#no-llms-alternate
- **WARN** No rel="alternate" link to the Agent Card in HTML
  Add to your <head>: <link rel="alternate" type="application/json" href="/.well-known/agent-card.json" title="Agent Card">
  https://axrush.com/guides/meta-tags#no-agent-alternate
- **WARN** No rel="me" identity links found
  Add rel="me" links to verify your identity across platforms: <link rel="me" href="https://github.com/yourname">, <link rel="me" href="https://twitter.com/yourname">.
  https://axrush.com/guides/meta-tags#no-rel-me
- **PASS** OpenGraph required tags present (og:title, og:description, og:url, og:type)
- **PASS** Twitter Card required tags present (twitter:card, twitter:title, twitter:description)

#### Sitemap — 100/100

- **PASS** Sitemap located: https://www.figma.com/sitemap.xml
- **PASS** Content-Type is XML (application/xml)
- **PASS** Sitemap-index references 11 child sitemap(s)
- **PASS** 3/3 sample child sitemap(s) reachable
- **PASS** Sample yielded 6237 URL(s) across 3 child(ren)
- **PASS** Newest <lastmod> is recent (1 day(s) ago)

#### HTTP Headers — 85/100

- **PASS** 4/7 security headers present
- **WARN** No Link header for AI discovery (llms.txt, Agent Card)
  Add a Link response header pointing to your AI discovery files: Link: </llms.txt>; rel="alternate"; type="text/plain", </.well-known/agent-card.json>; rel="alternate"; type="application/json"
  https://axrush.com/guides/http-headers#no-link-header
- **WARN** No machine-readable discovery relations beyond llms.txt and the Agent Card
  describedby — llms.txt v2 uses this relation to point a page at the llms.txt that covers it.
api-catalog — RFC 9727: the catalog of APIs this publisher offers.
service-desc — RFC 8631: a machine-readable API description.
service-doc — RFC 8631: human documentation for the API.
ai-catalog — Draft: the AI catalog listing agent cards and MCP server cards.
c2pa-manifest — C2PA 2.4: content provenance for media on the page.
license — RSL and other machine-readable licensing terms.
  Advertise what you publish with Link relations so agents stop guessing paths. Add the ones that apply, for example: Link: </llms.txt>; rel="describedby", </.well-known/api-catalog>; rel="api-catalog". Informational in 3.x: this does not affect your score.
  https://axrush.com/guides/http-headers#discovery-relations

### Protocolos — 0/100

#### Agent Card (A2A) — 0/100

- **FAIL** /.well-known/agent-card.json not found
  Site is agent-facing (an API surface (navigation into an API or developer area)). Also tried the pre-0.3 path /.well-known/agent.json. IANA-registered well-known URI.
  This site offers something an agent could call, but nothing tells an agent what. Publish an A2A Agent Card at /.well-known/agent-card.json. A minimal 1.0 card needs name, description, version, capabilities, supportedInterfaces, defaultInputModes, defaultOutputModes and skills. Spec: https://a2a-protocol.org/latest/specification/
  https://axrush.com/guides/agent-card#not-found

#### OpenAPI Spec — 0/100

- **FAIL** API surface present but no machine-readable description found
  Evidence of an API: navigation into an API or developer area. Checked /.well-known/api-catalog, Link and <link> rel="service-desc", and /.well-known/openapi.json, /openapi.json, /openapi.yaml, /.well-known/openapi.yaml, /api/openapi.json, /v1/openapi.json, /swagger.json, /api-docs, /asyncapi.json, /arazzo.json
  The API exists; nothing describes it in a form an agent can read, so using it requires a human to read your documentation first. Serve an OpenAPI description at /openapi.json and advertise it with Link: </openapi.json>; rel="service-desc". For several APIs, publish an RFC 9727 catalog.
  https://axrush.com/guides/api-discovery#not-found

#### MCP (Model Context Protocol) — N/D

- **PASS** No MCP server — MCP discovery does not apply to this site
  A server card describes an MCP server so agents can find it. A site that runs none has nothing to advertise. Run with --profile mcp to audit as though it did.

#### Catálogo de IA — 0/100 (informa, no puntúa)

- **WARN** No agent resource catalog found
  Checked robots.txt Agentmap: directive, Link header rel="ai-catalog", <link rel="ai-catalog">, well-known path and /.well-known/ai-catalog.json, /.well-known/ard.json. Both specifications are drafts.
  A catalog is one document listing everything an agent can call here — agent cards, MCP servers, APIs, skills — so a client stops probing four conventions to find out. Worth publishing once you have more than one of those. Informational: both ai-catalog.json and ard.json are still drafts, so this never affects your score.
  https://axrush.com/guides/ai-catalog#not-found

#### Habilidades de agente — 0/100

- **WARN** No Agent Skills published
  Checked /.well-known/agent-skills/index.json, /.well-known/skills/index.json, /skill.md, /SKILL.md. Draft specification — the path may still change. Cloudflare RFC v0.2.0 (2026-03-12). Not registered; a competing shorter path (/.well-known/skills/) also ships.
  This site has documentation, so it has procedures worth teaching. A skill is a SKILL.md an agent installs and follows: setup steps, argument shapes, the mistakes to avoid. Publish one per task at /.well-known/agent-skills/{name}/SKILL.md and list them in /.well-known/agent-skills/index.json.
  https://axrush.com/guides/agent-skills#not-found

#### WebMCP — N/D

- **PASS** No forms and no WebMCP code — nothing here for an agent to invoke as a tool

#### Descubrimiento de comercio — N/D

- **PASS** No commerce surface — agentic-commerce discovery does not apply to this site
  No Product or Offer structured data, cart links, or product price tags found.

#### Descubrimiento de autenticación — N/D

- **PASS** Nothing on this site requires authorization — auth discovery does not apply
  No API description, API catalog, MCP server card or commerce profile found.

### Política — 51/100

#### Security.txt — 100/100

- **PASS** /.well-known/security.txt exists
- **PASS** Required field "Contact" present
- **PASS** Required field "Expires" present
- **PASS** Expires date is in the future (2026-10-21)
- **PASS** 2/5 optional fields present

#### RSL License — 0/100

- **FAIL** No RSL license discovery found
  Checked robots.txt License directive, Link header, and <link rel="license" type="application/rsl+xml">
  Declare machine-readable licensing terms for your content with Really Simple Licensing. Add to robots.txt: License: https://your-site.com/license.xml — then publish the RSL document. See https://rslstandard.org.
  https://axrush.com/guides/rsl#not-found

#### Política de uso — 40/100

- **WARN** No machine-readable usage policy declared
  Checked robots.txt Content-Signal and Content-Usage, the Content-Usage and content-signal response headers, an RSL licence, TDMRep, and the noai meta directive.
  State your terms where they can be read without a lawyer. The lowest-effort option is a Content-Signal line in robots.txt: Content-Signal: search=yes, ai-input=yes, ai-train=no. Absence is neutral, not permission — but it also gives you nothing to point at.
  https://axrush.com/guides/usage-policy#no-policy

---

Representación en Markdown de https://axrush.com/report/figma.com