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

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

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