magentoseo.agency · INTSEO Media
A Magento SEO Agency for Stores Where the Platform Is Fighting Your Rankings
We are a Magento SEO agency for Magento Open Source and Adobe Commerce catalogues that lose crawl budget to filter URLs, ship slow themes, and watch migrations erase equity. Platform-specific Magento SEO services, not generic ecommerce advice with the word Magento pasted in.
Editions
Magento Open Source & Adobe Commerce
Catalogue scale
Hundreds to hundreds of thousands of SKUs
Themes & stacks
Hyva, Luma, PWA Studio, headless
Engagement
Audit, tickets, ship with your Magento devs
Why Magento stores underperform in search
Most Magento ranking problems are configuration and architecture. Missing blog posts are rarely the root cause.
Magento SEO is the practice of improving organic search performance for stores built on Magento or Adobe Commerce by fixing how the platform creates URLs, decides indexation, caches pages, and renders category and product templates. That definition matters because buyers keep hiring generalist teams who never open URL rewrite rules or layered navigation settings.
Filter URLs multiply quietly. A few attributes on a large catalogue can generate thousands of crawlable combinations. Google will fetch them unless you control robots, canonicals, and which facets deserve a public URL. Meanwhile default canonical behaviour around category paths and product URLs creates soft duplicates that dilute signals.
Themes add a second tax. Luma-era stacks and script-heavy storefronts push LCP and INP past what commercial pages can afford. Full page cache and Varnish help only when they are actually warm and correctly varied. Migrations drop traffic when redirect maps and sitemaps are treated as go-live leftovers. Out-of-stock products stay indexable and pad the index with pages that convert poorly. None of that is fixed by another keyword spreadsheet.
Magento SEO services as one programme
Six workstreams that share one crawl, one backlog, and one verification loop. Pick a starting point; we keep the rest aligned.
Where Magento breaks in search
A practical symptom table Magento merchants and developers can use before buying another plugin.
| Symptom | Magento-specific cause | Where to confirm | Typical fix |
|---|---|---|---|
| Thousands of near-duplicate filter URLs in the index | Layered navigation builds combinations of colour, size, price, and attribute filters as crawlable URLs | Site crawl, GSC page indexing, server logs | Facet allowlist, robots/meta robots rules, canonical policy, parameter handling |
| Out-of-stock PDPs bloating the index | Default visibility leaves unavailable SKUs indexable with thin or confusing offers | Catalogue export vs indexed URL sample | Stock-aware indexation rules, noindex or redirect policy for true discontinuations |
| Poor LCP on category and product templates | Heavy Luma/JS stacks, cold full page cache, oversized hero and PLP images | CrUX / PageSpeed on PLP and PDP URLs | Cache warm strategy, image pipeline, theme/JS reduction (often Hyva migration) |
| Duplicate titles and thin categories | Auto-generated meta, empty category CMS blocks, pagination without clear primary URL | Crawl of category tree + SERP sampling | Category content pattern, internal links, pagination and canonical rules |
| Store-view duplicates and language mix-ups | Multi-store URLs without aligned canonicals and hreflang | GSC international targeting + URL inspection | Store-view URL strategy, self-canonicals, reciprocal hreflang |
| Traffic drop after migration or replatform | Incomplete redirect map, sitemap gaps, canonicals pointing at staging patterns | Pre/post launch crawl diff + GSC coverage | Phase-based migration SEO: staging, launch redirects, post-launch verification |
If you are comparing Magento SEO companies, ask how they would complete this table for your store. Magento SEO experts who have lived with indexer queues and layered navigation will answer in platform terms. Generalists will talk about content calendars while your crawl budget bleeds into filter combinations.
As an ecommerce SEO agency for Magento, we treat this table as the start of the backlog. Magento 2 SEO services only work when the crawlable URL set matches the pages that earn revenue.
User-agent: *
Disallow: /*?dir=
Disallow: /*?order=
Disallow: /*?limit=
# Pair with meta robots / canonical rules for attribute filters.
# Do not block CSS/JS required for rendering.Editions, themes, and stacks we work with
We work across Magento Open Source and Adobe Commerce, including multi-store and multi-website setups with store views that need hreflang discipline. Catalogue scale ranges from a few hundred SKUs to large catalogues where Elasticsearch or OpenSearch, indexer throughput, and sitemap splits decide whether Google sees a clean tree or a mess.
Theme and frontend reality matters as much as admin config. Hyva storefronts usually give Core Web Vitals a fair fight. Luma can still rank when cache, images, and JS are controlled, but it starts behind. PWA Studio and other headless GraphQL setups add rendering and URL ownership questions that classic Luma playbooks ignore.
- Magento Open Source / Adobe Commerce
- Hyva · Luma · PWA Studio · headless
- Full page cache · Varnish · CDN edge rules
- Layered navigation · URL rewrites · URL keys
- Category & product sitemaps · robots.txt
- Product, Offer, BreadcrumbList structured data
How a Magento technical SEO agency actually works
Implementation support is the differentiator. Findings without a path into your Magento sprint board are theatre.
Step 1
Access and baseline
Admin (or guided access), Search Console, analytics, staging, and ideally logs. We establish how Magento is configured today: URL rewrites, canonical settings, sitemap generation, cache, and store views.
Step 2
Crawl and log analysis
We crawl the storefront and sample how Googlebot actually spends budget. Filter URL explosions and soft 404 patterns show up fast on large Magento catalogues.
Step 3
Prioritised findings
Each issue is scored by organic revenue impact and Magento dev effort. You get a register your team can sequence into sprints, not a unsorted dump of warnings.
Step 4
Ticket-ready specs
Recommendations name Magento surfaces: robots.txt, meta robots, canonical config, layered navigation rules, layout XML or theme templates, redirect maps. Developers should not have to reverse-engineer intent.
Step 5
Ship with your Magento team
We work through tickets alongside your developers or agency. The fix is often known in a week and shipped in a quarter because it sits behind release freezes and indexer-sensitive deploys. We plan for that reality.
Step 6
Verify after deploy
After release we re-crawl, check indexation samples, confirm Core Web Vitals on key templates, and watch Search Console for coverage regressions. Unverified advice is unfinished work.
Rough timing: discovery and audit in the first weeks, then a living roadmap. Shipping speed depends on your Magento release train. Read the fuller model on how we work, including reporting tied to organic revenue rather than vanity sessions.
What we will not do
These refusals exist because they waste Magento budgets.
No 90-page audit PDFs without prioritisation
Magento teams need ranked tickets with impact and effort. A wall of warnings sitting in SharePoint does not change robots or canonicals.
No “install this extension” as a strategy
Extensions can support templates. They do not replace crawl control, cache strategy, or honest out-of-stock handling.
No recommendations we cannot explain to a Magento developer
If we cannot point at admin config, layout, or a redirect row, it is not ready. Platform work must be implementable.
No blaming content while ignoring theme and cache
A slow PLP with INP issues will keep losing. We will say when performance is the constraint before asking for more copy.
No ranking guarantees
Competitors ship too. Magento release delays happen. We commit to diagnosis, prioritisation, and verification, not fantasy positions.
No work we cannot verify after deploy
If staging is unavailable and production changes are invisible, we stop and reset access. Unchecked changes create new duplicates.
Questions Magento merchants and dev leads actually ask
Do we need to replatform off Magento to rank again?
Usually no. Most Magento SEO failures come from filter URL control, canonical and indexation settings, theme and cache performance, thin category templates, or a messy migration, not from Magento as a platform. Replatforming is a separate business decision. If the catalogue, ERP integrations, and B2B workflows still fit Magento or Adobe Commerce, fixing architecture and configuration is almost always cheaper than a rebuild.
Can you work in our repo and staging environment?
Yes, when your team grants access. We prefer staging with a recent catalogue snapshot, admin access (or a recorded walkthrough), Google Search Console, and ideally server or CDN logs. We write ticket-ready specs your Magento developers can ship in their release cycle. We do not need production admin for every engagement, but we do need a way to verify what actually deployed.
Will installing another Magento SEO extension fix this?
Rarely on its own. Extensions can help with meta templates, schema scaffolding, and some admin convenience. They do not replace a filter URL policy, a correct canonical strategy, or a theme that ships too much JavaScript. If the root issue is layered navigation multiplying indexable URLs, another extension that rewrites titles will not stop the crawl waste.
Why is our Magento store so slow in Core Web Vitals?
On Magento, slow LCP and INP usually trace to theme weight (especially Luma-era stacks), uncached or poorly warmed full page cache, oversized images, third-party scripts, and heavy PLP/PDP templates. Keyword work will not fix a 4 second LCP. We start with field data, then theme, cache, and asset delivery before arguing about content length.
How long does Magento SEO take for a 50,000-product catalogue?
Expect the audit and prioritised roadmap in weeks, then months of shipped fixes because indexation, redirects, and template changes sit behind Magento release cycles and a busy dev team. Large catalogues also need careful crawl control so Google spends budget on money pages. We set expectations around implementation capacity, not fantasy timelines.
Do you touch code or only send a spreadsheet?
We deliver a prioritised findings register, ticket-ready specs, and verification after deploy. Some clients want us in the repo reviewing pull requests; others keep us advisory while their agency ships. Either way, we refuse the 90-page PDF that nobody can prioritise. If a recommendation cannot be explained to a Magento developer, it does not ship from us.
How do you report, and what do you measure?
We report on organic revenue and converting landing pages where tracking allows, plus index coverage, crawl waste signals, Core Web Vitals on key templates, and ranking movement on commercial category and product intent. Vanity traffic without revenue context is not the goal. Google Search Console, GA4, and crawl or log tools are the usual stack.
How does scoping and quoting work?
There is no public price list. You share the store URL, edition, catalogue scale, theme, and constraints. We scope an audit and programme shape, then send a custom quote. Cost questions go through that process because a 2,000-SKU Hyva store and a 120,000-SKU multi-website Adobe Commerce build are not the same engagement.
How do you think about AI Overviews for Magento ecommerce?
Product and category queries still earn organic clicks when the page matches intent, shows stock and offer clarity, and loads well. Informational queries lose more clicks to AI answers. We build category and product templates that are clear enough to cite, keep structured data honest, and treat generative visibility as a complement to classic rankings, not a replacement for crawl hygiene.
If you need an Adobe Commerce SEO agency for multi-website governance, or Magento SEO experts for a Hyva rebuild mid-programme, start with the audit. Secondary work such as content briefs or link prospects only joins once crawl and indexation stop wasting equity. That sequencing is how a Magento SEO agency protects budget on large catalogues.
That is how a Magento SEO company should sequence work in 2026: stabilise the platform signals, then grow category and product demand capture. Screaming Frog, JetOctopus, Ahrefs or Semrush, log file analysis, and Search Console all show up in the process when they earn their place.
Tell us what Magento is doing to your rankings
Share the store URL, edition, and the symptom you see (filter bloat, slow CWV, migration risk, thin categories). We reply within one business day. No public pricing: scoping produces a custom quote. Prefer email? Write to fabi@site-media.co.uk.
Or browse the Magento SEO blog for long-form notes your developers can use immediately.