Why we think this is Framer (2 signals)
- · framerusercontent.com
- · meta generator: Framer
1 failed · 3 partial out of 7 that apply to your site.
Quick Wins
Top 3 fixes ranked by score impact
- 01Fail+5 pts if fixed
Explicit AI bot rules
See full detailsAdd explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
- 02Partial+2 pts if fixed
robots.txt present & sane
See full detailsServe a non-blocking /robots.txt that references your Sitemap.
- 03Partial+2 pts if fixed
Link header for discovery
See full detailsAdd a Link header with rel="api-catalog" or rel="describedby".
# Agent-readiness remediation brief Site: https://www.framer.com/ Platform: framer (99% confidence) AIScan score: 69/100 — Level 3 (Governed) Rubric: v2026-06-08.1 ## Failing checks (sorted by weight) - **[D1] robots.txt present & sane** — PARTIAL - Evidence: 200 OK, 29 bytes - Fix: Serve a non-blocking /robots.txt that references your Sitemap. - **[B2] Explicit AI bot rules** — FAIL - Evidence: 0 known AI agent(s) addressed in robots.txt - Fix: Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc. - **[C3] Structured HTML (title, meta, JSON-LD, single H1)** — PARTIAL - Evidence: h1: 0, title: true, meta description: true, JSON-LD: false - Fix: Ensure a single <h1>, <title>, meta description, and schema.org JSON-LD. - **[D3] Link header for discovery** — PARTIAL - Evidence: Link: <https://framerusercontent.com>; rel="preconnect", <https://framerusercontent.com>; rel="preconnect"; crossorigin="" - Fix: Add a Link header with rel="api-catalog" or rel="describedby". ## General guidance - Static-first: `robots.txt`, `llms.txt`, `/.well-known/*` JSON cards. - Markdown negotiation: serve `text/markdown` when requested via `Accept` header or `?format=md`. - Bot access: explicit allow/deny per AI user-agent (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Applebot-Extended, Bytespider, Amazonbot, CCBot, meta-externalagent, cohere-ai, Diffbot). - Capabilities: publish an MCP server card and (optionally) an Agent Skills manifest even if the runtime isn't live — discovery first. - Re-scan at aiscan.site after deploying.
Discoverability
69Can agents find your pages? robots, sitemaps, llms.txt.
Content
89Can agents read your content cleanly? Markdown, structured data.
Bot Access
0Are AI crawlers explicitly allowed or blocked?
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · B2
What we found0 known AI agent(s) addressed in robots.txt
How to fix itAdd explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
1.⚡ Fix automatically with AIScanThe fastest way to apply this fix is using AIScan's own agent tooling — it gives any AI coding assistant machine-readable instructions for this exact check. **Option A — Claude Code skill** 1. Download `CLAUDE.md` from https://aiscan.site/CLAUDE.md and drop it into your project root. 2. Ask Claude Code: *"Fix the failing AIScan check for <your-url>"* — it will read the skill, call our API, and apply the fix. **Option B — MCP (any MCP-compatible agent: Claude Desktop, Cursor, etc.)** - Endpoint: `https://aiscan.site/api/mcp` - Tools: `scan_website`, `get_fixes`, `get_grade` - Call `get_fixes` with your URL for machine-readable fix instructions. **Option C — REST API (any tool / script)** ``` GET https://aiscan.site/api/public/scan?url=YOUR_URL ``` Returns the full report including failing checks and fix details. Then re-scan at https://aiscan.site to verify.
2.Add explicit User-agent blocksDon't rely on `User-agent: *` alone. Address each major AI crawler so your policy is unambiguous.
3.Recommended blockUser-agent: GPTBot Allow: / User-agent: ClaudeBot Allow: / User-agent: PerplexityBot Allow: / User-agent: Google-Extended Allow: / User-agent: Applebot-Extended Allow: /
4.VerifyAfter deploying, re-scan at https://aiscan.site. You can also test with `curl -I` or `curl` directly.
Embed your AIScan badge
Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of www.framer.com on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Fwww.framer.com%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade B (69/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=69&grade=B&host=www.framer.com" alt="AIScan.site Grade B — 69/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Fwww.framer.com%2F)
Track this over time
Coming soon: save sites, schedule re-scans, get email when something material changes. Standards land weekly — your tracker shouldn't be one-shot.
Scan your own site
Get a plain-English agent-readiness report you can hand straight to ChatGPT or Claude.
Scan your site