How to fix aeo schema client rendered on Webflow

Steps for Webflow

1. In the Webflow Designer select the page you want to edit and open Page Settings (the gear icon next to the page name in the Pages panel).
2. Scroll to 'Custom Code' → 'Head Code' section and paste your complete <script type="application/ld+json">…</script> block there — Webflow renders this server-side in the published HTML.
3. For CMS Collection pages (e.g., product detail pages), open the Collection Template's Page Settings and use Webflow CMS field bindings inside the JSON-LD values — you can manually reference field slugs like {{Name}}, {{Price}} using Webflow's Embed element with CMS bindings, which are rendered server-side.
4. Do NOT use Webflow Interactions or custom JavaScript to inject schema dynamically — this creates client-rendered schema invisible to AI crawlers.
5. Publish the site and view the page source to confirm the JSON-LD block appears in raw HTML.

What is aeo schema client rendered?

Structured data (also called schema markup) is a block of code — usually written in JSON-LD format inside a `<script type="application/ld+json">` tag — that tells search engines and AI systems exactly what your page is about: the product name, price, reviews, breadcrumbs, and more. "Client-rendered" means this code is injected into the page by JavaScript after the browser loads, rather than being baked into the HTML that the server sends. The problem is that many crawlers — especially AI-powered ones like GPTBot (ChatGPT), ClaudeBot (Anthropic), and PerplexityBot — fetch your raw HTML and never run JavaScript, so they never see the schema at all.

AI answer engines (ChatGPT, Perplexity, Claude, Google's AI Overviews) increasingly pull structured product data directly from your page to populate citations, shopping answers, and summaries. If your schema only exists after JavaScript runs, these crawlers see a blank — meaning your products are invisible to AI-driven discovery, costing you valuable citation traffic. Traditional search engines like Google also prefer server-rendered schema; client-rendered schema is never guaranteed to be indexed, putting your rich results (star ratings, price drops, availability badges) at risk and reducing your click-through rates from organic search.

See the complete Aeo schema client rendered guide for every platform and the full background.