Ecommerce SEO
Faceted Navigation, Crawl Budget and the Problems Most Agencies Skip
This is the section most ecommerce SEO pages leave out, and it's usually where
the biggest wins hide.
A store with 300 products and eight filter attributes can generate tens of thousands
of crawlable URL permutations. Google will crawl a portion of them, index some, and
dilute the authority that should be concentrated on your main collections. The
symptoms are familiar: rankings that plateau despite good content, new products taking
weeks to appear in search, and Search Console showing far more discovered URLs than
you have products.
Our approach is deliberate rather than blanket. We identify which filter combinations
have genuine search demand and deserve indexable, statically linked landing pages.
Everything else is controlled through a combination of robots directives, canonical
logic, nofollow handling on filter links, parameter configuration and, where the
platform allows, server-side rules. We then verify the fix against crawl data and log
files rather than assuming it worked.
The same discipline applies to pagination, internal search result pages, tag archives
on WooCommerce, and automatic collections on Shopify. These are boring problems. They
are also the ones that quietly cap a store's ceiling for years.
Platforms We Work On
Platform matters, because the constraints are real. We do not pretend every CMS
behaves the same way.
Shopify and Shopify Plus — We work within Shopify's fixed URL structure, handle
the /collections/all/ and product-in-collection duplication issue, manage app bloat
that damages Core Web Vitals, and optimize Liquid templates for scalable metadata and
schema.
WooCommerce — WordPress gives more control and more ways to go wrong. We manage tag
and attribute archive bloat, plugin conflicts, hosting and caching performance, and
permalink structures that create unnecessary depth.
Magento and Adobe Commerce — Built for scale, punishing when misconfigured. We handle
layered navigation indexation, store view and multi-site canonicalization, and the
performance work these installs typically need.
BigCommerce, Wix, Squarespace and custom builds — Each gets a platform-specific
technical scope rather than a copy-pasted checklist.
Headless and composable commerce — For Next.js, Hydrogen and similar stacks, we verify
what the crawler actually renders, not what the browser shows after hydration.