E-commerce SEO —
facets, index, and PDPs without a sea of duplicates
Catalogs from thousands of SKUs: which filter combos belong in search, what to canonicalize, and what to cut from the index. Product JSON‑LD in sync with the storefront, sitemap hygiene, and crawl aimed at revenue — not a one‑off Title tweak.
Why does the catalog drown in duplicates while key SKUs starve for crawl?
1
Endless duplicates in the index
Filter combos, sort orders, and URL parameters generate thousands of near-identical pages. Google drowns in duplicates and stops crawling your key products.
2
Products without traffic
Zero-demand SKUs waste crawl budget while truly valuable items wait months for discovery.
3
Snippets that don't attract clicks
Missing or mismatched Product schema: price and availability don't match the storefront, ratings are absent. Competitors grab the clicks.
4
Facet navigation is a black hole
SEO filters aren't configured: valuable landing pages are noindexed, junk combos are open to crawlers. Budget is leaking.
What's included in E-commerce SEO
Catalogs from thousands of SKUs: which filter combos belong in search, what to canonicalize, and what to cut from the index. Product JSON‑LD in sync with the storefront, sitemap hygiene, and crawl aimed at revenue — not a one‑off Title tweak.
Faceted navigation design
Demand for filter combos, SEO landings with unique Title/H1 and body copy; everything else — noindex, canonical, or parameter stripping.
- Matrix: filter axis × indexability
- Pagination and sort rules
- Release priorities for crawl and margin
Product schema & rich results
JSON‑LD Product: price, offers, availability, rating, variants; storefront and feed alignment, Rich Results Test and GSC enhancements.
- Alignment with Merchant Center when relevant
- Avoiding conflicts across multiple JSON‑LD blocks
- Regression checks after price/stock changes
Duplicates & thin URLs
Parameter dupes, zero‑result lists, empty filters — handled in URL and indexing policy, not only with nofollow links.
- Canonical vs noindex: when to use which
- Collapsing color/size variants
- Coverage monitoring with URL samples
Crawl budget
Robots.txt, logs (where available), section priorities and caps on URL series so bots see money SKUs more often.
- Slices by template and HTTP status
- Internal linking recommendations
- Coordination with INP/LCP on listings
PDP commerce
Price, shipping, guarantees, reviews, brand trust, CTAs — one template tuned for organic traffic.
- Commercial‑factor checklist for your niche
- A/B hypotheses on key PDPs
- Coordination with CRO without breaking SEO
Sitemaps & feeds
XML with only indexable, important URLs; auto‑updates; sync with Merchant/marketplaces without price drift.
- Sitemap sections by page type
- Keeping junk URLs out of the map
- GSC limit and error monitoring
Engineering SEO for retail
At tens or hundreds of thousands of SKUs, classic SEO hits scale limits. I steer crawlers with indexing rules, canonicals, and a facet model; conversions get a lift from Product markup and stronger PDP commercial blocks.
Proper catalog structure — I design faceted navigation: which filter axes become unique landing pages with content, which get canonicalized or blocked.
Indexing control — Strict Canonical, Robots.txt, and Sitemap policy: only rank-worthy pages enter search. GSC Coverage monitoring.
Rich Snippets for conversion — Correct Product schema with live price, availability, and rating. Feed-to-storefront sync so the snippet never lies.
How the engagement runs
Three pillars: structure (what ships to search), index (avoid drowning in dupes), conversion (organic traffic shouldn’t die on PDP).
Step 1
Audit & structure
I review the catalog, faceted navigation, and index. Design the target structure: filter landings aligned with keyword research. Outcome: Map of target landing pages and a catalog restructuring plan.
Step 2
Indexing configuration
Roll out canonicals, robots.txt, and sitemaps: block worthless combos, keep valuable landings with unique content. Outcome: Clean index; bots prioritise key pages.
Step 3
Structured data implementation
Implement Product schema, sync data with the storefront. Validate via Rich Results Test and GSC. Outcome: Product rich results with accurate price and availability.
Step 4
Conversion optimization & monitoring
Improve commercial PDP blocks, run A/B hypotheses. Track Coverage, Crawl Stats, and revenue dynamics. Outcome: Organic traffic and conversion growth, cleaner GSC signals.
Personal
The expert who runs the work
No hiding behind a sales team: priorities, reviews, and straight answers—from strategy through reporting.
SEO Strategist
Pavel Barushka
Head of SEO @ Texode · Minsk / hybrid
SEO strategist with an engineering mindset. I lead projects from zero launch to scaling high-load platforms: JS/SPA, subdomains, multilingual and multiregional websites. Technical audits, indexation strategy, semantics and structured data are in my scope.
Frequently Asked Questions
Ready to bring order to your catalog?
Order an audit — I'll show you how many pages are hidden from search and where conversions are leaking.
Free initial consultation