// Case Studies

How content problems actually look in the wild.

These are illustrative examples drawn from common patterns observed across different e-commerce catalog types. Details are generalized to describe the type of problem and the approach used rather than specific outcomes.

// Case 01
Apparel Retail

Variant explosion on a clothing catalog.

The Situation

An apparel retailer running on Shopify had a catalog of several thousand product SKUs. Each product was available in multiple colors and sizes, and the platform had been configured to create individual URLs for each color variant. This is a common setup, often chosen because it allows each color to have its own images and occasionally its own name.

What it created was a situation where a single t-shirt model generated eight to twelve separate URLs, all with nearly identical descriptions, identical titles except for the color name, and the same category tags. Search engines were encountering clusters of pages so similar that distinguishing between them meaningfully was not straightforward.

The Analysis

Crawl data showed that Googlebot was spending significant time on low-value variant URLs and frequently not reaching newer product pages. Search Console coverage data showed large numbers of discovered but un-indexed pages, concentrated in these variant clusters.

The analysis identified which variant pages had meaningful content differentiation (primarily products where the color was the primary search term) and which were purely structural duplicates with no distinct search value.

The Approach

For the majority of color variants, canonical tags were implemented pointing to the primary product URL. For a subset of products where color-specific pages had distinct search value, those pages were retained but enriched with color-specific content to justify their existence as separate indexed pages. The sitemap was updated to reflect only the canonical set of product URLs.

Platform Shopify
Catalog Size Multi-thousand SKUs
Primary Issue Variant URL duplication
Key Signals Crawl budget dilution, low indexation rate
Approach Used Canonical consolidation + selective enrichment
// Case 02
Home Goods

Faceted navigation generating thousands of thin category pages.

The Situation

A home goods retailer with a broad catalog had implemented faceted navigation to help customers filter by material, finish, room type, style, and price range. Individually, each of these filters was useful. In combination, they were generating an enormous number of unique URLs, most containing only two or three products.

The URL structure was fully indexable. Robots.txt did not restrict any parameter-based URLs. The sitemap did not include them, but Googlebot was discovering them through internal links and spending significant crawl budget on pages that would never provide meaningful search value.

The Analysis

Log file analysis revealed the scope of the problem clearly. Googlebot was visiting a large proportion of faceted combination URLs repeatedly, while important category and product pages were being crawled less frequently than their traffic potential warranted.

Search Console data showed significant numbers of "Crawled but not indexed" pages, almost all concentrated in the faceted URL space. This was not causing a penalty but was quietly diverting resources from pages that actually mattered.

The Approach

A parameter handling strategy was developed that identified which facet types had standalone search value (material type, for example, sometimes has distinct search demand), which could be consolidated via canonical to the parent category, and which should be blocked from crawling via robots.txt directives or parameter configuration in Search Console.

This required careful coordination between the SEO recommendations and the development team to ensure that blocking crawl access did not inadvertently affect the user-facing filter functionality.

Platform Magento 2
Catalog Size Large multi-category
Primary Issue Faceted URL crawl waste
Key Signals Log file analysis, coverage report
Approach Used Parameter strategy + crawl control
// Case 03
Specialty Retail

Auto-generated descriptions creating a thin content problem at scale.

The Situation

A specialty outdoor equipment retailer had a large product catalog where the majority of product descriptions had been generated from a template that pulled in manufacturer specifications. The content was technically unique in that product names and specifications differed, but the sentence structure, framing, and informational approach were identical across thousands of pages.

From a search engine's perspective, these pages offered limited unique value. They were not thin in the word-count sense - many were reasonably long. They were thin in the sense that they added nothing beyond what could be found on dozens of other sites carrying the same products.

The Analysis

Content analysis identified product categories where unique content had the highest potential search value. This was based on search demand data, the competitiveness of the category, and the degree to which differentiated content could realistically be created.

Not every product category warranted investment in unique content creation. The analysis helped prioritize which segments of the catalog would benefit most from enrichment versus which could be adequately addressed through canonical consolidation to category pages.

The Approach

A content enrichment framework was developed for priority product categories, providing guidance on what unique information to include for each product type. For lower-priority categories, a canonicalization strategy was implemented that consolidated thin variants to their parent category pages. The goal was to direct ranking consolidation toward pages with the strongest content, not to simply remove pages from the index.

Platform Custom Build
Catalog Size Thousands of SKUs
Primary Issue Templated thin descriptions
Key Signals Content similarity score, ranking distribution
Approach Used Enrichment framework + selective canonicalization

Recognize any of these patterns in your own catalog?

The specific details differ for every site, but the underlying patterns are common. If something here looks familiar, a conversation is worth having.

Reach Out