Leroy Merlin Brasil: enterprise organic growth at catalog scale
At Leroy Merlin Brasil I worked on organic growth where category architecture, rendering, indexing, seasonality, and analytics all met. The traffic moved from about five million to about eighteen million monthly organic visits during the tenure, a site-level outcome the whole function shared.
Leroy Merlin Brasil sells a large ecommerce catalog. Category architecture, how pages render, what gets indexed, seasonal demand, and the tracking behind it all interact, and every fix touches more than one team.
I joined when the SEO team had two people. It grew to five SEO specialists plus adjacent analytics work while I was there. The record below states the site-level outcome and then the specific scope I owned, because the two should not be confused.
The scale is the point. This is where I learned to turn search demand, measurement, and technical structure into a page architecture a large catalog can actually run on.
The problem
A large catalog where the same product could be reached through several page types with competing structure.
Category and department pages were not organized around how people actually searched.
Rendering and indexing gaps meant important pages were not reliably discoverable.
Tracking and the data layer were incomplete, so optimization had weak measurement.
Seasonal demand swung hard, so prioritization had to move with the calendar.
The marketplace SEO pilot needed agreement from teams well outside SEO.
System map
SurfaceComposed modules
Hotels
Search
Result
Hotel detail
Booking
Packages
Build
Price
Package detail
Checkout
Transfers
Route
Options
Schedule
Confirmation
Tours and tickets
Catalog
Availability
Purchase
Confirmation
CONCEPTUAL VIEW / PUBLIC SCOPE
Constraints
The traffic number is a company and site outcome, not one person's result, so the record describes my scope precisely and stops there.
Fixes crossed engineering, content, analytics, and category teams.
The marketplace pilot covered hundreds of thousands of products in its first year.
There were no direct reports, so progress depended on influence and clear technical argument.
What I built
Ownership of 13 large departments, with their category and department page structure.
Technical optimization across rendering and indexing so important pages could be found and crawled.
A tracking and data-layer model, so organic work had a measurement base.
Structured data across the catalog to describe products and pages to search engines.
Programmatic SEO work so large product and category sets could be structured at scale.
Category and department content strategy tied to search demand rather than to internal naming.
A marketplace SEO pilot, presented to national and global directors, that covered hundreds of thousands of products in year one.
Growth of the team from two people to five SEO specialists, with adjacent analytics work added.
Decisions and trade-offs
01
Prioritize by demand and seasonality instead of by team convenience
What it cost: Harder sequencing across teams, and work that matched when people were actually searching.
02
Build the tracking and data layer before scaling optimization
What it cost: A slower start, and decisions that could be defended with numbers from then on.
03
Use programmatic structure where the catalog is too large for hand-built pages
What it cost: Templates and rules to govern, in exchange for coverage no manual process would reach.
04
Argue the pilot on shared outcomes rather than SEO metrics
What it cost: More time in rooms with other teams, and a pilot that had support beyond the SEO function.
Outcome
Monthly organic visits grew from about five million to about eighteen million during the tenure, a site-level result shared by the whole function. The marketplace SEO pilot went from a proposal to a program presented to national and global directors, covering hundreds of thousands of products in its first year. After the tenure, the top-3, top-10, and top-20 ranked-term volumes were not matched again. My contribution sits in the scope above: the departments, the page architecture, the tracking model, the structured data, and the pilot.
5M to 18Mmonthly organic visits across the tenure, site-level
13large departments owned
2 to 5SEO specialists, plus adjacent analytics
Hundreds of thousandsproducts in the marketplace pilot in year one
Stack
Google Analytics and GA4, Google Search Console, Looker Studio, and SEMrush reporting.
Structured data, sitemaps, rendering and indexing work on a large ecommerce platform.
A tracking and data-layer model feeding analytics and reporting.
Programmatic page templates for category and product coverage.
What I would do next
Document the department page architecture as a reusable playbook for large catalogs.
Rebuild the marketplace pilot numbers as a public case with its own method.
Apply the same demand and measurement logic to smaller catalogs where it moves faster.