Magento Open Source Adobe Commerce Storefront design & front-end Independent · not affiliated with Adobe
Magento Themes Store Storefront Lab
Published 13 Nov 2026 11 min read

Buying Magento SEO services: what you are paying for, and what you are not

A useful Magento SEO proposal should expose the technical decisions, named deliverables, responsible people and evidence required before anyone signs a retainer.

One retainer, three different jobs

“Magento SEO services” can cover technical implementation, editorial work and link acquisition. Agencies often present these as one service, with one report and one monthly invoice. That can work, but only if the proposal makes the boundaries clear.

The distinction matters because each job requires different evidence. A URL rewrite can be configured and tested in the store. A product description requires a subject-matter brief and editorial judgement. A link requires research, outreach and an editorial decision by the publisher.

It also matters because most Magento problems labelled “SEO” are structural implementation problems. Content and links may improve the result, but neither repairs a catalogue that exposes duplicate URLs, treats filter combinations as indexable pages or sends contradictory canonical signals.

A competent agency should be able to explain which part of the proposal is Magento-specific and which is ordinary search optimisation that it would perform for any sizeable catalogue.

What a Magento SEO retainer may include

Type of work What it includes What is Magento-specific
Structural work URL design, canonical rules, handling filters and pagination, redirects, store-view consistency, internal-link architecture and implementation testing. Most of the work. The agency must understand Magento URL rewrites, catalogue entities, category trees, store and website scopes, configurable products and the behaviour of generated URLs.
Content work Category copy, product copy, editorial briefs, content refreshes, duplication control and page-level recommendations. Little of the process. The Magento-specific part is choosing the correct content type, template, category scope and internal-link destination.
Link work Digital PR, editorial outreach, link reclamation, relevant resource development and analysis of referring links. Limited. Internal links must respect the catalogue and store hierarchy; external links are not “configured” in Magento.

If the proposal calls all three “technical SEO”, ask for a breakdown. A technical template cannot create useful category copy, and an editorial plan cannot determine what should happen to a faceted URL.

1. Structural Magento work

This is the part that requires platform knowledge rather than a general SEO checklist. It includes decisions about how the catalogue is represented to crawlers and how those decisions survive changes to products, categories and store configuration.

Typical work may include reviewing the URL rewrite table, separating category and product routes, preserving valuable legacy URLs through redirects, defining canonical behaviour for duplicate pages and resolving conflicts between store views.

Layered navigation deserves particular attention. Filters can generate many URLs from the same category. Some faceted combinations have genuine search demand; many do not. The correct treatment depends on the catalogue, the search strategy and the way competitors represent the same products.

There is no universal answer to “index the filters” or “noindex the filters”. A proposal should explain the rule it recommends, which URLs it covers, how it will avoid conflicts with pagination and how it will be implemented in Magento rather than merely described in a report.

Store views introduce another boundary. The same product may have different names, descriptions, URLs or availability in different stores. The agency should say whether the task is to consolidate those URLs, distinguish them with canonical and hreflang signals, or correct the underlying scope configuration.

Generic technical work still matters: crawl paths, rendered output, redirects, broken links, response codes, metadata and sitemap accuracy. The question is whether the agency understands how Magento produces those signals. A platform-specific diagnosis without broader technical checks is incomplete; generic checks without Magento configuration knowledge are merely preliminary.

2. Content work

Content is mostly ordinary SEO work. Any competent agency can assess whether category descriptions match intent, whether product copy is useful and whether important pages deserve an editorial refresh.

The Magento-specific decision is placement. A rewritten guide may need a CMS page, a native category description or a landing page attached to a particular category. A product description may have to work across several store views, while a category description may need to be conditional because the products change.

Ask who provides the subject-matter information. An agency cannot infer the material differences between product ranges from a crawler export. If the catalogue contains regulated claims, technical specifications or complex compatibility information, content production requires inputs from the merchant.

Also establish whether copy is written, edited or templated. A description generated from a handful of fields may remove duplication at scale but can still produce thin or misleading pages. The proposal should identify the inputs, approval route and review method rather than promising “optimised content” without defining it.

3. Link work

Link acquisition is also ordinary SEO. It may include reclaiming displaced editorial links, producing research that publishers can cite, identifying relevant coverage and conducting outreach.

The agency should state what it considers a link opportunity, who makes the contact and what the merchant can reasonably supply. A large product catalogue is not a public-relations campaign by itself. Relevant data, expertise, case material or access to specialists may be necessary.

Internal linking can involve Magento structures, breadcrumbs, navigation and editorial links within page content. External links cannot be inserted by changing a store configuration. Any proposal implying otherwise is confusing product and outreach work.

A useful proposal separates leading indicators from outcomes. Publishing a relevant resource, contacting a defined set of publications or identifying a broken link is a deliverable. “Improve authority” is not.

What the proposal must contain

A named audit of this store

The audit should describe the current Magento store, not reproduce a universal checklist. It should name the affected store views, URL patterns, templates and catalogue examples that contain the problem.

A credible audit record includes the URL examined, the observed behaviour, the likely cause, the intended change and the method for checking it. It should also distinguish confirmed issues from questions that require access to the store, server, analytics or deployment process.

“We will conduct a full technical SEO audit” is a work description. “Filter combinations under two specific category paths are indexable and return canonical tags to the parent category” is an auditable finding.

The Magento settings they intend to change

The proposal should identify the exact configuration layer involved. Depending on the finding, that might be a URL rewrite rule, category URL settings, canonical implementation, redirect, robots directive, metadata template, store scope or a customisation.

“Improve canonicalisation” does not say who will implement it, where the logic will live or what happens when a future catalogue change alters the URL. The more consequential the change, the more detail is needed.

Where the implementation requires a module or code change, ask for the maintenance obligation. A useful configuration may be replaced during an upgrade. A custom extension may need revision. An extension that modifies canonical output can conflict with another extension that changes the same template.

Who makes the changes, and where

Name the roles: Magento developer, SEO consultant, editor, copywriter, link acquisition specialist, merchant reviewer or the merchant’s internal team. A proposal that assigns no responsibility leaves the handoff unpriced and unowned.

State where changes will be made. Implementation should normally be reviewed outside production, then deployed through the merchant’s release process. The proposal should explain how staging data, third-party extensions, payment functions and other catalogue behaviour will be protected.

For work performed directly in production, ask what change control, rollback and approval steps apply. Editing a live category or redirect can affect navigation, cached pages and analytics. Convenience for the agency is not a sufficient reason to bypass the store’s release controls.

How the result will be measured

Measurement should connect each change to an observable outcome. A technical change might be verified through URL inspection, server responses, rendered output and crawl data. Content performance might be assessed through indexed pages, engagement with the intended result and assisted conversions.

Link work should be judged through referring pages, relevance, destination quality and referral traffic rather than a raw link total. The proposal should also state which baselines will be recorded, because later comparison needs a starting point.

Avoid promises tied to rankings for a broad set of commercial terms. Search results vary by device, location and personalisation, while the catalogue and competitors also change. A sensible proposal defines leading outputs, reporting intervals and the merchant’s business measures without pretending that an agency controls the final result.

Questions that expose Magento competence

Ask for an explanation, not a yes-or-no answer. The agency should be prepared to discuss configuration and consequences.

  • How will you inspect and change the URL rewrite table? Which entries will you preserve, remove or add, and how will you prevent a rewrite conflicting with a category or product URL?
  • What happens to filter URLs? Which parameters will generate crawlable routes, which will be blocked or canonicalised, and how will you handle combinations that have search demand?
  • How will you prevent pagination from creating duplicate or conflicting URLs? Which pages should be discovered, and how will canonical rules interact with them?
  • How do store views affect URLs and canonical signals? Which store scopes does the recommendation cover?
  • Which extension or template emits the current canonical tag? Will the proposed change replace that behaviour or add to it?
  • How will you test without taking the catalogue down? What staging data will be used, which journeys will be tested, and what is the rollback path?
  • Which Magento version is the store running? The current general release is 2.4.9, and the proposal should be valid for the merchant’s actual version rather than a generic platform description.

The answers should be concrete enough to test. An agency that knows only that Magento has “URL rewrites” may still make unsafe assumptions. An agency that understands how generated URLs, custom routes, filters and canonical output interact is likely to find causes rather than rearrange labels.

Ask which parts are standard SEO. A Magento specialist should not imply that content research, editorial standards or external link acquisition are exclusive capabilities. The platform knowledge should be concentrated where it changes the diagnosis or implementation.

Warning signs in the proposal

A fixed monthly retainer is not automatically wrong. It becomes weak when the proposal contains no named deliverables, no owner and no evidence of progress. “Continuous SEO” needs a monthly sequence of audits, fixes, publications, outreach and reviews if it is to be comparable with project work.

Guaranteed rankings are a decisive warning sign. No agency can honestly guarantee a position for a commercial query in a changing search environment. A guarantee also confuses rankings with business outcomes: traffic can rise without a higher position for one term, and a position can improve without producing profitable demand.

Direct production work without a stated change process is another warning. It may conceal limited staging access, but it should never become the default merely because the agency can complete the task faster.

A proposal that omits the store’s current version has not begun with the facts. Magento behaviour, extension compatibility and deployment practices vary across releases. If the agency cannot name the version, store scope or key extensions, its advice may be based on assumptions.

Be cautious with reports that contain percentages, coloured charts and no prioritised issues. Volume can demonstrate activity, but it does not show whether the work addresses a blocked category, a duplicated template or a commercial page with no internal links.

Be equally cautious with undefined deliverables such as “authority building”, “content optimisation” or “technical improvements”. Translate each into an artefact, an owner, an acceptance test and a place in the release process.

Check the structural half before paying

A merchant can check much of the structural diagnosis without buying a retainer. This does not replace an experienced implementation, but it does establish the store’s baseline before quotations begin.

Start with a URL inventory across the relevant store views. Include category, product, search, filter, pagination and content URLs. Record redirects and rewrite rules, then compare the visible links, sitemap entries and canonical output.

Look for several specific faults. Check whether the same product or category appears under multiple URLs; whether faceted routes have an intentional indexability rule; whether pagination points back to the correct page; whether store views overlap unintentionally; and whether legacy URLs redirect once rather than through a chain.

Then inspect the catalogue, not just the rendered pages. Magento’s URL rewrite table may contain custom routes and historical entries that influence the visible address. A crawler sees the final URL, while the store configuration reveals why it exists.

Record each issue in a simple register: current URL, affected scope, observed signal, expected behaviour, likely implementation point, owner and acceptance test. This creates a document against which agency quotes can be compared.

It also makes the proposals cheaper and more comparable. Agencies no longer need to sell a preliminary diagnosis as part of an ambiguous retainer, and quotations can be compared against the same named problems rather than different interpretations of “SEO”.

Content and link acquisition cannot be fully settled from a crawl. Their proposals should still specify the evidence, editorial inputs, publication standard and campaign scope. Structural checking narrows the technical brief; it does not turn an undefined agency retainer into a sound contract.

Questions this page answers

What does Magento SEO services cover?
Technical implementation, editorial work and link acquisition. Agencies should explain which parts are Magento-specific.
Why should a Magento SEO proposal separate structural, content and link work?
Each job requires different evidence and may need different roles. Combining them under technical SEO without a breakdown obscures responsibility and delivery.
What should a named audit of a Magento store include?
It should name affected store views, URL patterns, templates and catalogue examples. A credible record includes URL, observed behaviour, likely cause, intended change and checking method.
What should a Magento SEO proposal say about implementation?
Name the roles responsible, exact configuration layer and where changes will be made. Explain staging protection, change control, rollback, approval and maintenance for code or modules.

More in Magento SEO

Editorial & corrections: [email protected]