Magento 2 Audit: The Complete 2026 Guide to Technical, SEO, Performance & AI-Visibility Checks

What is a Magento 2 audit?

A Magento 2 audit is a systematic evaluation of an Adobe Commerce or Magento Open Source store that identifies technical defects, SEO gaps, performance bottlenecks, and AI-visibility problems, then ranks them by impact so a team knows what to fix first. It is diagnostic, not cosmetic: the deliverable is a scored report with concrete remediation steps, not a general opinion about the store.

In 2026 the term covers more than it used to. A store can pass a classic SEO audit — clean structure, fast pages, good Google rankings — and still be invisible to AI answer engines, because those systems evaluate a separate machine-readable layer. A modern Magento 2 audit therefore treats AI-search visibility as a first-class layer alongside the three traditional ones.

The four layers of a Magento 2 audit

1. Technical audit — is the store structurally sound?

The technical layer checks the foundations that everything else depends on:

• Crawlability & indexation — robots.txt rules, XML sitemap validity, canonical tags, noindex leaks, and duplicate URLs from layered navigation.
• Code & extension health — core patches applied, third-party module conflicts, deprecated code, and custom code that overrides core classes unnecessarily (the magento 2 code audit concern).
• Platform & security — running a supported release line, security patches current, and admin/checkout paths excluded from crawling. See the Adobe Commerce 2.4.7 end-of-life options for supported-version context.
• Infrastructure — caching (Varnish/FPC) configured, indexers healthy, cron running, and Redis/OpenSearch tuned.

2. On-page SEO audit — can search engines understand each page?

The on-page layer checks how well individual pages communicate their meaning:

• Title tags, meta descriptions, and heading hierarchy across category, product, and CMS pages.
• Structured data — microdata vs JSON-LD, and whether product entities are complete (this overlaps directly with the AEO layer below).
• Internal linking depth, breadcrumb consistency, and orphaned pages.
• Thin, duplicated, or auto-generated product copy that neither shoppers nor AI systems can use.

3. Performance audit — is the store fast enough to rank and convert?

The performance layer checks Core Web Vitals and the server-side factors behind them:

• Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift on real category and product templates.
• Time to First Byte, full-page-cache hit rate, and JavaScript bundle size (a recurring Hyvä vs Luma difference).
• Image delivery — modern formats, correct sizing, and lazy-loading that does not hide content from crawlers.

4. AI-search visibility audit (AEO) — can ChatGPT, Gemini & Perplexity recommend the store?

This is the layer most audit checklists still skip. AI answer engines pick one or two stores to recommend rather than listing ten links, and they decide using signals that classic SEO tools never inspect:

• AI-crawler access — whether search-time agents such as OAI-SearchBot, PerplexityBot, and Claude-SearchBot are allowed in robots.txt. Blocking them removes the store from generated answers entirely.
• Content map — presence of a valid llms.txt served at the domain root without redirects.
• Product schema — JSON-LD Product with a populated offers.availability; without it, ChatGPT Shopping skips the product.
• Product feed — a spec-compliant feed for agentic-commerce protocols.

For the full method behind this layer, see the Magento 2 AEO guide. To measure it directly, the free AEO audit returns a scored report in about two minutes.

Which audit layer needs which tool?

The first three layers are well served by mature tooling. The fourth is where most Magento stores have an untested blind spot in 2026.

How to run a first-pass Magento 2 audit yourself

1. Check supported version & patch level — confirm the store runs a supported release line and has current security patches.
2. Crawl the store — run Screaming Frog to surface broken links, redirect chains, missing titles, and duplicate URLs.
3. Validate Core Web Vitals — test real category and product templates in PageSpeed Insights, not just the homepage.
4. Inspect structured data — open a product page and check for JSON-LD Product with a populated offers.availability. See the Magento 2 Product JSON-LD schema guide.
5. Review AI-crawler access — confirm robots.txt allows search-time AI agents. See how to fix robots.txt for ChatGPT and Gemini.
6. Score the AEO layer — run bin/magento angeo:aeo:audit or the 2-minute self-assessment.

When do you need a professional Magento audit instead?

A self-assessment tells you where you stand. A professional audit adds three things a checklist cannot: prioritisation by revenue impact, a written remediation roadmap with effort estimates, and validation against how AI engines actually behave for your category rather than in theory. It is worth it when the store is large, the stakes are a replatform or migration decision, or when repeated internal fixes have not moved the numbers.

angeo.dev runs a structured 3-week AI Commerce Audit across eight signal categories, delivered as a scored report with a prioritised roadmap. If you only need the AI-visibility layer checked first, start with the free AEO self-assessment.