- Category / collection pagesPriorityhigh-intent discovery surface
- Product detail pages (PDPs)Scalelarge indexable catalogue surface
- Buying guidesAssistresearch and internal-link support
- Homepage + brand queriesBrandbranded and navigational demand
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.
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.
Five tiers ordered by revenue leverage.
Most teams work them in the wrong sequence.
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.
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.
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.
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.
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.
Eight ecommerce stacks.
Each one needs a different implementation approach.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
The pieces underneath ecommerce SEO.
What ecommerce founders ask before they hire us.
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.