Forem: Ievgenii Gryshkun

How to Check If Your Magento Store Is Visible to ChatGPT — Free AEO Audit Module

Ievgenii Gryshkun — Tue, 14 Apr 2026 20:35:57 +0000

Part 2 of the AEO for Magento 2 series. Part 1: What is llms.ljson and why eCommerce needs it.

Most Magento developers spend hours manually checking robots.txt, schema markup, and sitemap configurations. Then they wonder why their store still doesn't appear in ChatGPT or Gemini recommendations.

There is now a faster way.
🔗 This article was originally published on https://angeo.dev/magento-aeo-audit-module-chatgpt-visibility/:

The problem: no standard AEO checklist for Magento

SEO has Lighthouse. SEO has Search Console. SEO has audit tools built into every CI pipeline.

AEO — AI Engine Optimization — has almost nothing.

Magento developers who want to know whether their store is AI-visible have to check manually:

Is GPTBot allowed in robots.txt?
Does the store have a llms.txt file?
Is Product JSON-LD schema present on PDP pages?
Is there an AI-readable product feed for ChatGPT Shopping?
Does the homepage have FAQPage schema for answer-box eligibility?

This takes time, requires domain knowledge, and produces no consistent score to track over time.

Introducing: angeo/module-aeo-audit

angeo/module-aeo-audit is a free, open-source Magento 2 CLI module that runs a complete AEO audit with one command.

composer require angeo/module-aeo-audit
bin/magento setup:upgrade
bin/magento angeo:aeo:audit

The module checks 8 signal categories, scores your store from 0–100, and tells you exactly what to fix — with specific commands.

What it checks

Signal	Category	What it looks for
robots.txt — AI Bot Access	Critical	GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended
llms.txt — AI Content Map	Critical	Spec-compliant llms.txt at /llms.txt
Product JSON-LD Schema	Important	@type Product with offers.price and offers.availability
FAQPage Schema	Important	FAQPage schema on homepage
AI Product Feed	Important	Feed file at expected paths
sitemap.xml	Standard	sitemap_index.xml or sitemap.xml
Open Graph	Standard	og:title, og:description, og:image
Canonical Tags	Standard	rel=canonical on all pages

What the output looks like

╔══════════════════════════════════════════════════════════╗
║  Angeo AEO Audit — Store: default                        ║
╚══════════════════════════════════════════════════════════╝

✓ PASS  robots.txt — All 7 AI bots are permitted.
✗ FAIL  llms.txt — /llms.txt not found (404).
✓ PASS  sitemap.xml — found (1,243 URLs).
✓ PASS  Product Schema — Product JSON-LD found.
⚠ WARN  FAQPage Schema — No FAQPage schema on homepage.
✗ FAIL  AI Product Feed — No AI-readable product feed found.
✓ PASS  Open Graph — All required OG tags found.
✓ PASS  Canonical Tags — Canonical tag found.

AEO Score: [████████████░░░░░░░░] 50% — Needs Improvement
✓ Pass: 5   ⚠ Warn: 1   ✗ Fail: 2

Critical fixes needed:
→ composer require angeo/module-llms-txt
→ bin/magento angeo:llms:generate
→ composer require angeo/module-openai-product-feed

Every failed check includes a specific command. Not "fix your schema" — but exactly what to run.

Three output formats

# Default — readable table in terminal
bin/magento angeo:aeo:audit

# JSON — for dashboards or automated processing
bin/magento angeo:aeo:audit --format=json --output=/tmp/aeo-report.json

# Markdown — for Notion, docs, or sharing with clients
bin/magento angeo:aeo:audit --format=markdown

# Specific store only
bin/magento angeo:aeo:audit --store=en_gb

CI pipeline integration

The --fail-on flag exits with code 1 if the score drops below a threshold:

# Fail the build if AEO score drops below 80
bin/magento angeo:aeo:audit --fail-on=80

Add this to your GitHub Actions or GitLab CI pipeline — if a deploy breaks AI visibility, the build fails. Same way phpstan or phpcs works for code quality.

# .github/workflows/aeo.yml
- name: AEO Audit
  run: bin/magento angeo:aeo:audit --fail-on=80

How it fits the Angeo suite

module-aeo-audit is the diagnostic layer. It tells you what's missing. The other free modules fix those gaps:

# Fix signal 2 — llms.txt
composer require angeo/module-llms-txt
bin/magento angeo:llms:generate

# Fix signal 5 — AI product feed
composer require angeo/module-openai-product-feed

# Re-run audit to verify
bin/magento angeo:aeo:audit

Installation

Requirements: PHP 8.2+, Magento 2.4+, Magento Open Source or Adobe Commerce Cloud.

composer require angeo/module-aeo-audit
bin/magento setup:upgrade
bin/magento cache:flush
bin/magento angeo:aeo:audit

No admin configuration. No database changes. One CLI command registered.

Why this exists

ChatGPT referral traffic converts at 4–5× the rate of standard organic search. Most Magento stores have at least 2–3 critical AEO issues they don't know about — a robots.txt that blocks OAI-SearchBot, a product page with no JSON-LD schema, no llms.txt while competitors already have one.

The audit takes 30 seconds. The fixes usually take less than an hour.

Next in series: The Complete AEO Checklist for Magento 2 — 8 Signals, 90 Minutes — the step-by-step fix guide for every signal the audit checks.

Module on Packagist: packagist.org/packages/angeo/module-aeo-audit

What is llms.jsonl and why eCommerce needs it

Ievgenii Gryshkun — Sun, 12 Apr 2026 08:10:18 +0000

AI assistants don't read your website the way customers do. They need structured, machine-readable data — and that's exactly what llms.jsonl provides.

If you already know about llms.txt, think of llms.jsonl as its structured, data-rich sibling — purpose-built for eCommerce product catalogs.

🔗 This article was originally published on https://angeo.dev/what-is-llms-jsonl-and-why-ecommerce-needs-it/:

What Is llms.jsonl?

llms.jsonl stands for LLM-optimized Line-delimited JSON. It is a file where each line contains a complete, self-contained JSON object representing a single entity — a product, a category, or a CMS page.

Unlike a regular JSON array (which wraps everything in brackets and requires loading the whole file at once), JSONL is:

Streamable — AI agents can read it line by line
Scalable — stores with 50,000 SKUs don't need one giant file
Parseable — each line is valid JSON independently

A Single Product Line in llms.jsonl

{"type":"product","sku":"WB-004","name":"Alpine Hiking Jacket","price":189.99,"currency":"USD","url":"https://angeo.test/alpine-jacket","category":"Outerwear","short_description":"Waterproof 3-layer shell for alpine conditions","in_stock":true,"attributes":{"color":"Navy","size_options":["S","M","L","XL"],"material":"Gore-Tex"}}

Every product — one line. Every line — complete context for an AI to understand and recommend that product.

llms.txt vs llms.jsonl — What Is the Difference?

Feature	llms.txt	llms.jsonl
Format	Markdown (human-readable)	Line-delimited JSON (machine-readable)
Best for	Store overview, pages, categories	Full product catalog data
AI use case	Context & navigation	Product recommendations & queries
Scalability	Up to ~500 items	Unlimited (streamed line by line)
Attributes	Basic (name, URL, price)	Full (variants, stock, specs)

Both files work together. llms.txt tells AI what your store is. llms.jsonl tells AI what your store sells — in full detail.

Why Does eCommerce Specifically Need llms.jsonl?

1. AI Agents Need Structured Product Data

When a user asks ChatGPT or Claude "recommend a waterproof jacket under $200," the AI needs structured, queryable product data — not HTML product pages. llms.jsonl provides exactly that: a clean feed of every product with its attributes, price, stock status, and URL.

2. HTML Product Pages Are Noise for AI

A typical Magento 2 product page contains navigation menus, cookie banners, review widgets, upsell carousels, and footer links. The actual product data is buried inside this noise. AI context windows are limited, and parsing messy HTML wastes them. llms.jsonl gives AI only signal, zero noise.

3. Product Catalogs Are Too Large for llms.txt

A store with 5,000 SKUs cannot fit them all meaningfully into a single llms.txt file. llms.jsonl handles any catalog size because AI systems can stream and process it line by line — one product at a time.

4. Variants, Stock, and Pricing Change Daily

Unlike static blog content, product data changes constantly. A configurable product might have 12 size/color combinations. Stock goes in and out. Prices change with promotions. llms.jsonl is generated fresh by cron and always reflects the current state of your catalog.

What Does a Full llms.jsonl File Look Like?

Each line is an independent JSON object. Here is a multi-entity example:

{"type":"store","code":"angeo_en","name":"EN","url":"https:\/\/angeo.test\/","currency":"USD","locale":en}
{"type":"category","store":"angeo_nl","id":"4","name":"Sale","parent_id":"2","url":"https:\/\/angeo.test\/sale.html","description":"","embedding_text":"Sale "}
{"type":"product","store":"angeo_en","id":"4","sku":"product_sku","title":"product name","price":"123.00","currency":"USD","short_description":"","description":"test descriprtion","url":"https:\/\/angeo.test\/product-name.html","embedding_text":"product name  test descriprtion"}

An AI agent processing this file can instantly answer:

"What waterproof jackets do you have under $300?" → WB-001
"Do you have merino base layers?" → WB-002
"Is the 3-in-1 jacket in stock?" → No (in_stock: false)

How to Generate llms.jsonl for Magento 2

The open-source module angeo/module-llms-txt generates both llms.txt and llms.jsonl automatically for your Magento 2 store.

Install in 3 commands:

composer require angeo/module-llms-txt
bin/magento setup:upgrade
bin/magento cache:flush

After installation, navigate to:

Stores → Configuration → General → Angeo → LLMS

Generate manually or let cron handle scheduled updates. Both files are created at your store root:

https://yourstore.com/llms.txt
https://yourstore.com/llms.jsonl

The module supports multi-store and multi-language Magento 2 setups, includes unit tests for both file types, and is MIT licensed.

Source: Packagist

The Bigger Picture: AI Commerce Infrastructure

We are entering a phase where AI agents don't just recommend products — they initiate purchase flows on behalf of users. For an AI agent to recommend your products, it must be able to:

Understand what you sell
Filter by price, attributes, stock status
Navigate to a product URL and initiate checkout

Steps 1 and 2 are solved by llms.jsonl. Step 3 is the next frontier — but without steps 1 and 2, step 3 is impossible.

Stores that generate structured AI feeds today will be the ones AI agents recommend tomorrow.

Summary

llms.jsonl is a line-delimited JSON file that exposes your full product catalog to AI systems
It complements llms.txt — together they give AI both context and structured data
For Magento 2, the open-source angeo/module-llms-txt generates both files automatically
Implementation takes under 5 minutes and requires no custom development

The AI commerce era is not coming — it is already here. Structured product feeds are the foundation that makes your store visible to the systems that are replacing traditional search.

Have questions about llms.jsonl for Magento 2? Drop a comment below or check the module on Packagist.