Framer SEO Audit: Rendering, Schema, and AI-Crawlability Check

The short answer

Framer's rendering is not the problem people fear. Since traffic-aware pre-rendering rolled out across all sites in late 2025, Framer serves fully pre-rendered HTML to AI crawlers, so bots that don't run JavaScript still get your headings and copy. The real risks are manual: missing JSON-LD schema, and Cloudflare quietly blocking AI bots by default.

The JS-rendering fear vs. the reality

Framer is a design-first tool that produces heavily JavaScript-driven sites, so it's fair to worry about client-side rendering. The concern is real in general: GPTBot, ClaudeBot, and PerplexityBot do not execute JavaScript, do not wait for rendering, and do not make second attempts. (aioclicks) If a page is a client-side shell, an AI crawler sees nothing and moves on.

But Framer handles this at the platform level. Framer delivers server-rendered / pre-rendered HTML, so AI crawlers and search engines get full-page content without executing JavaScript — headings, paragraphs, and semantic HTML all arrive in the initial response. (INSIDEA) So the content-visibility problem is largely solved for you. What's left is structure and access.

Where Framer actually leaves you exposed

Schema is manual JSON-LD. Framer's advanced SEO has limits: custom canonical links (below Enterprise), editable robots.txt, and schema markup all require manual work. Framer does not auto-generate the schemas that matter for AEO — FAQPage, Article, SpeakableSpecification, and HowTo. All four are implementable via custom JSON-LD, but none appear unless you add them. (INSIDEA) Most Framer sites ship with none.

Cloudflare may be blocking your AI crawlers. This is the silent killer. Cloudflare changed its default configuration to automatically block AI bots — if your Framer site sits behind Cloudflare, your AI crawler access may have been shut off without you realizing it. (INSIDEA) Perfectly rendered HTML is worthless if GPTBot gets a 403 before it reads a word.

AI-crawler rules aren't set by default. You want explicit allow rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Applebot-Extended, and CCBot in robots.txt. Framer lets you edit robots.txt, but doesn't configure this for you.

Canonicals are gated. Custom canonical links sit below the Enterprise tier, which matters if you have duplicate or campaign-parameter URLs. (oma-kase)

The fixes that matter

1. Confirm AI crawlers aren't blocked — check Cloudflare bot settings and your robots.txt for accidental Disallow rules against GPTBot and friends.

2. Add explicit allow rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Applebot-Extended, and CCBot.

3. Add FAQPage JSON-LD to pages with real Q&A content.

4. Add Article schema to blog and resource pages.

5. Add SpeakableSpecification to pages you want voice/AI assistants to read aloud.

6. Verify canonical handling; on lower tiers, avoid the duplicate-URL patterns you can't fully control.

7. Confirm each page's pre-rendered HTML actually contains your key content by viewing source, not the rendered DOM.

Framer SEO + AEO checklist

FAQ