Hiring a Magento SEO expert: name your edition first, then test for the three Magento jobs
Why Magento Open Source, Adobe Commerce and Adobe Commerce as a Cloud Service need different SEO skills, and the interview questions that show who has done the work.
Published by AI Knows Us · Updated 21 October 2026
The right Magento SEO expert depends first on which Magento you run, because Adobe now documents SEO in two different places. If your store is Magento Open Source, or Adobe Commerce on cloud infrastructure or on-premises, SEO is configured in the Admin: metadata, URL rewrites, canonical tags, robots and the XML sitemap. If your store is Adobe Commerce as a Cloud Service with the Edge Delivery Services storefront, Adobe sends you to separate storefront documentation, and the work is closer to front-end engineering. Name your edition, then hire someone who can show work on that edition, test them on three Magento-specific jobs, and start with a fixed-price audit.
Step one: name your edition
Adobe's own SEO overview for Commerce, last updated 8 October 2026 and read on 21 October 2026, marks its metadata, sitemap and URL rewrite sections "PaaS only", meaning Adobe Commerce on cloud projects and on-premises projects. It then adds a tip: "For Adobe Commerce as a Cloud Service, see the SEO guidelines in the Commerce Storefront documentation." So there are, in practice, two Magento SEO jobs:
| Your setup | Where SEO is controlled | The skills that matter |
|---|---|---|
| Magento Open Source, or Adobe Commerce on cloud (PaaS) or on-premises, with a Luma-based or custom theme | The Admin (Stores, Configuration and Content, Design, Configuration), plus theme templates | Admin configuration, URL rewrite tables, layered navigation, theme performance, cron and indexers |
| Adobe Commerce as a Cloud Service with the Edge Delivery Services storefront | The storefront code, CDN configuration and the Commerce Storefront guides | Front-end and CDN work: URL formats, canonical signals, metadata in first-load HTML, sitemaps |
An expert who has only worked on the first kind can still be the wrong hire for the second, and the reverse. Ask which they have shipped.
The three jobs that separate a Magento specialist
1. Duplicate URLs and canonical tags
Magento can produce several URLs for one product. Adobe's metadata guide gives the classic case: if the catalogue is set to include the category path in product URLs, the store generates multiple URLs for the same product, and the canonical meta tag tells search engines which one to index. On the Edge Delivery storefront, Adobe's indexing guide adds two rules worth testing a candidate on: set the canonical of a configurable product to the parent product, or "Google may index child product URLs instead," and make sure canonical URLs "do not point to redirects (301)." A specialist answers these from experience. A generalist answers with theory.
2. Layered navigation and crawl control
Filters by size, colour and price can multiply category URLs into the thousands. The specialist decides which filter combinations deserve an indexable page, keeps the rest out of the index, and sets robots instructions to match. Adobe documents robots settings under Content, Design, Configuration, with a default robots.txt that already disallows paths such as /checkout/, /customer/ and session ID parameters. Ask the candidate what they would add for your filters, and why.
3. Metadata at catalogue scale
A store with thousands of products cannot be written by hand on day one. Adobe's guide says the meta title should be unique and "fewer than 70 characters," and a meta description ideally 150 to 160 characters, though the field accepts up to 255. It also notes that schema.org structured data is added to the product template by default. A good expert sets sensible patterns for the long tail, then rewrites titles and descriptions by hand for the categories and products that carry revenue.
The configuration details behind these three jobs, setting by setting, are in our guide to Magento 2 SEO. Read it before the interview and you will hear quickly who knows the platform.
Storefront facts to test on the Edge Delivery side
If you are on Adobe Commerce as a Cloud Service, Adobe's storefront indexing guide gives the default product page URL as /products/{urlKey}/{sku}, where the URL key carries the product name and the SKU is needed for Catalog Service queries. It says the format can be changed, but changes "require CDN configuration," and that the boilerplate forces SKUs in URLs to lowercase. A candidate for this kind of store should be comfortable with that stack, and should plan URL changes together with your developers rather than alone in the Admin.
Interview questions that work
- "Which edition and storefront have you optimised, and can I see one?" Ask for a live store and the before and after Search Console data.
- "How would you handle our layered navigation?" Listen for a rule for which filters get indexed.
- "What happens to our URLs if a merchandiser renames a product?" They should talk about URL keys and permanent redirects.
- "How do you check that cron and the sitemap job are running?" On a self-managed store the sitemap regenerates through cron, so a stopped cron job means a stale sitemap.
- "What will you need from our developers?" Theme, CDN and storefront changes need a developer. An expert who never needs one is not touching the code.
- "What would you leave alone?" Good experts protect what already ranks.
Access, scope and how the work is priced
Google's "Do you need an SEO?" guide advises giving an SEO only read access to Search Console during an audit. Do the same with the Admin: a role limited to the areas they need, on a staging environment for changes, and removed when the work ends.
Magento SEO is usually sold as a fixed-price technical audit, a project to apply its findings, and an optional monthly retainer for content and links. Ask for the audit as a ranked list with the expected impact and the effort for each item, and price the fixes separately. If the work overlaps with platform development, our checklist for choosing a Magento development agency covers the questions for that side. If you are moving between editions or off Magento altogether, treat it as a migration and read our comparison of SEO migration services before anyone touches the URLs.
And if anyone promises a top position on Google, the guide's advice fits in three words: "find someone else."
Questions about hiring a Magento SEO expert
Is Magento SEO different from general ecommerce SEO?
The goals are the same. The work is different, because Magento's URL rewrites, layered navigation, store views and indexers create problems other platforms do not, and the settings live in specific places in the Admin.
Do I need a developer as well as an SEO expert?
Usually yes, for theme, performance and storefront changes. Some experts are also developers. If yours is not, agree up front who writes and deploys the code.
Is Adobe Commerce SEO the same as Magento SEO?
For Adobe Commerce on cloud infrastructure or on-premises, SEO is set in the Admin, as on a self-managed Magento store. For Adobe Commerce as a Cloud Service, Adobe points to separate storefront SEO guidance.
What should a Magento SEO audit include?
Canonical and duplicate URL checks, layered navigation and crawl rules, robots and sitemap status, metadata coverage, structured data, speed on key templates, and redirects. Each finding should name where to fix it.
How many store views can one expert handle?
That depends on languages and markets more than on Magento. Ask how they handle hreflang and duplicate content between store views before you agree the scope.
What a buyer's assistant says about your catalogue
Magento stores tend to sell considered purchases, and those shoppers increasingly ask ChatGPT or Gemini which brand or retailer to trust before they search. The answer names a few stores, built from pages and reviews the assistant can read. A Magento SEO expert works on your Google rankings. Whether those assistants name your store is a separate question, and it is the one AI Knows Us measures.