Catalogue architecture · Vadodara
Ecommerce SEO
Category and product architecture, faceted navigation and templates that can grow without cloning themselves — regardless of which cart you use.
Fit
Who this is for
A fit
- Catalogues where categories, products and filters are the search surface — not a brochure site with a shop bolted on.
- Teams who can change templates, merchandising rules or the feed, not only the blog.
- Stores whose problem is duplication, thin variants, or an IA that fights the way people shop.
Not a fit
- A Shopify theme or app specialism. A Shopify store whose problem is category architecture or indexation is in scope; customising themes and apps is not a claimed offering.
- Paid-ads accounts, feed-only shopping campaigns, or marketplace SEO (Amazon and the rest) as the engagement.
- Stores that will not give access to how collections, facets and canonicals are actually generated.
Problems
What I diagnose
Facets that explode the index. Colour, size, price and availability each mint URLs. Without indexation rules, Google spends its time on combinations nobody should land on, and the real category pages dilute.
Categories that cannibalise each other. Overlapping collections, seasonal copies, and manufacturer pages that target the same intent. The architecture has to pick an owner per query, not hope the CMS does.
Product templates that say nothing unique. Manufacturer copy, empty specification tables, and variants that each look like a new URL. Thinness here is a template and data problem, not a “write 300 words” problem.
Canonical and pagination fights. Self-canonicals on filtered views, paginated series that drop internal links, and parameter orders that reshuffle the same set. These are header and template bugs with commercial cost.
Migrations and catalogue churn. SKUs disappear, collections are renamed, and the old URLs still earn demand. Without a map, yesterday’s products become soft 404s.
Delivered
What you actually get
Taxonomy and indexation rules
Which category, product, facet and parameter URLs may be indexed, which must noindex or canonical elsewhere, and how that is enforced in the template — not in a one-off robots.txt comment.
Template brief
Title, heading, copy blocks, spec tables, internal links and structured data for category and product types. Written so a developer can ship one change that covers thousands of URLs.
Facet policy
Crawlable filters versus UI-only filters, parameter handling, and which combinations deserve a landing page because people actually search that way.
Internal-link model
How products inherit from categories, how related items are selected, and what must not be left to “customers also viewed” widgets that change every render.
Churn and redirect rules
What happens when a SKU dies, a collection is merged, or a campaign URL expires. A policy, not a heroic spreadsheet after the fact.
Facets are a crawl problem before they are a merchandising problem.
Method
How the work runs
Inventory the URL types
Categories, products, variants, search, filters, tags, campaigns. Count how the index would grow if every combination were allowed.
Name the commercial owners
Which template should win which intent. Everything else is a child, a facet, or a noindex.
Template and facet spec
Indexation, canonicals, copy slots, and the filter policy. Platform-specific implementation is derived from your stack in the diagnostic — not assumed from a logo on this page.
Ship at template level
One category template, one product template, the facet rules. Then sample the live HTML, not the theme preview.
Watch crawl and coverage
Search Console for the patterns we opened or closed. Recrawl after merchandising changes, because a new collection can undo the policy.
Proof
Examples in progress
There is no ecommerce case study on this site, and I will not invent store counts or borrow a platform win I cannot show. When an example is published, it will describe the catalogue shape, the facet policy, and what shipped in the templates — with permission.
Until then, the work is judged on architecture: send a category URL, a product URL and a filtered URL, and I will tell you which of them should even exist in the index.
Questions
Common questions
Do you specialise in Shopify or WooCommerce?
No. This page is about category and product architecture, facets and templates. WooCommerce is the WordPress-adjacent cart: that work is shop architecture plus the WordPress constraints covered on the WordPress SEO page. Shopify appears only when the store’s search problem is architecture or indexation — not as a theme or app specialism.
Can you fix thin product copy at scale?
I can specify which fields the template must have, which products deserve unique copy, and which should stay close to the data sheet. I will not pretend a consultant can hand-write ten thousand unique descriptions. The lever is usually the template plus the PIM, not a copy sprint.
What about product variants?
Colour and size as separate indexable URLs is often the bug. The spec decides when a variant is a product with demand of its own, and when it must canonical to a parent. That decision is merchandising plus crawl maths, not a plugin default.
Do you do shopping feeds and ads?
Feed hygiene matters when it affects landing-page quality and availability, and I will flag mismatches. Running Google Ads or Marketplace campaigns is not this service.
Send a category, a product, and a filtered URL
Those three tell me more than a platform name. I will tell you whether the job is indexation rules, template work, or an audit first.