SEO and Marketing · 9 min read · Updated

Search Everywhere: eCommerce SEO and AI Shopping: Categories, Products and Faceted Navigation

Rank category and product pages, tame faceted navigation, handle variants and out-of-stock items, and get products picked by AI shopping assistants.

eCommerce SEO and AI Shopping: A Practical Guide: featured image for the webocreation.com guide

This post is Chapter 9 of Search Everywhere: The Practical Guide to SEO, AEO and GEO, the free online edition. Chapter and appendix references link to the matching post.

Online stores face every SEO challenge in this book at once, multiplied by thousands of product URLs, plus some challenges of their own: faceted navigation, out-of-stock products, thin manufacturer descriptions, duplicate variants, and now AI shopping assistants that recommend products directly. Because webocreation.com/’s audience is mostly store owners and the developers who build stores for them, this chapter applies the book’s methods to eCommerce specifically.

The eCommerce page types

Every store has the same core templates, each with a different search role:

Page type Typical intent SEO role
Homepage Navigational, broad commercial Brand searches; passes authority to categories
Category (collection) Commercial investigation (“men’s leather wallets”) Usually the biggest organic traffic driver
Subcategory / filtered category Narrower commercial (“men’s bifold leather wallets brown”) Long-tail commercial traffic, if handled carefully
Product Transactional, specific (“Bellroy Hide and Seek wallet”) Product name and model searches; rich results; Shopping
Brand / manufacturer Navigational-commercial Brand + category searches
Blog / guides Informational Top-of-funnel traffic, links, AI citations
Support / FAQ / policies Informational, trust Answers pre-purchase questions; trust signals for AI and users

Most store owners obsess over product pages, but category pages usually have the greatest organic potential, because they match the broader commercial queries people use before they know which product they want.

Category pages that rank

A category page that is only a grid of products gives search engines little to work with. To rank, it needs:

  1. A descriptive H1 and title that match how people search (“Handmade Silver Rings”, not “Collection 7”).
  2. A short introduction above the grid (one or two sentences) that confirms the page is what the searcher wanted.
  3. Helpful content below the grid: a buying guide, size or material explanations, care advice, FAQs. Keep it genuinely useful, not keyword filler.
  4. Internal links to subcategories, related categories and relevant guides.
  5. Crawlable pagination with self-canonical pages.
  6. Unique metadata for each category.

In OpenCart, the category description field supports HTML and appears above the products by default; a theme change can move longer content below the grid, keeping a short introduction on top.

Product pages that convert and get cited

Product pages compete on specificity. A strong product page has:

  • A unique description. Manufacturer descriptions are copied across hundreds of stores. Rewrite them, or at least add unique content: who the product is for, how it compares, what customers say, how it is made.
  • Complete specifications in a table: dimensions, materials, compatibility, model numbers, GTIN.
  • Original photos from several angles, plus video where useful.
  • Genuine reviews with ratings, and Q&A from customers.
  • Clear price, availability, shipping and returns information on the page.
  • Product structured data with offers, shipping details, return policy and ratings (Chapter 7).
  • Breadcrumbs linking back to the category.

For AI shopping assistants, the most important of these are the factual attributes. When a user asks “Which silver ring under $100 is best for sensitive skin?”, the assistant needs explicit facts (material: sterling silver 925, nickel-free, price $79, 4.8 stars from 37 reviews) that it can match against the request.

Faceted navigation: the biggest technical risk

Faceted navigation lets shoppers filter by colour, size, price, brand and so on. Each combination can create a unique URL:

/rings?color=silver
/rings?color=silver&size=7
/rings?color=silver&size=7&sort=price-asc
/rings?size=7&color=silver          (same as above, different order)

With a few facets and values, this explodes into millions of URLs, most of them near-duplicates. Search engines waste crawl budget on them, index thin variants, and split signals.

A sound strategy:

  1. Decide which facet combinations have search demand. “Silver rings”, “rose gold rings”, “men’s rings” may deserve their own indexable pages. “Silver rings size 7 sorted by price” does not.
  2. Turn high-demand combinations into proper static category or landing pages with clean URLs (/rings/silver/), unique titles, H1s and introductions.
  3. Keep other facet URLs out of the index: use canonical tags to the base category, noindex on filtered results, or both.
  4. Stop crawling of low-value parameters, such as sort, limit, view mode and price sliders, with robots.txt rules or by implementing filters without crawlable links (for example JavaScript-driven filtering that updates results without generating <a href> links for every combination).
  5. Keep parameter order consistent so the same filter set always produces the same URL.
  6. Monitor in logs (Chapter 20) to confirm Googlebot is not spending its time in facets.

Tip. Do not combine robots.txt blocking with noindex on the same URLs: if Googlebot cannot crawl the page, it never sees the noindex. Choose one approach per URL pattern based on whether the URLs are already indexed. If they are, use noindex first and let Google recrawl; block crawling later once they have dropped out.

Product variants

A product sold in several colours or sizes can be modelled as:

  • One URL with variant selectors (most common in OpenCart and WooCommerce). Good for consolidating signals; use ProductGroup and hasVariant structured data if supported by your platform, or describe the main offer.
  • Separate URLs per variant (common when variants are searched separately, such as phone colours). Each needs unique content, or a canonical to the main product if they are near-identical.

Google supports product variant structured data (ProductGroup with variesBy and hasVariant), which helps it understand variant relationships for Shopping and rich results.

Out-of-stock and discontinued products

Situation Action
Temporarily out of stock Keep the page live (200), show “out of stock” and expected date, mark availability as OutOfStock or BackOrder, suggest alternatives
Discontinued, with a direct replacement 301 to the replacement product
Discontinued, no replacement but category still relevant 301 to the category, or keep the page with alternatives if it has links and traffic
Discontinued, no relevance 410

Never mass-redirect discontinued products to the homepage; Google treats that as a soft 404.

Internal search, cart and account pages

Block internal search results, cart, checkout, wishlist, compare and account pages from crawling, or noindex them. In OpenCart these live under routes such as product/search, checkout/, account/, product/compare. In WooCommerce, they are /cart/, /checkout/, /my-account/ and ?s= searches.

Merchant Center and free listings

Chapter 17 covered Google Merchant Center. For stores, it is essential:

  • Free listings put products in the Shopping tab, Google Images and other surfaces at no cost.
  • Product data quality (titles, GTINs, attributes, images) determines how often products appear.
  • Price and availability must match the landing page; mismatches lead to disapprovals.
  • Shipping and return policies configured in Merchant Center, or marked up on the site, can appear in listings.
  • Product reviews feeds can add ratings.

Bing has an equivalent, Microsoft Merchant Center, which feeds Bing Shopping and Copilot shopping experiences.

AI shopping assistants

Shopping is one of the fastest-growing uses of AI assistants. People ask ChatGPT, Gemini, Copilot, Perplexity and Google’s AI Mode for product recommendations, comparisons and deals. Several of these products now show product cards with images, prices and merchant links, and some support checkout inside the assistant through partnerships and emerging agentic commerce protocols.

Where does the product data come from?

  • Google’s AI Mode and Gemini draw on the Shopping Graph, built from Merchant Center feeds, product structured data and crawled pages.
  • ChatGPT shopping uses structured product data from third-party providers and merchants, plus web search results and crawled pages. OpenAI has invited merchants to submit product feeds.
  • Copilot draws on Bing Shopping and Microsoft Merchant Center.
  • Perplexity uses its own index plus merchant partnerships.

How to be recommended:

  1. Submit complete, accurate product feeds to Google Merchant Center, Microsoft Merchant Center, and any AI platform that accepts merchant feeds.
  2. Use complete Product structured data on product pages.
  3. Write factual, attribute-rich descriptions: materials, dimensions, compatibility, use cases, who the product is for.
  4. Collect genuine reviews, on your site and on third-party platforms. Assistants often summarise review sentiment (“customers praise the comfort but note it runs small”).
  5. Get included in “best of” roundups and comparison articles on reputable sites; assistants cite these heavily for product recommendations.
  6. Allow AI search crawlers (Chapter 23) so assistants can verify prices and availability on your pages.
  7. Keep prices and stock accurate everywhere; assistants that find conflicting information may skip your store.

Case study connection. webocreation.com/’s ShoppingGPT guide and its AI services (AI shopping assistant, AI product content, recommendations, predictive automation) position it well to publish a practical guide on “making an OpenCart store visible to AI shopping assistants”: feed setup, Product schema for OpenCart 4, review collection and AI crawler policy. This would be a strong, original asset in exactly the topic area where the site has authority.

Speed for stores

Stores tend to be heavier than blogs: large product images, many scripts (reviews, chat, payment, analytics, personalisation). Priorities:

  • Optimise product and category images aggressively (modern formats, responsive sizes, lazy-loading below the fold).
  • Cache category and product pages for anonymous users.
  • Load review widgets, chat and recommendation scripts after interaction or below the fold.
  • Watch INP on add-to-cart and filter interactions.

Content for stores

Blogs and guides attract links and informational traffic that category pages cannot. For a store, the best content:

  • Answers pre-purchase questions (sizing, materials, compatibility, comparisons).
  • Shows products in use (guides, lookbooks, tutorials).
  • Links naturally to categories and products.
  • Includes original photography and expertise.

These guides are also prime AI citation targets, because they answer the “which should I buy?” questions people bring to assistants.

An eCommerce SEO checklist

Key takeaways

  • Category pages usually have the greatest organic potential; give them real content.
  • Product pages win on unique descriptions, complete attributes, original images, reviews and structured data.
  • Faceted navigation is the biggest technical risk; index only combinations with demand and control the rest.
  • Merchant Center feeds and Product schema power both Google Shopping and AI shopping experiences.
  • AI assistants recommend products from feeds, structured data, reviews and roundup articles; factual, consistent product data is the foundation.

Previous: Platform SEO: WordPress, OpenCart and WooCommerce
Next: On-Page SEO and Content That Ranks and Gets Quoted
All chapters: Search Everywhere: The Practical Guide to SEO, AEO and GEO

Search Everywhere (full PDF)The complete guide in one printable PDF.PDF · 2.8 MB
Free download: unlock it in one step

Share this page

or

Mailchimp opens in a new tab to confirm. Unsubscribe any time.

Tagged
Rupak Nepali
Written byRupak Nepali

Rupak Nepali is a web developer, manage Webocreation website and the author of six books:
Getting Started with OpenCart Module Development (Packt, 2013),
OpenCart Theme and Module Development (Packt, 2015),
OpenCart 4: Dev Guide for Themes & Extensions (2024),
OpenCart 4: User Manual (2025),
Cloudflare for the Enterprise Website (2026) and
The Technical Web Guide for Marketers (2026).
Rupak has built OpenCart stores and extensions since 2010, has published more than 600 tutorials on Webocreation, and shares free OpenCart extensions on GitHub.
Find Rupak on
GitHub | Amazon | LinkedIn | X | YouTube.

Leave a Reply

Your email address will not be published. Required fields are marked *