Magento SEO.A big catalogue, big problems.
Magento is used where the catalogue is serious: tens of thousands of products, several storefronts and complex filters. The mistakes get serious too, because they multiply a thousand times over.
What you get
What gets fixed on Magento.
At this size you work by template and by rule, not page by page. One change hits tens of thousands of URLs.
Layered navigation
Filters on a large catalogue can produce millions of URL combinations.
- Indexing rules per attribute
- Canonicals for filtered views
- Filter combinations that get blocked
- Pagination and view-all pages
- Crawl budget and log file analysis
Several storefronts and languages
Magento often runs several storefronts with the same products, and they compete with each other.
- Hreflang between the storefronts
- Stopping duplicates across storefronts
- URL structure per storefront
- Separate measurement per storefront
- Shared rules, local differences
Speed on a large catalogue
Magento is heavy and needs serious infrastructure. Without caching it chokes.
- Full page caching and Varnish
- Indexes and database optimisation
- Images and static content over a CDN
- Server response time
- Core Web Vitals per page type
Categories and products
You cannot write by hand across tens of thousands of products. It is done by template and by priority.
- Copy for the categories that carry the traffic
- Templates for product descriptions
- Original descriptions for the best sellers
- Product schema with the full set of data
- Discontinued products and where they redirect
How it runs
The order of work on a large catalogue.
-
Month 1
Crawling and log files
Where Google spends its time and what it never gets to at all.
-
Months 1 - 2
Indexing rules
Filters, duplicates and canonicals. The single biggest gain on Magento.
-
Months 2 - 3
Speed
Caching and infrastructure, together with your team or your hosting partner.
-
Month 3+
Content by template
Categories and products, in the order of what they bring in.
Who this is for
Who it works for, and who it does not.
It makes sense if:
- You have a Magento shop with thousands of products
- You run several storefronts or languages on one installation
- Google never gets round to crawling all your pages
It does not make sense if:
- Your catalogue is small - then Magento is too heavy a platform, and that is worth a conversation
- You have access to neither a development team nor a hosting partner
Magento work is almost always done alongside your development team or the partner who maintains the installation. We do not touch production without them.
Frequently asked questions