What is Magento layered navigation and how does it affect SEO?
Magento layered navigation is the faceted filter system that lets shoppers narrow a category by attributes — colour, size, price, brand, material. For every filter combination, Magento generates a unique crawlable URL. A UK fashion retailer with 10 filterable attributes across 100 categories can produce hundreds of thousands of these junk pages. Google crawls them instead of your priority category and product pages, wasting crawl budget and slowing down the indexation of new stock and content updates. The fix is a URL parameter strategy implemented in your Magento configuration — blocking, canonicalising, or noindexing filter URLs based on their SEO value.
How do you handle Magento duplicate content at scale?
Magento generates duplicate content from two main sources: layered navigation filter URLs and the configurable/simple product relationship. For filter URLs, we apply a parameter-by-parameter strategy — block high-volume junk parameters, noindex low-value combinations, canonicalise the remainder to the parent category. For configurable/simple products, we implement canonical tags on simple product URLs pointing to the parent configurable product, remove simple products from the XML sitemap, and apply noindex where simple product pages have no independent commercial search demand.
Does Magento 2 have better SEO than Magento 1?
Magento 2 has significantly better default SEO capabilities — cleaner URL structures, improved canonical handling, better sitemap configuration, and a more performant architecture. Magento 1 reached end-of-life in June 2020 and no longer receives security patches. For UK retailers still operating Magento 1 stores, migration is both a security and SEO priority. The key is managing the migration with a full SEO plan — redirect mapping, content parity audit, and post-launch crawl validation — to preserve rankings built under the old store.
How does GDPR affect Magento SEO tracking in the UK?
GDPR consent management affects GA4 data collection on UK Magento stores because visitors who decline non-essential cookies are not tracked by default GA4 implementations. Depending on your consent rate, this can mean 20–40% of organic traffic and revenue goes unattributed. The solution is GA4 consent mode v2 — which uses Google's modelling to estimate traffic and conversions from users who declined consent — combined with server-side tagging via Google Tag Manager Server Container for accurate first-party data collection. This does not bypass GDPR; it maximises lawful data collection within GDPR constraints.
How long does a Magento SEO audit take?
A Magento SEO audit for a UK store with up to 5,000 SKUs takes 5–7 business days. Catalogues above 10,000 SKUs require 10–14 days. Magento 1 migration audits add 2–3 days for redirect map assessment and content parity analysis. We scope audits accurately upfront.
How much does Magento SEO cost in the UK?
Magento SEO for UK mid-market retailers typically starts from GBP 2,500–4,500 per month as an ongoing retainer, depending on catalogue size and scope. Magento 1 migration remediation projects can be scoped separately as fixed-scope work. The best starting point is a search diagnostic — it identifies exactly what your store needs before any retainer commitment.
How do you approach Magento SEO for post-Brexit product categorisation?
Post-Brexit changes affected UK product classification and customs categorisation in ways that sometimes ripple into ecommerce catalogue structure — particularly for retailers who restructured product categories or added new compliance-related category pages. From an SEO perspective, any catalogue restructure creates URL change and canonical strategy requirements. If your Magento catalogue underwent significant structural changes after Brexit, we assess whether those changes introduced indexation issues — category pages that were restructured without redirect management, or new compliance pages that dilute crawl budget.
Does Magento support product schema for UK rich results?
Magento 2 includes basic Product schema by default, but the implementation is frequently incomplete for UK-specific requirements — particularly GBP pricing with correct currency markup, UK availability status, and review aggregate from UK review platforms. We audit your schema output against Google's Product rich result requirements and implement missing attributes with GBP pricing and UK-specific data.