Who this is for
Stores running Magento Open Source or Adobe Commerce with a real catalogue, usually several hundred to several thousand products, where organic traffic has plateaued or the store has grown faster than anyone’s attention to its URLs. It is also for teams planning a Magento replatform who want the SEO consequences handled before the launch rather than after. This sits alongside my broader eCommerce SEO work; the difference here is platform-specific.
The problems Magento creates, and the fixes
- Layered navigation. Every filter combination can generate a crawlable URL, so a category with five filters produces thousands of near-identical pages that consume crawl budget and split signals. The fix is a deliberate policy: which filter combinations are valuable enough to index (usually a small set with real search demand), which are canonicalised to the parent category, and which are blocked from crawling entirely.
- Products in multiple categories. Magento can serve the same product under several category paths. Canonical tags must point at one, consistently, and the store’s URL settings must not undo that.
- Category pagination. Page two onward needs self-canonicals rather than canonicals to page one, with enough on-page text on the first page only, so paginated pages remain crawlable without becoming duplicates.
- Speed. Magento’s default front end is heavy. The work is full-page caching configured properly, image sizing and formats, JavaScript bundling, a CDN, and often Varnish. This matters more than any content change for a store whose customers are on mobile data.
- Store views and multi-language. Multiple store views need correct hreflang and separate canonical handling, or the language versions compete with each other. See international SEO where you sell across markets.
- Product data quality. Manufacturer descriptions duplicated across every retailer selling the same item. Categories and the products you actually want to sell need original copy, specifications as text, and the questions buyers ask.
How a Magento SEO engagement runs
- Crawl and index audit. A full crawl to find how many URLs the store actually exposes versus how many you intended, then a comparison against what is indexed. On most Magento stores this is where the surprise is.
- URL and canonical policy. A written decision for filters, sorts, pagination, search pages and multi-category products, implemented in configuration rather than patched per page.
- Speed work, prioritised by what the field data says rather than by a lab score.
- Category and product template optimization: titles, headings, on-page copy placement, internal linking between related categories, and structured data for products, offers, availability and reviews.
- Content on the categories that carry margin, not all of them, plus buying guides where the research happens off the product page.
- Monitoring of index counts, crawl stats, Core Web Vitals and organic revenue by category, monthly.
What you receive
- A crawl and index report with the URL bloat quantified and the cause named.
- A written URL, canonical and indexation policy your developers can implement.
- Prioritised speed recommendations with the expected effect on Core Web Vitals.
- Optimized category and product templates, and copy for the categories that matter commercially.
- Structured data implemented and validated.
- Monthly reporting on organic revenue by category, not just sessions.
Next step
If the store is on Magento and organic traffic has stopped growing, the crawl is the fastest way to find out why, and it is the first thing the free SEO audit covers. If a replatform is planned, involve me before the URL structure is decided rather than after: see website migration SEO. For stores on other platforms, see Shopify SEO and WooCommerce SEO.
