Magento Open Source · Self-hosted ecommerce

Magento Open Source SEO audit: the issues built into Magento Open Source — and how to fix them

A Magento Open Source SEO audit checks your store across search, AI visibility, accessibility and security — with a fix for each issue we find.

The powerful, complex, developer-driven platform (now Adobe Commerce). Endlessly configurable — and endlessly capable of generating crawl and performance problems if left at defaults.

How does Magento Open Source's architecture shape your SEO?

Magento Open Source is self-hosted and built for large, complex catalogs, which is exactly why its SEO problems are at scale. Its layered navigation is the classic example: filterable attributes multiply into a vast space of parameter URLs. By default products can resolve under multiple category-path URLs, performance collapses without Varnish full-page cache and a tuned search backend, and security depends on you applying Magento's patch cadence. Most fixes are configuration- or developer-level, but they're well-trodden: canonical settings, layered-nav crawl control, full-page caching, and patch discipline.

Reference: Adobe Commerce SEO best practices →

What issues show up most on Magento Open Source sites?

Why these happen on Magento Open Source

Specific to how Magento Open Source is built — not generic checklist advice.

SEO

Layered navigation crawl explosion

This is the signature Magento SEO problem. Filterable attributes (color, size, price, brand) combine into millions of parameterised category URLs. Without robots and canonical controls, crawlers drown in them and your real category pages lose priority. Restrict crawlable filter combinations and canonical filtered views back to the base category.

SEO

Duplicate product URLs from category paths

By default Magento can serve the same product at /category/product.html and /product.html depending on the 'Use Categories Path for Product URLs' setting. Pick one structure and ensure canonicals enforce it, or you create duplicate-content clusters across your whole catalog.

SEO

Performance demands real infrastructure

Magento is heavy. Without Varnish full-page cache, a tuned OpenSearch/Elasticsearch backend, and production-mode compilation, category and product pages are slow enough to fail Core Web Vitals. Performance here is an infrastructure decision, not a plugin toggle.

OWASP

Security patch cadence is on you

Self-hosted Magento means you're responsible for applying Adobe's security patches promptly and hardening the admin path. Unpatched Magento installs are routinely exploited. Track the patch level and keep the admin URL non-default and protected.

Fixes written for Magento Open Source

We catalog 113 Magento Open Source fixes — exact steps for Magento Open Source's admin and theme, each with a link to the official docs.

Catalog coverageSEO

Audit your XML sitemap and internal linking so that every product and category page is discoverable and crawlable by Google — not hidden behind JavaScript, pagination, or missing links.

On Magento Open Source
  1. 1Follow the same steps as Adobe Commerce (Magento) above — the admin paths and sitemap configuration are identical in Magento Open Source.
  2. 2Run bin/magento indexer:reindex after making visibility or category changes to ensure the sitemap and flat tables are up to date.
  3. 3Check pub/robots.txt via Admin › Content › Design › Configuration to confirm crawl paths are open.
Code · Generic HTMLhtml
<!-- CORRECT: Standard crawlable link -->
<a href="/products/blue-running-shoes">Blue Running Shoes</a>

<!-- WRONG: JavaScript-only — Googlebot cannot follow this -->
<span onclick="navigate('/products/blue-running-shoes')">Blue Running Shoes</span>

Standard crawlable product link — use plain <a href> tags, never JavaScript-only click handlers, for navigation links that Google must follow.

Magento Open Source docs →
Cwv inpSEO

Reduce Interaction to Next Paint (INP) to under 200 ms by breaking up long JavaScript tasks, deferring non-critical third-party scripts, and lightening event handlers so the page feels fast and responsive after every tap or click.

On Magento Open Source
  1. 1Follow all Adobe Commerce (Magento) steps above — the admin paths and configuration options are identical.
  2. 2Additionally, use the free Yireo Webp2 or Hyva theme (if applicable) — the Hyva theme replaces Magento's heavy RequireJS/KnockoutJS stack with lightweight Alpine.js + Tailwind CSS, which dramatically reduces INP on many stores.
  3. 3Run `bin/magento setup:static-content:deploy` and `bin/magento cache:flush` after any JS configuration change.
Magento Open Source docs →
Faceted url indexableSEO

Point the rel=canonical on every faceted/filter URL to its clean parent category URL (or add noindex), so Google treats filtered pages as a single authoritative page instead of thousands of duplicates.

On Magento Open Source
  1. 1Same steps as Adobe Commerce (Magento) above — go to Stores → Configuration → Catalog → Catalog → Search Engine Optimization and set 'Use Canonical Link Meta Tag for Categories' to 'Yes'.
  2. 2For community extensions that add faceted/layered navigation, check the extension's configuration for SEO options including canonical and noindex settings.
  3. 3After configuration, flush the cache via System → Cache Management and verify by inspecting a filtered URL's page source.
Code · Generic HTMLhtml
<head>
  <!-- Canonical points to the CLEAN category URL, not the filtered variant -->
  <link rel="canonical" href="https://www.example.com/womens-pants">
</head>

Place this in the <head> of every filtered/faceted page. The href must be the clean parent category URL — never the filtered URL itself.

Magento Open Source docs →
Images missing altSEO

Add descriptive alt text to every product and content image so search engines and screen readers can understand what the image shows.

On Magento Open Source
  1. 1FOR PRODUCT IMAGES: Admin > Catalog > Products > open product > Images and Videos section > hover over image > gear icon > fill 'Alt Text' field > Save.
  2. 2FOR CMS CONTENT: Admin > Content > Pages or Blocks > open item > WYSIWYG editor > click image > Insert Image icon > fill 'Image Description' (alt) field.
  3. 3FOR BULK IMPORT: System > Data Transfer > Import > select Products entity type > prepare CSV with additional_image_labels column populated > upload and import.
Code · Generic HTMLhtml
<!-- BEFORE (missing alt — bad) -->
<img src="/images/red-leather-bag.jpg">

<!-- AFTER (descriptive alt — correct) -->
<img src="/images/red-leather-bag.jpg" alt="Red leather crossbody bag with gold buckle clasp">

<!-- Decorative image (intentionally empty alt — correct) -->
<img src="/images/divider-line.png" alt="">

Place this wherever an <img> tag appears in your HTML. Replace the placeholder text with your real description.

Magento Open Source docs →

Browse all 113 Magento Open Source fixes →

Magento Open Source on the open web

0.3% of the crawled web runs Magento Open Source

44,869
live Magento Open Source sites
#5
of 6 ecommerce platforms
0.3%
share of all crawled sites

Gaining share — +1.3% over the last 6 monthly crawls

Source: HTTP Archive — a real-Chrome crawl of 15.5M origins (2026-09-01). Share of all crawled sites, not just ecommerce.

How AI reads Magento Open Source sites · AEO

49% of Magento Open Source sites publish structured data

JSON-LD is the schema.org markup AI answer engines read to understand — and cite — a page. But 4.8% of Magento Open Source sites add it only after JavaScript runs, so non-JS AI crawlers never see it. SEOLZ checks whether your structured data is present, valid, and visible to AI.

49%
publish JSON-LD
37%
have Open Graph
4.8%
JSON-LD only via JS

Source: HTTP Archive — structured-data probes on static + rendered HTML across 43,964 Magento Open Source sites.

The typical Magento Open Source site · HTTP Archive

How Magento Open Source sites measure up

Performance — median

3.4 MB
page weight
208
requests
11.8s
load time

Accessibility gaps — share of sites

79%
empty image alt
44%
unlabelled fields
33%
non-semantic controls

Source: HTTP Archive lab performance + accessibility probes across 43,964 Magento Open Source sites. SEOLZ measures your site against these.

Every scan checks all six pillars

You can't rank what AI can't read. SEO, AEO, and GEO tell you where you rank; WCAG, OWASP, and Lifecycle determine whether search and AI can read and trust you at all. SEOLZ scores all six as one system.

🔍
SEO

Your catalog pages may be invisible to Google right now and you'd have no way to know. Indexability gaps, canonical conflicts, and faceted navigation issues silently kill organic traffic — we surface every one and tell you which to fix first.

Learn how to fix SEO issues →
✨
Answer Engine (AEO)

When someone asks ChatGPT to recommend a product in your category, is your store in the answer? Often it isn't. We check the structured data, page structure, and brand signals that help search and AI understand your products and describe them accurately — and we measure whether they actually cite you, or a competitor.

Learn how to fix Answer Engine (AEO) issues →
🌐
AI Visibility (GEO)

AI search is eating traditional organic traffic. We track your actual brand mentions across ChatGPT, Perplexity, and other AI engines — and tell you what's pushing you down in the results.

Learn how to fix AI Visibility (GEO) issues →
♿
Accessibility (WCAG)

Ecommerce stores are among the most frequent recipients of ADA accessibility demand letters. We run WCAG 2.1 AA checks across your catalog, surface the barriers that most often appear in demand letters, and track each one through to a verified fix.

Learn how to fix Accessibility (WCAG) issues →
🛡️
Security (OWASP)

A missing security header exposes your customers, and a compromised or flagged site loses search visibility fast. We check the server configuration, HTTPS setup, and email authentication issues that erode trust — before they become an incident.

Learn how to fix Security (OWASP) issues →
⏳
Site Lifecycle

SSL expires. Plugin versions fall behind. GTM containers go unverified. These aren't hypothetical risks — they're the operational failures that cause outages, ranking drops, and security incidents. We catch them before they happen.

Learn how to fix Site Lifecycle issues →

Start free. Upgrade when ready.

Scout
Free
1 site · 50 pages/audit · monthly audits
6-pillar welcome scan
  • ✓Composite + pillar scores
  • ✓Issue counts
  • ✓Recurring five-pillar re-scan
  • ✓Free forever
Start free
Starter
$49/mo
1 site · 500 pages/audit · weekly audits
All 6 pillars
  • ✓Every finding across all 6 pillars, with step-by-step fixes for your platform
  • ✓Template fixes: fix it once, clear it on every page built from that template
  • ✓Fix tracking: mark it fixed and the next audit confirms it
  • ✓Email alerts for score drops, new security issues, and SSL / domain expiry
  • ✓Report builder with PDF, HTML and Markdown export
  • ✓GTM & tracking audit, plus Search Console topic gaps
Choose Starter

Questions about Magento Open Source audits

Does SEOLZ work with Magento / Adobe Commerce?+

Yes — we crawl your live Magento Open Source or Adobe Commerce storefront and write fixes for Magento's admin configuration and developer workflow.

Why does Magento generate so many URLs?+

Layered navigation: every filterable attribute combination is a URL. It's powerful for shoppers but, uncontrolled, it floods the crawl. We identify the filter URLs being crawled and how to constrain them.

Do Magento fixes need a developer?+

Some are admin-configuration (canonical settings, URL structure), others are developer/infra (full-page cache, patches). We label each fix by where it lives so you know what your team or agency needs to touch.

See what's holding back your Magento Open Source site

Free scan, no credit card, results in minutes. We've got you.

Scan My Magento Open Source Site Free