SEO for stores, where the problem is usually too many pages
eCommerce SEO applies search work to stores, where the defining problem is scale. A catalogue generates thousands of URLs through variants, filters, sorting and pagination, most of which should never be indexed, and controlling that is more consequential than any individual page's content.
General SEO assumes a site has too few pages answering too few questions. Stores have the opposite problem. A thousand-product catalogue with filtering can generate hundreds of thousands of crawlable URLs, and the search work is mostly about deciding which small fraction deserves to exist in an index.
Faceted navigation is the main offender. Every filter combination produces a URL, and unmanaged that is a combinatorial explosion consuming crawl budget on pages nobody searches for. Alongside it: variants published as separate products so the same shoe competes with itself eleven times; category pages with nothing on them but a product grid, so there is no content to rank; and manufacturer descriptions copied verbatim, which every other retailer selling that product has also copied.
When this work makes sense
Questions worth asking any supplier
How many URLs does filtering generate, and which are indexable? This is usually the biggest single issue.
Do category pages have content, or only a product grid? A grid alone gives nothing to rank.
Are variants separate products or variants? Separate ones compete with each other.
Is product copy original or the manufacturer's? Everyone selling that product has the same text.
Is Product structured data accurate, including price and availability? Wrong data here is worse than none.
Deliverables
Faceted navigation audit with an indexation rule per facet type
Category architecture built around how customers search rather than internal hierarchy
Category page content that gives search engines something to assess
Variant handling reviewed so products do not compete with themselves
Original product content for the lines that justify the investment
Product structured data with accurate price and availability
Out-of-stock and discontinued product handling, which most stores get wrong
Internal linking from content to the categories that convert
Built with
Process
The first piece of work is a crawl-budget assessment: how many URLs the store exposes, how many are indexable, and how many are variations of the same thing. On large catalogues the gap between pages you meant to publish and URLs you actually expose is frequently an order of magnitude. Until that is controlled, content work on individual pages is being done on a site where crawlers are spending their time elsewhere.
The standard nine stages, discovery, strategy, UX/UI, development, content and SEO, testing, launch, measurement and continuous improvement, apply to every project. The paragraph above is what differs for this one.
What moves the number
Pricing depends on scope, functionality, integrations and content requirements. These are the factors that change it most:
Where to concentrate effort in a store
Category pages
Fits: Highest commercial value, these target the terms with volume and intent
Limits: Needs content beyond a product grid, which stores resist adding
Product pages
Fits: Long-tail and branded searches for specific items
Limits: Enormous volume; original content for every product is rarely justified
Content and guides
Fits: Capturing research-stage searches before the purchase decision
Limits: Converts indirectly; needs internal linking to the categories that sell
Case studies
No published eCommerce SEO case study. Revenue attribution from organic search requires client data we do not have permission to publish.
MBGDesk operates from 4 offices in India, United States, United Kingdom, United Arab Emirates. We hold no industry certifications and do not imply otherwise.
Frequently asked questions
Should filter URLs be indexed?
Most should not. A few high-demand combinations, a brand within a category, for instance, may deserve indexing if people genuinely search for them. The rest should be blocked or canonicalised, because unmanaged faceted navigation consumes crawl budget on URLs nobody searches for.
Do we need unique descriptions for every product?
For the products that matter commercially, yes. For a long tail of thousands, it is rarely a sensible investment. Manufacturer copy is identical across every retailer selling that item, so those pages compete on other signals. Prioritise by what actually sells.
Why do marketplaces outrank us for our own products?
Domain authority, mostly, plus review volume and freshness. Competing directly on a product term against a major marketplace is usually unwinnable. The realistic ground is category terms, your brand, and content they do not produce.
What should happen to out-of-stock products?
Keep the page if the item is returning, show availability clearly and offer alternatives. Redirect to the category if it is discontinued. Deleting it produces a 404 that discards whatever ranking and links the page had accumulated, which is the most common mistake here.
How should we handle product variants?
As variants on one page, with a canonical to the main product URL. Publishing each colour as a separate product creates near-duplicate pages competing with each other, splits their signals, and gives search engines a reason to trust none of them.
Do category pages need text?
They need something to assess beyond a grid of products. That does not mean a wall of text below the fold that nobody reads, a genuine introduction explaining the range and helping someone choose serves both the reader and the search engine.
Is Product structured data worth adding?
Yes, and accuracy matters more than presence. Price and availability that disagree with the page can cost you rich result eligibility, and wrong structured data is a worse position than none at all.
Services that connect to this
Talk to us about this
Tell us what you are trying to build and we will come back with scope, approach and an estimate.