How to fix aeo schema client rendered on Adobe Commerce (Magento)

Steps for Adobe Commerce (Magento)

1. Locate the relevant layout XML file for the page type (e.g., catalog_product_view.xml in your theme's Magento_Catalog/layout/ directory).
2. Add a <block> or <referenceContainer> entry that calls a PHP Block class responsible for rendering the JSON-LD <script> tag, using the product's data model ($product->getName(), $product->getFinalPrice(), etc.) to populate values server-side.
3. Alternatively, create a .phtml template file in your theme (e.g., Magento_Catalog/templates/product/schema.phtml) that echoes the JSON-LD block using PHP, and reference it from the layout XML.
4. If you use an SEO extension (e.g., Mageplaza SEO, Amasty SEO), check its configuration under Stores → Configuration → [Extension Name] → Structured Data and ensure 'Render Method' is set to server-side/PHP, not JavaScript.
5. Run bin/magento cache:flush after making template changes, then view the page source to confirm the JSON-LD block is present in the raw HTML response.

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.