Frozen archive
This report was produced on September 23, 2026. Scans are no longer run, and www.figma.com may have changed since.
Readiness only — no security assessment was run on sites I don't own.
This scan is incomplete
3 checks could not retrieve content. The score reflects only what was readable.
Observed responses: 200 ×3, 404 ×3
Checks without content: llms_txt, agents_md, machine_endpoint
This scan completed with notes
- Followed redirect to the canonical host: https://www.figma.com
www.figma.com
Scanned on September 23, 2026
Followed redirect to https://www.figma.com
58/100
Signal breakdown
The score above combines two different things: whether an agent can understand this site at all, and whether the site has adopted the emerging optional agent conventions. They're grouped separately here because a site can be excellent at one and have none of the other.
Comprehension
Whether an agent can read and understand the page at all.
48/58(83%)
Agent convention adoption
Whether the site has adopted the emerging optional agent conventions.
10/42(24%)
Tap a row to see how to fix it.
Do these first
The highest-impact fixes, ranked by points left on the table.
- 1llms.txt+12 pts available
Add a /llms.txt file at your site root: a plain-text/markdown document with a title and links describing your site for AI agents. See https://llmstxt.org for the convention.
- 2AGENTS.md+10 pts available
Add an /AGENTS.md file at your site root with markdown headings describing how AI agents should interact with your project. See https://agents.md for the convention.
- 3Machine-Readable Endpoint+10 pts available
Publish a /.well-known/mcp.json (Model Context Protocol manifest) for the strongest signal, or at minimum an /openapi.json spec or a visible 'API Docs' link on your homepage.
Scanned by AgentLitmusBot. Methodology v0.1. Source. All archived reports.