Magento SEO Services for Large Ecommerce Catalogues

Layered navigation in Magento generates a URL for every combination of filter selections. For a catalogue with 10 filters and 5 options each, this can generate millions of URLs. The correct approach combines: (1) canonical tags on filtered pages pointing to the unfiltered category URL; (2) robots noindex on low-value filter combinations; (3) robots.txt rules to stop crawlers spending time on low-value filter combinations; and (4) selective indexation of commercially valuable filtered pages (e.g., /women/tops/colour-red/ if it has sufficient search volume). Google retired Search Console's URL Parameters tool in 2022, so these controls have to be set on your own site. We map this out per store before implementing. For a broader walkthrough, see our guide to optimising a Magento store for SEO.

Yes significantly. Magento 2 has native URL rewrites, improved canonical tag handling, better XML sitemap generation, and cleaner URL structures than Magento 1. However, Magento 2 still has the layered navigation problem, can generate duplicate content from category/product URL combinations, and requires proper configuration to achieve optimal SEO performance. Magento 1 reached end of life in June 2020, so if you are still on it, migrating to Magento 2 or Adobe Commerce is a strong SEO recommendation - along with a comprehensive redirect mapping exercise.

Yes. Magento product schema (Product, Offer and, where you have genuine reviews, AggregateRating) supports both organic rich snippets and Google Shopping feed quality. We implement structured data that enhances your organic listings while aligning with Google Merchant Centre feed requirements - giving your products a presence in both Shopping ads and organic results. See also our Google Shopping management service.

Magento speed improvements follow a priority order: (1) Enable full-page cache and Varnish; (2) Configure a CDN (Adobe Commerce on Cloud uses Fastly; Open Source stores often use Cloudflare or a similar CDN); (3) Compress and convert images to WebP; (4) Enable JS/CSS bundling and minification; (5) Defer non-critical third-party scripts; (6) Address render-blocking resources in the theme. We use PageSpeed Insights and Chrome DevTools to identify your specific bottlenecks before implementing changes.

Yes. Magento multi-store setups - multiple websites, stores, and store views - require careful hreflang implementation, separate GSC properties for each domain or subdomain, and store-view-level canonical tag configuration. We handle international Magento multi-store SEO, including currency and language variations.

Adobe Commerce (formerly Magento Commerce) adds commercial features and a managed cloud option, and Adobe Commerce on Cloud uses Fastly as its CDN. Magento Open Source is self-hosted, so you typically choose your own hosting, CDN and search engine (Elasticsearch or OpenSearch). Each setup affects Core Web Vitals, crawlability and rendering differently, so our audit covers the specific version and hosting you run and adjusts recommendations accordingly.

Technical fixes on Magento stores typically show crawl and indexation improvements within 3 to 6 weeks. Keyword ranking improvements for existing pages usually appear within 8 to 16 weeks following on-page optimisation. Large catalogues take longer because Googlebot needs time to re-crawl and re-index pages after changes. These are typical ranges, not guarantees. We track GSC crawl stats weekly post-implementation so you can see progress building from the first month.