Ecommerce SEO Consulting

Faceted navigation: the biggest ecommerce SEO risk

Filters help shoppers narrow a catalog by brand, size, color, price or material. Every filter combination can also create a URL. A category with several filters, each with many values, can produce more URL combinations than the store has products. Search engines then spend their time crawling near-identical pages, while new products and important categories wait.

The answer is not to block all filters. Some combinations match real search demand, such as a category plus a brand or a key material, and deserve a proper indexable page with its own title, introduction and internal links. Most combinations do not.

I build a facet rule set that classifies every filter:

• Indexable: combinations with real demand and enough products, given clean URLs and unique content
• Crawlable but not indexed: useful for discovery, kept out of the index with canonical or noindex rules
• Not crawlable: sort orders, view modes and low-value combinations that should not create links crawlers follow

I also check how parameters are ordered, whether the same filter set produces different URLs, and how pagination works with filters. These rules need developer implementation and must be tested, because a mistake can remove valuable pages from the index. For general crawl and indexing work beyond catalogs, see my technical SEO service.

Category and product pages that earn their place

Category pages usually carry the most commercial search demand, because buyers search for types of products before specific models. Yet many stores treat them as plain grids. I review whether each category matches a real way buyers search, whether subcategories overlap, and whether the page explains the range, helps with choice and links to related categories and buying guides.

Product pages need different things. Buyers compare specifications, compatibility, sizes, delivery and returns. Search engines need unique titles, descriptions that go beyond supplier copy, structured attributes and correct identifiers such as GTINs where applicable. I review the product template rather than individual products, so improvements apply across the catalog.

Variants deserve a deliberate decision. Separate URLs for each color or size can help when buyers search for them specifically, but often create thin duplicates. I recommend a variant strategy per category, with canonical and markup rules to match.

Stock changes are the other common issue. Temporarily unavailable products should usually stay live with clear messaging. Discontinued products may redirect to a replacement or a close category, or return a removed status if nothing fits. Structured data must reflect availability accurately, which my schema markup consulting page covers in detail.

ERP, inventory and product feeds

This is where my background in business systems changes the audit. Most product data starts in an ERP, PIM or inventory system, such as Odoo, ERPNext, Zoho Inventory or Dynamics 365, and is synchronized to the store, to Google Merchant Center feeds and to marketplaces.

Common data problems I find:

• Product names built for warehouse staff, with internal codes and abbreviations, reaching the storefront unchanged
• Attributes stored as free text in the ERP, so filters and markup cannot use them reliably
• Stock and price synchronized on different schedules for the site, the feed and the markup, causing mismatches
• Missing or inconsistent identifiers between ERP items and feed items
• Discontinued items deleted in the ERP, leaving broken pages and feed errors instead of planned redirects

I map the fields that matter for search from source to page, feed and markup, identify where quality is lost, and recommend whether to fix the data in the ERP, add enrichment in a PIM or CMS layer, or change the integration. Integration changes follow the same approach as my ERP integration work. This connection between operations data and acquisition is the differentiator: clean product data serves search, ads and internal reporting at the same time.

Implementation checklist

1. Agree the facet rule set and implement it: clean URLs for indexable combinations, canonical or noindex rules for others, and no crawlable links for sort and view parameters.
2. Consolidate overlapping categories and fix category hierarchy and breadcrumbs.
3. Add useful introductions, buying guidance and internal links to priority category pages.
4. Improve the product page template: unique titles, structured attributes, specifications, delivery and returns information, and related products.
5. Apply the variant strategy with matching canonical and structured data rules.
6. Define stock lifecycle rules for temporarily unavailable, discontinued and replaced products.
7. Fix product data at the source: naming conventions, attribute fields and identifiers in the ERP or PIM.
8. Align the timing of stock and price updates across site, feed and markup.
9. Implement Product and Offer markup from the same data source as the page.
10. Check Core Web Vitals on category and product templates, since filtering and image-heavy pages often fail, following Core Web Vitals consulting.
11. Verify every release with a catalog crawl and Search Console monitoring.

I coordinate between developers, the ecommerce team and whoever owns the ERP, because most catalog fixes need all three.

Measuring ecommerce SEO by category and revenue

Ecommerce SEO should be measured in the same units the business uses: categories, products and revenue. I set up reporting around:

• Indexed pages by type: categories, indexable facets, products, and the share of crawled URLs that are useful
• Crawl distribution from server logs: how much crawler activity reaches products and categories versus filter combinations
• Organic sessions, orders and revenue by category, from analytics joined with your category structure
• New product discovery: how quickly new items are crawled and indexed
• Merchant listing and product snippet performance in Search Console
• Feed health: disapproved items and data mismatches in Merchant Center
• Data quality: attribute completeness and stock or price mismatches between ERP, site and feed

Where your ERP or order system holds margin by product, I recommend reporting organic revenue alongside margin, because traffic to low-margin products is worth less than it looks. The same clean data supports paid shopping campaigns too, so I coordinate with Google Ads management where both channels share a feed. I do not forecast specific revenue gains; I report actual movement by category and explain it.