Platform guide

How to rank in AEO and GEO on a Framer site

By Arnav Mukherjee, founder of TofuBofu · July 6, 2026

Framer is built on React, and if you have read anything about AI crawlers you might brace for the worst, since raw React apps are exactly the kind of client-rendered content that AI engines cannot read. Here is the reassuring part: Framer does not ship a raw React app. It publishes server-rendered HTML, so AI crawlers like GPTBot and ClaudeBot receive your content in the page source, not an empty shell. Framer gets the hard requirement right.

That means the AEO work on Framer is a short, concrete list: add the schema Framer does not add for you, get your structure right, and write for buyer questions. Here it is, step by step.

Step 1: Confirm crawler access and rendering

Framer generates a robots.txt and lets you customize it in the site settings. Open it and make sure you are not disallowing AI crawlers like GPTBot, ClaudeBot, PerplexityBot, or Google-Extended.

Then run the view-source test on a live page to confirm your content is in the raw HTML, which on Framer it should be thanks to server-side rendering. It is a 30-second check that turns an assumption into a fact.

Step 2: Add JSON-LD through Custom Code

This is the main manual step. Framer supports JSON-LD through its Custom Code feature. You add a script tag with your schema to the end of the head:

• Site-wide: Site Settings, then Custom Code, and add the script to the end of the head for schema like Organization.
• One page: use that page's custom code to add page-specific schema such as FAQPage.
• CMS collection pages: put CMS variables inside the JSON-LD on the template, so each collection item outputs its own structured data automatically.

Publish, then validate the live URL with Google's Rich Results Test. FAQ schema is the one to prioritize: even after Google removed the visual FAQ result, AI engines still parse FAQPage into clean question-and-answer pairs.

Step 3: Assign real heading tags

In Framer, give your text real heading tags, H1 for the page title, H2 and H3 for sections, rather than only styling the font size. AI engines read the tag, not the look. Use one H1 per page, and write your headings as the questions buyers ask. That structure is what lets an engine lift a clean, self-contained answer from your page.

Step 4: Build answer-first pages with the CMS

Framer's CMS makes it easy to publish many specific, structured pages fast, which is an AEO advantage. Build pages that each answer one real buyer question, with the answer stated first, targeting qualified queries like your service for a particular industry or situation. Bind schema to those templates so every new page ships citation-ready.

Step 5: Add proof off-platform

A polished, structured Framer site still needs outside validation. AI engines corroborate your claims against third-party sources, so gather a few genuine reviews on the platforms your category uses. That off-site proof is frequently what moves a clean Framer site from readable to recommended.

The exact FAQ schema to paste

If the abstract talk of schema has you unsure what it actually looks like, here is a minimal, valid FAQPage block. Swap in a real question and answer your buyers ask, then on Framer add it through Custom Code at the end of the head.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "Do you support HIPAA compliance?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Yes. We provide HIPAA-compliant backups, access controls, and audit logging."
    }
  }]
}
</script>

Add three to six real question-and-answer pairs to the mainEntity array, keep every answer specific and self-contained so it reads well on its own, and after publishing, validate the live page with Google’s Rich Results Test. That one block is the highest-return piece of markup you can ship.

What good looks like: a before and after

Framer attracts design-forward founders, so the pattern here has a twist. Picture an AI-services agency with a slick Framer site. Someone told the founder that "React is invisible to AI crawlers," so they panicked and assumed the worst, or worse, they assumed Framer would handle everything and did nothing. Both are wrong. Framer server-renders, so the content is readable, but Framer adds no schema, and the agency's pages are gorgeous visual statements with almost no extractable, specific text. Ask AI "best NLP consulting firm for healthcare," and the agency is nowhere, despite genuinely doing that work.

The after keeps the aesthetic and adds substance a machine can use. The agency builds a CMS collection of specific capability pages, each opening with a plain-language answer and its own FAQPage schema bound to CMS variables through Custom Code. They assign real heading tags instead of styled display text. And they drop an Organization schema block into the site-wide head. The site still looks like a Framer site, which is to say excellent. But now each capability is a clean, structured, cited answer, and the agency starts showing up for the exact queries its buyers ask.

The mistakes I see most on Framer

Framer's failure modes cluster around two false beliefs: that React dooms you, and that a beautiful site is a finished site.

How to know it worked

Framer gives you a real published URL, so verification is direct. After publishing, view the source and confirm your content and JSON-LD are in the raw HTML, which they should be given Framer's server-side rendering. Run the URL through Google's Rich Results Test to confirm the schema is valid. Then re-scan your brand across the AI engines to see whether the specific capability queries you targeted have started to name you.

Then run it as a loop. Framer's CMS is built for producing polished pages quickly, so the cadence is: publish a specific capability page, let engines re-crawl over the following weeks, check which queries moved, and target the next page at the next gap. On Framer, the design will always be handled. The work that actually moves your AI visibility is the structured substance underneath it.