Magento gives a retailer a great deal of control, and much of that control arrives set up for a demo store rather than for a search engine. This page is for UK businesses running Magento Open Source or Adobe Commerce who suspect the platform itself is holding back their organic traffic. If you want help with an online shop more broadly, my ecommerce SEO service covers the wider strategy. Here I deal with what is particular to Magento.
What Magento SEO fixes
A Magento store can publish far more URLs than it has products. Layered navigation, sort orders, page-size options, store views and category paths in product addresses all create pages Google can find, and each one competes with the page you actually want to rank. The first thing I measure is the gap between the number of pages you sell from and the number Google says it has found.
Closing that gap is mostly technical SEO applied to one platform’s habits. The aim is a store where every category and product has one address, Google spends its visits on those addresses, templates load quickly on a phone, and the admin settings stop quietly undoing the work whenever someone adds a range or installs an extension. For you, that means less wasted crawling, cleaner indexing reports and category pages with a fair chance of ranking for what your customers type.
Who it suits, and who it does not
It suits UK retailers on Magento 2 or Adobe Commerce with a catalogue large enough for duplication to matter, usually a few hundred products or more, and a developer or agency who can make changes. It also suits businesses running trade and retail store views side by side, or several brands from one installation.
It is less useful if you are still on Magento 1. Adobe ended support for it in June 2020, and SEO fixes on an unsupported platform are money spent on something you will have to replace. There the priority is the move itself, and website migration SEO protects what you have built while you rebuild on Magento 2 or change platform. If you are weighing up a switch, I will explain the search trade-offs plainly: Shopify SEO comes with a different set of limits, not fewer of them.
What the work covers
Layered navigation and filter URLs
Filters by colour, size, price and brand help shoppers and, left alone, give Google an endless supply of near-identical pages. I decide which filter combinations deserve an indexable landing page, because people genuinely search for something like “black leather ankle boots”, and which should stay out of the index. Then I specify how to handle the rest with canonicals, noindex, robots rules or links that crawlers cannot follow, depending on what your theme and extensions support. Faceted navigation is where most crawl problems on Magento begin, so this is usually the biggest single lever.
Product URLs, canonicals and configurable products
Magento can show one product at several addresses, with and without the category path in front of it. Configurable products add another layer: if the simple products behind each size or colour are visible individually, each becomes its own thin page. I compare the store’s SEO settings with the canonical tags the pages actually output, which do not always match what the admin suggests, and recommend one consistent rule for every product type.
Sorting, pagination and internal search
Sort order, products-per-page and grid or list parameters create copies of every category. Internal search results get indexed when they should not. Paginated categories need to stay crawlable so products deeper in a range are still found. Each fix is small on its own; together they decide how much of your crawl budget reaches the products you sell.
Store views, sitemaps and robots.txt
Multi-store set-ups leak in predictable ways: a trade store view indexed alongside the retail one, a staging copy left open, or an XML sitemap that still lists disabled products. I check how sitemaps are generated for each store view, what the robots.txt held in the admin really says, and whether everything meant to be private is.
Speed and Core Web Vitals
The default Luma front end loads a lot of JavaScript, and each extension tends to add more. I measure Core Web Vitals from real-user data where your traffic allows, find what is slowing the category and product templates, and work through caching, image handling and script loading with your developer. Where a new front end is the honest answer, I say so and set out the search risk of rebuilding alongside the benefit.
Structured data and product feeds
It is common for a Magento store to output product markup twice, once from the theme and again from an extension, sometimes with different prices. I make sure each product page carries one clean set of Product schema, with the price in pounds, availability, and reviews only where you genuinely collect them, and that it agrees with the feed you send to Google Merchant Center. Wider structured data work across the site sits under schema markup and structured data.
Category and product content
Magento templates arrive with no useful copy. I write briefs for the categories that matter commercially so each one answers a shopper’s real questions, and fix titles and meta descriptions in bulk using patterns built from your own product attributes rather than editing pages one at a time.
How I run a Magento SEO engagement
- Access and crawl. I ask for a restricted admin user, Search Console and analytics, then crawl the store as Google would and compare what I find with what is indexed. On larger catalogues, server logs show where Googlebot really spends its time.
- Configuration review. I go through the SEO, sitemap and robots settings for each store view, and list every installed extension that touches URLs, metadata or markup.
- Prioritised plan. You get a written list of fixes ranked by likely impact and effort, with the reason behind each one.
- Developer tickets. For every fix I write a ticket your Magento developer or agency can work from: the current behaviour, the behaviour needed and how to test it. The code stays with the people who maintain your store.
- Staging check and release. I test changes on staging before they go live, then check the live store and Search Console once they are released.
- Monitoring. Upgrades and new extensions can reverse earlier fixes, so if you keep me on I recheck after each release.
Problems I check for first on UK Magento stores
- Thousands of filter URLs indexed while the main categories sit on page two.
- Products reachable under several category paths, each pointing its canonical somewhere different.
- A staging or development store view open to Google, sometimes carrying the live catalogue.
- Discontinued products returning a 404 rather than being redirected to the closest alternative, throwing away links that took years to earn.
- Structured data showing prices without VAT while the page shows VAT-inclusive prices, a mismatch that can lead to Merchant Center disapprovals.
- Duplicate titles across store views because the defaults were never overridden.
- Two SEO extensions installed at once, each with its own idea of the canonical.
- Old URL rewrites left behind after a category restructure, producing chains of redirects.
What you receive
- A crawl and index report comparing the URLs your store produces with the ones it should, broken down by type.
- A configuration review of SEO settings, sitemaps, robots.txt and extensions for each store view.
- A filter map setting out which layered navigation combinations to index and which to keep out.
- A prioritised action plan with developer-ready tickets.
- Content briefs for your most valuable categories.
- Checks in Search Console after each release, and a short monthly summary if the work continues.
Next step
Send me your store’s address and I will look at how it is indexed, which Magento settings are likely to be causing trouble and what I would fix first. Requesting a free SEO audit is the simplest way to start. If you would rather talk it through, book a call with me and bring your developer along if you have one.