Skip to content
XpandShow Me What To Fix First
Where ecommerce SEO revenue actually comes from
  • Category / collection pagesPriority
    high-intent discovery surface
  • Product detail pages (PDPs)Scale
    large indexable catalogue surface
  • Buying guidesAssist
    research and internal-link support
  • Homepage + brand queriesBrand
    branded and navigational demand
Most agencies pour effort into PDPs. The leverage is one tier up the architecture.
Ecommerce SEO

Most ecommerce SEO is product-page polish.
Your category pages decide your revenue.

Ecommerce SEO that prioritises the highest-yield real estate first. Category-page architecture, PDP at scale, Merchant Center integration, AI Overview defense. Built for DTC brands $500K–$50M across Shopify, BigCommerce, Magento, headless.

Founder-led diagnosis · Scope agreed before ongoing work
Ecommerce search behavior: what the data tells us
Categories
collection architecture connects broad demand to useful product sets
Products
PDP templates need accurate, scalable structure and unique value
Speed
Core Web Vitals and usability should be measured on real store templates
Choice
comparison and buying-guide content can support research before purchase
Definition

What is ecommerce SEO?

Ecommerce SEO is the practice of building organic search visibility for online retailers: the brands selling on Shopify, BigCommerce, Magento, WooCommerce, custom Next.js builds, headless commerce stacks, and the marketplace presences that surround them.

The discipline differs from generic SEO in four ways. The indexable surface is dominated by category pages and product detail pages instead of long-form articles. The conversion event is a transaction, not a lead form, which means revenue per organic session is a useful measurement lens. Core Web Vitals affect usability and can be part of search performance assessment. Product, Offer, AggregateRating and BreadcrumbList schema can also help search engines understand eligible visible content.

Done well, ecommerce SEO is built to keep working across an entire catalogue rather than chase isolated rankings. The leverage is structural: category architecture, PDP scale, faceted-navigation control, and the strategic question is which tier to prioritise first based on where the buyer journey actually breaks for your brand.

The five ecommerce SEO tiers

Five tiers ordered by revenue leverage.
Most teams work them in the wrong sequence.

01

Category / collection page architecture

The highest-yield tier and the most under-optimized. Category pages capture buyers in 'shopping a category' intent. 'leather backpacks for women,' 'organic baby formula,' 'standing desks under $500.' These pages need substantive content above and below the product grid, structured H1 + meta + canonical, BreadcrumbList schema, ItemList schema for the product grid, internal linking from related categories and from blog content, and faceted-navigation control to prevent thin-content URL explosion. Most stores ship category pages with two sentences of boilerplate above the grid. Fixing that single tier is often the largest organic-revenue lever in an entire engagement.

02

Product detail page (PDP) optimization at scale

PDPs can be the largest indexable surface in a catalogue. Scalable work can include structured product titles, useful descriptions, eligible Product and Offer schema, breadcrumb schema, internal-link rules, accurate review markup and visible FAQ content. Prioritize deeper manual work using commercial importance, search demand and page quality rather than a universal percentage split.

03

Google Shopping / Merchant Center integration

The Merchant Center feed is part of the product-discovery surface, not an isolated paid-media silo. Review GTIN coverage, disapprovals and identifier consistency, then align visible PDP data, eligible schema and feed attributes. See /google-shopping for the feed-optimization service.

04

Site architecture for ecommerce

Faceted navigation, canonicals, pagination, and infinite-scroll handling. The structural layer most ecommerce teams quietly get wrong. Faceted URLs (/leather-backpacks?color=black&size=large) generate combinatorial explosion of thin pages that dilute crawl budget. The right control is robots-meta and canonical rules per facet combination: index the high-intent combinations, noindex the rest. Pagination needs rel='next/prev' history-aware solutions or proper canonical-to-self with full content per page. Infinite scroll needs paginated-equivalent URLs for crawlers. Each gets a different rule set; we audit and codify them.

05

Ecommerce content marketing: buying guides + comparisons + gift guides

Buying guides, comparisons and seasonal gift guides can support research and create internal paths into category pages. A useful guide may also earn relevant editorial links when it contains distinctive evidence or judgment. Measure qualified discovery and citations over time rather than assuming a fixed link, ranking or timeline outcome.

Platform considerations

Eight ecommerce stacks.
Each one needs a different implementation approach.

01 · Most popular DTC stack

Shopify / Shopify Plus

Shopify Plus introduces additional implementation and governance choices that should be reviewed against the actual theme, apps and catalogue. Check pagination, canonicals, redirect behavior, schema customization and performance in the live store rather than assuming platform defaults are correct.

02 · Strong enterprise option

BigCommerce

Solid native schema implementation, clean URL handling, decent default Core Web Vitals. The trade-off vs Shopify is a smaller app ecosystem: fewer plug-and-play SEO tools means more configuration through the API and Stencil. Strong choice for $5M+ brands that need flexibility without going full custom.

03 · Heavy but flexible

Magento / Adobe Commerce

Adobe Commerce is highly configurable and can support large catalogues. Performance, indexation and schema quality depend heavily on implementation and developer capacity. See /magento-seo for platform-specific considerations.

04 · WordPress-based, plugin-driven

WooCommerce

SEO quality depends on the theme, plugin stack, hosting and catalogue complexity. Review schema ownership, duplicate output, performance and indexation rules rather than assuming one plugin controls the whole system.

05 · Performance leaders

Custom (Next.js, Remix)

Full control over rendering strategy (SSR / ISR / streaming), schema implementation, and Core Web Vitals, when implemented well, custom builds dominate. The catch: schema, sitemap, robots, and structured-data quality are entirely the developer's responsibility. We work alongside engineering teams to specify the SEO contract that the build needs to satisfy.

06 · Composable architecture

Headless commerce

Frontend (Next.js, Remix, Hydrogen) decoupled from commerce backend (Shopify, commercetools, BigCommerce headless). Performance and editorial flexibility are unmatched. The risk: schema and structured-data quality split across systems, server-rendering of dynamic catalogue content needs careful caching strategy, sitemap generation is bespoke. Headless done well is the strongest position; done poorly it leaks ranking signal.

07 · Distinct discipline

Marketplace SEO (Amazon, eBay, Walmart, Etsy)

Amazon SEO (A9 / A10 algorithm), eBay listing optimization, Walmart Marketplace, Etsy search: each has its own ranking system and is not a substitute for owned-domain SEO. The strategic layer is brand-protection: stopping competitors and aggregators from ranking in marketplace search for your branded terms and re-selling your own product back to you at a margin loss.

08 · Brand site + marketplace mix

Multi-channel + DTC hybrid

The reality for most $5M+ brands. Brand site captures branded and category queries at full margin; marketplace presence handles buyers who only shop on Amazon. The work is auditing the channel split, identifying queries where the brand is losing margin to a marketplace listing of its own product, and reclaiming those queries through brand-site SEO and direct-to-consumer paid amplification.

The 2026 AI Overview problem

AI Overviews can intercept product research.

Google AI Overviews can answer ecommerce research questions inside the results page. The pattern often appears on top-of-funnel prompts such as "best running shoes for flat feet," "difference between merino and cashmere," "what to look for in a standing desk", exactly the queries that used to feed buyers into your buying guides and category pages.

An AI Overview may surface a synthesized answer and cite a small set of sources. Track the prompts that matter to the category, compare them with organic discovery and avoid assuming that a traditional ranking automatically creates visibility in an AI answer.

The defense

Build citation-friendly comparison and FAQ content, keep entity data consistent and use Outrigger where the agreed scope calls for a dated baseline. Independent AI systems decide what they cite.

Why Xpand Digital

Three things most ecommerce SEO agencies cannot match.

The discipline is crowded. The differentiation is in inspectable thinking, careful implementation and an outreach workflow that remains subject to editorial judgment.

Published thinking you can inspect

Joel has published books about marketing and practical AI, including AI for Revenue. Publishing makes the thinking inspectable, but it does not prove a result for an ecommerce store.

AI visibility can be measured when relevant

Build citation-friendly comparison and FAQ content, keep entity data consistent and use Outrigger where the agreed scope calls for a dated baseline. Independent AI systems decide what they cite.

PressForge: link infrastructure for ecommerce

The buying-guide and comparison-content tier only earns its weight when credible third parties choose to cite it. Xpand may use PressForge to manage research and outreach when digital PR is in scope. Publications, placements and outcomes are never promised in advance.

Common questions

What ecommerce founders ask before they hire us.

Ecommerce SEO is the practice of building organic search visibility for online retailers. Shopify stores, BigCommerce sites, Magento brands, WooCommerce shops, headless commerce builds, and the marketplace presences (Amazon, eBay, Walmart, Etsy) that surround them. The discipline is structurally different from generic SEO because the indexable surface area is dominated by category pages and product detail pages (PDPs) rather than blog content, the conversion event is a transaction (not a lead), and Core Web Vitals directly affect both rankings and conversion rate. The leverage tiers are category architecture, PDP optimization at scale, Google Shopping / Merchant Center integration, faceted-navigation control, and content marketing that earns links and captures top-of-funnel research traffic.

We should not claim that category pages drive a universal percentage of ecommerce revenue without store-specific attribution. Their importance comes from intent: a category query often represents a buyer comparing a set of products rather than seeking one SKU. Review category traffic, assisted product views, transactions, merchandising, internal links, and query coverage in the store's own data before deciding where category pages sit in the priority order.

Large catalogues usually need repeatable rules for product titles, descriptions, structured data, internal links, reviews, images, and breadcrumbs. The highest-value or highest-opportunity products can then receive deeper manual work. The split should follow catalogue size, revenue concentration, margin, search demand, data quality, and implementation capacity rather than a fixed percentage applied to every store.

Yes: they are complementary, not substitutes. Organic SEO captures research and shopping queries where the buyer wants to read, compare, and click into your category or PDP. Google Shopping (and the Merchant Center feed underneath it) captures buyers who already know what they want and are price-comparing across retailers. The overlap is in the schema layer: well-structured Product / Offer schema on PDPs feeds organic rich results AND improves Merchant Center match quality. We treat the Merchant Center feed as part of the SEO surface area, not a separate paid-media silo. See the /google-shopping deep dive for the feed-quality, GMC disapproval, and Performance Max overlap layer.

AI Overviews and other AI-assisted results can answer product-research questions before a buyer visits a retailer. The practical response is to review which commercial questions trigger those surfaces, which sources are cited, and whether the brand's product facts, comparisons, structured data, and entity information are clear and supportable. Where relevant, that work can be included in scope, but no engine citation or recovered click volume is guaranteed.

The fundamentals are the same, category architecture, PDP schema, internal linking, Core Web Vitals, but each platform has its own gotchas. Shopify: native SEO is strong but collection pagination, automatic redirects on URL changes, and the /collections/all canonical issue catch teams out. Magento / Adobe Commerce: highly configurable but heavy, performance tuning is a constant project. BigCommerce: strong native schema, weaker app ecosystem. WooCommerce: plugin-driven, varies by stack. Headless (Next.js, Remix, custom): you own performance and rendering, which is a leadership position when implemented well and a disaster when not. We adapt the playbook to the platform rather than running the same checklist across all of them.

Marketplace SEO is distinct from owned-site SEO. Amazon, Etsy, Walmart, and other marketplaces have their own search, advertising, content, and merchandising systems. The useful decision is channel-specific: identify where buyers discover and purchase, what the marketplace costs, which queries the owned site can serve credibly, and how product information stays consistent. A hybrid model may fit, but the recommendation should follow the brand's margins, customer data, fulfilment, and current demand.

We begin with the store's category, product-page, technical, merchandising, and measurement evidence instead of a fixed content quota. Where AI-assisted discovery matters, Outrigger can support dated prompt samples and source review. Where digital PR is in scope, PressForge can support research, pitching, and follow-up. Independent systems and editors still decide what they cite or publish. Joel's books and wider background are available on the About page.

Every ecommerce store retires products, and how you handle those pages decides whether the ranking they earned survives. We decide page by page: keep the URL live and point visitors to relevant alternatives, redirect it to the closest match, or let it go. Google Search Console shows which retired pages still bring search traffic to your website, so nothing valuable disappears quietly. Seasonal lines that come back each year keep their page rather than being rebuilt from nothing, which also protects any link or customer reviews that page collected.

Filtered and sorted URLs are the most common technical problem we find on an ecommerce website, because every size, brand and price filter can spawn another crawlable page. We decide which filter combinations match keywords shoppers use and deserve indexing, and which get closed off so Google spends its crawl budget on pages that sell. Variants get consolidated to one canonical product page, so link value is not split. It is unglamorous technical work, and usually why a large online store with good products cannot get its strongest pages ranking against smaller ecommerce websites.

Build the strategy backwards from your peak. Pages that need to rank in your busiest trading window should be live and indexed well before it opens, because Google and other search engines take time to trust new content and customers research gifts long before they buy. Starting inside the peak is the expensive version: you spend the season fixing a website while paid traffic carries the business. Quiet months are for technical cleanup, keyword research and new pages, so the online store meets its season already ranking for relevant keywords.

Google Analytics and Google Search Console are the honest scoreboard for an ecommerce website: organic sessions, revenue by landing page, and which product pages convert. We report the keywords a page is ranking for and what those visitors do next, separate from paid channels. Marketing reporting should help you decide where the next dollar goes. That also shows when the strategy is wrong. If a keyword brings browsers rather than buyers, we would rather find that early and move the work to terms your customers use. Results you cannot trace are not results.

Durable ecommerce growth

Your category pages are leaking revenue.
We can show you where.

Start with the category, product-page and measurement evidence already available. The first conversation identifies the highest-confidence constraint and whether the next move belongs in SEO, site architecture, tracking or somewhere else.