How to fix aeo schema client rendered on Wix

Steps for Wix

1. In the Wix Editor open your site and go to the page you want to add schema to.
2. Click Add → Embed Code → Embed HTML (Custom Code) and place the JSON-LD block in the <head> section — IMPORTANT: use Wix's 'Add Custom Code' feature under Settings → Custom Code, NOT Velo (JavaScript) for schema, as Velo runs client-side.
3. In the Wix dashboard go to Settings → Custom Code → click '+ Add Custom Code', paste your complete <script type="application/ld+json">…</script> block, select 'Head' as placement, and set it to load on the relevant pages.
4. For dynamic product pages (Wix Stores), use the Wix SEO Wiz or Wix's built-in structured data support — Wix automatically outputs Product schema server-side for Wix Stores items; verify this is enabled under Store → Settings → SEO.
5. View the page source to confirm the JSON-LD appears in the raw HTML. Note: Wix's custom code placed in 'Head' IS server-rendered; code injected via Velo's $w() or window events is NOT.

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.