Magento Open Source Adobe Commerce Storefront design & front-end Independent · not affiliated with Adobe
Magento Themes Store Storefront Lab

Magento SEO

Structural search optimisation in Magento usually begins with crawlable URLs, so the fix starts with evidence from rewrites, logs and crawl data.

The structural half of Magento SEO

Magento SEO usually starts with a URL problem, not a copy problem. Layered navigation, configurable suffixes, pagination and store-view rules can leave a crawler with many routes to the same catalogue entity. Even strong category content cannot compensate for crawl attention spent on URLs customers never use.

Most Magento SEO services cover two jobs: repairing that structure and improving content, metadata and internal linking. The structural half is the part a merchant can test without waiting for an agency report. It begins with URLs, response codes, canonical signals and the rewrite records connecting requests to destinations.

Start with crawlable architecture

Magento’s layered navigation can expose an effectively unbounded set of crawlable URLs when category filters and options appear as links. The issue is not the number of products. It is the number of routes through the same catalogue data, especially where combinations, sort orders and tracking parameters create additional requests.

Inspect the navigation in rendered HTML and identify which controls pass crawlable links. Faceted routes should normally prevent search engines from indexing internal filter combinations while leaving useful category pages available for crawling. Check whether filtering changes the canonical target as well as the robots directive.

  • Follow several category and filter combinations from the rendered page.
  • Record the URL, response code, canonical target and robots directive.
  • Look for repeated routes that serve the same content without a deliberate reason.

Do not leave canonicals to chance

Do not assume canonical tags are enabled by default. Review the canonical settings for products, categories and custom routes, then make each indexable final URL reference itself. A canonical is a preference, not a redirect, and it does not reliably repair poor internal linking.

Where duplicate variants exist, select one preferred URL and point the others towards it. Avoid using canonical tags to conceal redirect chains, soft 404s or arbitrary parameter variants. Test the HTML source and response headers, because the rendered canonical can differ from the one implied by the storefront settings.

Pagination and URL suffixes

Each paginated category page should normally have a unique, indexable URL and a self-referencing canonical. Do not canonicalise every page to page one: that treats deeper listings as duplicates and removes legitimate entry points. Check that category links, generated sitemaps and pagination controls all use the same final URLs.

Product and category URL suffixes can multiply otherwise sensible routes. A product might be reachable through several combinations of URL key, suffix and path. Decide which form is canonical, remove internal links to the others and preserve the old addresses with direct permanent redirects where they have external value.

Store views need one URL policy

Multi-store Magento installations add another duplication layer. Store codes, websites, currencies, customer groups and session behaviour can produce URLs that look similar but serve different inventory or pricing. Decide whether store views require separate indexable URLs or should share one canonical host with controlled navigation.

Check how the same product appears across store views, whether links switch store context, and whether session or currency parameters appear in crawlable links. The chosen policy must be consistent in templates, navigation, sitemaps and canonical output.

See the damage in the evidence

Use crawl data, server logs and Magento’s URL rewrite records together. No single source gives the complete picture: search data shows what search engines discovered, logs show what they requested, and the rewrite table shows how Magento resolved them.

Evidence What to inspect What it reveals
Crawl statistics Discovered, crawled and indexed URLs Pages search engines can see and which routes they ignore
Server logs Status codes, request paths and crawler activity Crawl traps, errors, redirect chains and wasted requests
URL rewrite table Request paths, targets and redirect types Stale mappings, duplicate routes and broken catalogue transitions
Rendered HTML Canonical tags, robots directives and internal links What the storefront actually tells crawlers

Search Console’s crawl statistics and URL inspection results are useful starting points, but they are not a complete server log. Compare them with requests received during the same period. Magento’s generated sitemap provides another check: compare its URLs with the canonical set and with the routes found in navigation.

Look for server errors, redirected URLs that never resolve, pages returning soft 404s and requests for products or categories that no longer exist. Also check whether parameters such as tracking codes, sort options or session identifiers create crawlable duplicates.

Control redirect sprawl

Catalogue changes leave old URLs behind. Replacing a category, disabling a product or reorganising a tree can produce years of accumulated mappings if each change adds another hop. Search the rewrite records and logs for chains, loops and redirects to generic home or category pages.

Send each obsolete address directly to its closest relevant replacement where one exists. Use a permanent redirect for a lasting move, retain useful query information when it has a destination and avoid chains. A product that has genuinely disappeared needs an appropriate absence response, not a permanent redirect to an unrelated category.

Content still matters, but it cannot repair structure

Category introductions, product descriptions, metadata and internal links help search engines understand and distinguish the pages that deserve to rank. Structured product data should describe the same product shown on the page. Image alternative text and headings also make the rendered page easier to interpret.

These improvements should follow the structural work. Rewriting ten descriptions does not solve hundreds of duplicate routes, and a canonical tag does not compensate for a category page with no useful content. The catalogue, URL policy and content strategy need to point to the same preferred destination.

Front-end changes can alter the crawl surface

Changing the front end can affect what crawlers receive even when the catalogue data stays intact. Luma uses Knockout.js and RequireJS, while Hyvä uses Alpine.js and Tailwind CSS. Neither stack makes rendered output or crawlability automatic; inspect the HTML and routing rather than assuming the framework handles them.

For React-based or headless implementations, confirm that important category, product and pagination content is present in server-rendered or otherwise reliably retrievable responses. Check canonical tags, links and status codes as part of any front-end and speed migration rather than treating the launch as a visual change.

A practical repair order

  1. Identify duplicate routes and crawl traps using logs and crawl data.
  2. Define one preferred URL for each product, category and store-view route.
  3. Correct navigation, pagination, canonical output and sitemap generation.
  4. Replace redirect chains with direct, tested permanent mappings.
  5. Review product and category content after the URL structure is stable.
  6. Retest rendered HTML, indexing and catalogue performance after deployment.

A credible Magento SEO service should separate these structural tasks from editorial work and show the evidence for both. A merchant can audit the structural half directly in the admin URL rewrite table, rendered pages, Search Console and server logs. That makes the scope clearer, exposes unsafe assumptions and prevents content work from being used as a substitute for fixing the crawlable structure.

Questions this page answers

How should faceted Magento routes be handled?
Faceted routes should normally prevent search engines from indexing internal filter combinations while leaving useful category pages available for crawling.
What should each paginated category page have?
Each should normally have a unique, indexable URL and a self-referencing canonical. Do not canonicalise every page to page one.
How should obsolete catalogue URLs be redirected?
Send each obsolete address directly to its closest relevant replacement where one exists. Use a permanent redirect for a lasting move and avoid chains.
Which sources should be used to inspect Magentou2019s crawl structure?
Use crawl data, server logs and Magentou2019s URL rewrite records together. Also compare the generated sitemap with the canonical set and routes found in navigation.

Guides in this section

Editorial & corrections: [email protected]