Laika · strategic & SEO consulting

TECHNOLOGY · MAGENTO / ADOBE COMMERCE

Magento allows almost anything. That's the problem.

Attributes, layered navigation and cache layers give a lot of freedom, and over the years leave a site with more pages than anyone can sustain.

Let's talk about your project
+15
years working visibility for large brands
+200
projects with our own data behind them
48 h
to reply, at most

Brands that have trusted Laika

  • Foot District
  • Cosentino
  • Telepizza
  • Arcos
  • Autocasión
  • ILUNION
  • El Corte Inglés
  • Uno de 50
  • Roberto Verino
  • Don Disfraz
  • Lladró
  • GF Hoteles
  • Racetick
  • Douglas
  • Startupxplore
  • Infoempleo
  • CEF
  • VisionLab
  • cdmon
  • Fronda
  • Tressis
  • Packlink
  • Toys R Us
  • SAP
  • Motocard
  • ¡HOLA!
  • Multiópticas
  • PandaGo
  • ALSA
  • Clínica Menorca
  • Funidelia
  • Regalo Original
  • Médicos Sin Fronteras
  • Maxcolchón
  • Cofares
  • Samsung
  • Logiscenter
  • Decathlon
  • Bijou Brigitte
  • Adolfo Domínguez
  • Kia
  • Foot District
  • Cosentino
  • Telepizza
  • Arcos
  • Autocasión
  • ILUNION
  • El Corte Inglés
  • Uno de 50
  • Roberto Verino
  • Don Disfraz
  • Lladró
  • GF Hoteles
  • Racetick
  • Douglas
  • Startupxplore
  • Infoempleo
  • CEF
  • VisionLab
  • cdmon
  • Fronda
  • Tressis
  • Packlink
  • Toys R Us
  • SAP
  • Motocard
  • ¡HOLA!
  • Multiópticas
  • PandaGo
  • ALSA
  • Clínica Menorca
  • Funidelia
  • Regalo Original
  • Médicos Sin Fronteras
  • Maxcolchón
  • Cofares
  • Samsung
  • Logiscenter
  • Decathlon
  • Bijou Brigitte
  • Adolfo Domínguez
  • Kia

Some of these situations may sound familiar

Layered navigation has created thousands of pages

Attribute combinations that get crawled and receive no visits.

The same product lives in several categories

With different URLs depending on the path you arrive from.

Large pages are slow

Listings with many attributes and a cache layer that doesn't always kick in.

Version upgrades break things

After an upgrade you find lost redirects and templates that stop generating tags.

Several stores share one catalogue

Different languages, currencies and availability on the same product base.

The scope

We review attributes and layered navigation, category structure, URL generation, cache and multi-store configuration, and order the work by impact.

We work on the judgement and the spec: what needs to change on Magento, in which order and how it gets checked afterwards. Your team or your development partner implements it, and we review that what reaches production is what was agreed.

The areas of work

Four fronts that come up again and again on Magento projects. Depending on where your project stands, some weigh more than others.

Layered navigation

Decide which combinations exist for search engines and close the rest.

See the detail
  • Inventory of attributes used in navigation
  • Indexing rules per combination
  • Canonicals, parameters and pagination
  • Crawl analysis before and after

Categories and product URLs

One address per product and a category structure that makes search sense.

See the detail
  • Review of product routes and nested categories
  • Accumulated rewrites and old redirects
  • Target structure and change plan
  • Internal linking between category and product

Cache and performance

Make critical templates respond fast against real user data.

See the detail
  • Measurement per template type
  • Review of full-page and block cache
  • Weight of images, scripts and extensions
  • Priorities by revenue impact

Releases and upgrades

Keep an upgrade from wiping out what already worked.

See the detail
  • Pre-release checklist
  • Review in staging
  • Redirect and tag checks after going live
  • Indexing watch in the following weeks

Who does it?

A small team with real hours inside Magento. MJ leads the strategy and the specialist who reviews your platform is the one who explains it to you.

Why Laika?

Knowing the platform changes the conversation: you stop arguing about whether something is possible and start deciding when it ships.

We've worked on Magento projects long enough to know where its real limits are and what a second pass at configuration can solve.

  • We tell the urgent from the eye-catching

    On Magento the list of findings is always long. The value is in deciding where to start.

  • You always talk to whoever decides

    There's no management layer between you and the judgement. MJ leads the strategy and the specialist team executes.

  • If we're not the right fit, we say so

    Even if that means there's no project for us, we'd rather say so before signing.

Frequently asked questions

Do you work with Adobe Commerce and Magento Open Source?

With both. What changes is the configuration margin and who deploys.

Do we need to change platform?

Almost never for visibility reasons. If it were needed, we'd say so with the reasons.

Can you support a version upgrade?

Yes, and it's the best moment to tidy up what's been dragging on for years.

Tell us about your project

Knowing which version you run, who develops it and what worries you is enough for us to say whether it makes sense to talk.

Tell us like you'd tell a colleague: no jargon needed.

We only use this to reply to you.

Shall we talk about your platform?

We look at your project before proposing anything and tell you what can move without fighting the roadmap.

Let's talk about your project