Sites/framer.com

Framer

Sign in to claim

framer.com

Framer is a site builder that allows users to create, collaborate, and go live with their websites.

saaswebsite-builderdesign-toolscontent-managementcollaboration-platform
41
AI-Readiness / 100
Level 3 · Agent-Accessible
500/5041
Pages analyzed
0/15
Questions answered
Live
For AI agents
Visit site →

Content

AI-judged Q&A · 70% of score

27

0 of 15 buyer questions answered cleanly

Your site doesn't cover:

limitsoperationspricing
See all 15 gaps →

Protocol

Technical hygiene · 30% of score

73

8 of 11 items installed

Missing:

MCP card +3WebMCP +3Content-Signal +3
Install with Lattis · +9 pts →

Protocol fix list

3 to ship · 8 passing

Start here

install the MCP server card

One JSON file at /.well-known/mcp/server-card.json tells agents you have an MCP server. Ours points at mcp.lattis.dev so Lattis handles queries for you.

+3 pts
Download server-card.json

Host at framer.com/.well-known/mcp/server-card.json — points agents at Lattis as your MCP server.

One-click installs

We host the heavy lifting — you ship one file or one line.

WebMCP

Paste the widget script — that is the W3C WebMCP draft (navigator.modelContext) and the actual integration. Then also host the discovery manifest so crawlers can find your tool surface without rendering JS. Do both; the script is the spec, the manifest is just discoverability.

+3 pts

1. Runtime — paste in <head>

<script async src="https://lattis.dev/widget.js"></script>

Calls navigator.modelContext.provideContext() — the W3C WebMCP draft. Agents on the page see your tools live, scoped to framer.com.

2. Discovery — host the manifest

Download webmcp.json

Host at framer.com/.well-known/webmcp.json. The WebMCP spec defines no discovery mechanism, so crawlers can't see runtime registrations — this manifest closes that gap.

Paste into robots.txt

Static snippets that tell agents your policy.

Content-Signal policy

Cloudflare-launched (Sep 2025) signal in robots.txt. Declare your stance on search, ai-input, and ai-train.

+3 pts
User-agent: *
Content-Signal: search=yes, ai-input=yes, ai-train=no
Allow: /

Add to framer.com/robots.txt. Adjust values: search, ai-input, ai-train each accept yes or no.

Already passing

✓ robots.txt✓ sitemap.xml✓ llms.txt✓ Allow major AI crawlers✓ Clean crawl rate✓ Markdown content negotiation✓ Server-rendered content✓ OpenAPI spec

Content gaps

15 gaps

MCP Server

AI agents can query this site directly via MCP. Add this endpoint to Claude Code, Cursor, or any MCP client.

Endpoint

https://mcp.lattis.dev/s/framer-com/mcp

Claude Code

claude mcp add framer --transport http https://mcp.lattis.dev/s/framer-com/mcp

Cursor

{
  "mcpServers": {
    "framer": {
      "url": "https://mcp.lattis.dev/s/framer-com/mcp"
    }
  }
}

WebMCP — runtime + discovery

1. Widget script — drop in <head>. WebMCP-capable browsers (Chrome 146+ Origin Trial) call navigator.modelContext.provideContext() via this script — that's the W3C draft and the actual integration agents care about.

<script async src="https://lattis.dev/widget.js"></script>

Renders a small "AI-indexed by Lattis" badge bottom-right. Hide with [data-lattis] { display: none !important; }.

2. Discovery manifest — host alongside the script. The WebMCP spec defines no discovery mechanism, so crawlers can't see the runtime registration. This static JSON closes the gap.

Download webmcp.json

Host at framer.com/.well-known/webmcp.json.