Skip to content
SEO Evaluate
TREN (current language)ARFA

SEO & Organic Growth · Service

E-commerce & Marketplace

Category architecture, faceted navigation rules and feed quality for your store and the marketplaces you sell on.

An e-commerce SEO agency works at catalogue scale: thousands of product and category URLs, filters that multiply them, and prices and stock that change daily. We design the category architecture, write the index and canonical rules for faceted navigation, keep Product schema honest, treat the Merchant Center feed as SEO and run Amazon, Trendyol and Hepsiburada listings on the same plan as your own store. We do not build stores; we make the store you have visible.

How we work

CatalogProduct feed quality + schema
CategoryCategory-page CRO + filters
MarketplaceTrendyol, Amazon, Shopify fit

/01 · Definition

What is e-commerce SEO?

E-commerce SEO is the practice of making an online store's category, product, brand and filter pages crawlable, indexable and able to rank for purchase-intent queries. It covers category architecture, product page content, faceted navigation and canonical rules, duplicate product content, Product and Offer structured data, Merchant Center feed quality, out-of-stock handling, internal linking and site speed. Marketplace SEO applies the same discipline to listings inside Amazon, Trendyol and Hepsiburada; both work best from one catalogue.

A corporate site is a few hundred pages reviewed one by one. A store is a system: every product has variants, every category has filters, and every filter combination can become a URL. Problems at that scale are rule problems: which URL types are indexed, which canonicalise to the parent, what happens when a product sells out, and whether feed and page agree.

/02 · Who it is for

Who this service is for

Brands that run their own store and sell on marketplaces, and teams whose catalogue has outgrown its rules.

/03 · Problems we solve

Problems we solve

  • Index bloat from filters and parameters

    Search Console shows many times more crawled URLs than the catalogue has products, while traffic concentrates on a few categories.

  • Category cannibalisation

    Three categories, a brand page and a blog post compete for one query; the ranking URL changes weekly.

  • Duplicate product content

    Manufacturer descriptions appear word for word on your store, marketplaces and competitors; variants multiply the same text across URLs.

  • Feed disapprovals and data mismatch

    Price and availability in Merchant Center disagree with the page and its Product schema; products are disapproved.

Category page SEO: architecture before products

In most stores the bulk of organic demand is category demand: 'women's midi dresses', 'wireless earbuds', 'baby strollers'. So the first job is the category tree: each category gets a verified search demand, one target query cluster and a scope that does not overlap a sibling; where two chase the same query, one is merged.

The URL hierarchy mirrors that tree. Parent categories, subcategories and the facets that earn an indexable page (typically colour or material) get static, readable paths; every other combination stays a parameter. Breadcrumbs and navigation repeat the hierarchy. Brand pages are indexed only where brand-plus-category searches exist; campaign pages keep a permanent URL.

Product page SEO and duplicate product content

Product page SEO answers three questions: which query the page exists for, how its variants are handled, and where its content has already been published. Title, short description, specification table and Q&A are written to the search intent; manufacturer text is never published as-is, because it already sits on marketplaces and competitor sites.

Variants are the main source of duplicates. No separate search demand means one canonical product URL with variant selection on the page; separate demand means a separate URL with its own title. We define the rule per attribute, so it applies to the whole catalogue. A product shown in several categories still has one canonical path.

/06 · Comparison

Faceted navigation: index, noindex and canonical rules

The decision table we write for every store, following Google Search Central guidance on faceted navigation and canonicalisation.
URL typeExampleIndex decisionCanonical ruleWhy
Parent and subcategory/women/dresses, /women/dresses/midiIndexSelfOwn query cluster; links and authority concentrate here.
Single facet with demand (colour, material)/women/dresses/blackIndex, static URL with unique titleSelfCombinations such as 'black dress' are searched.
Single facet without demand (size, price band)/women/dresses?size=10noindexParent categoryNo demand; thin pages that spend crawl budget.
Multi-facet combination/women/dresses?colour=black&size=10noindex; links not crawledParent categoryCombinations are effectively unlimited.
Sort parameter/women/dresses?sort=pricenoindexParent categorySame content, different order.
Pagination/women/dresses?page=3IndexSelfDeep pages are how products get crawled; canonicalising to page one orphans them.
Internal search results/search?q=dressnoindex; disallowed in robots.txt—Infinite query space; Google Search Central advises against indexing it.

Product schema and Merchant Center feed optimization

Product and Offer structured data lets product pages show price, availability and ratings in search results. One rule: schema carries only data that is visible on the page and true. Price matches the displayed price, availability matches real stock, and a rating exists only if genuine reviews are shown. A Review or AggregateRating that is not on the page breaks Google Search Central's structured data policies.

We treat Merchant Center feed optimization as SEO, because Google compares feed, page and Product schema, and a price or stock mismatch disapproves the product. Feed quality means titles in the language shoppers search in, complete GTIN and brand attributes, correct category mapping and one data source for feed and page. Fix the feed once and free listings and Shopping approval improve together.

/08 · Comparison

Marketplace SEO versus your own store: one plan for both

How we position Amazon, Trendyol and Hepsiburada alongside the owned store. Orders and logistics stay with you; we manage listing content and visibility.
ChannelWhat decides visibilityDependence riskOur role
AmazonA9 search: title, bullets, backend keywords, sales velocity, PPCOne channel carries international revenueAmazon SEO, PPC and organic integration, listing localisation
TrendyolPlatform search: title, attributes, sales velocity, reviewsCommission and ranking changes hit margin directlyListing optimisation, category and attribute mapping
HepsiburadaPlatform search and category placement; seller scoreSeller score gates visibilityListing optimisation, attribute completeness
Your own storeGoogle search: category architecture, content, technical healthDemand takes time; technical debt accumulatesThe full e-commerce SEO programme; turning marketplace awareness into brand search

Technical essentials: out-of-stock pages, speed and internal links

Out-of-stock handling is the rule most stores never write down. Ours has four outcomes: if the product will return, the page stays live with availability updated on the page and in schema; if it is discontinued and a close alternative exists, it 301-redirects there; if there is no alternative but the page has links or traffic, it redirects to the parent category; otherwise it returns 410. Seasonal categories wait at a permanent URL.

Site speed is a ranking and a conversion matter. We measure Core Web Vitals (LCP, INP, CLS) per template and report store-specific causes: image weight, third-party scripts and the INP cost of filter interactions; implementation sits with your developer. Internal linking carries authority to deep pages: homepage to categories, categories to subcategories and indexable facets, products to related categories. Multi-country stores plan duplicate content and hreflang with our international SEO work.

Category content and category CRO

A category page is more than a product grid: a short orienting line above the grid and a buying-guide paragraph with Q&A below it make the page meaningful for its target query and distinguish it from its own filter pages.

Category CRO asks how well the page moves a visitor to a basket: filter layout, default sort, product-card content, mobile layout and pagination, tested with our CRO service.

/11 · Method and process

How we run an e-commerce SEO engagement

Five steps; the first three usually complete in the first quarter, the last two run monthly.

  1. 01

    Catalogue and index audit

    We crawl the store, compare indexed URLs with the catalogue, and list parameter bloat, cannibalised categories, duplicate content, Product schema errors and Merchant Center disapproval reasons, with marketplace listings in the same audit.

  2. 02

    Category architecture and URL rules

    We redefine the category tree against search demand, select the facets that earn an indexable URL, write canonical and noindex rules per URL type and set the out-of-stock policy as a specification your developers can implement.

  3. 03

    Product data and feed quality

    We align Product and Offer schema with real page data, rewrite feed titles and descriptions in search language, complete GTIN, brand and category mapping, and restructure marketplace titles.

  4. 04

    Content and category CRO

    Priority categories receive orienting copy, buying guidance and Q&A; product descriptions are rewritten away from manufacturer text. Category layout and filters are tested through our CRO work.

  5. 05

    Measurement and monthly cycle

    Search Console, Merchant Center and GA4 data are reported by template, with marketplace performance alongside. Each month we check new products against the rules and review disapprovals and cannibalisation.

/12 · Tools and platforms

Platforms and tools we work with

/13 · Measurement and KPIs

How we measure e-commerce SEO

Measurement is per template: category, product, facet and brand pages are tracked separately; no metric is promised at a level.

  • Indexing

    Catalogue-to-index ratio

    Indexed URLs against the URLs we want indexed.

  • Visibility

    Non-brand clicks by template

    Clicks and impressions for category, product and indexable facet pages.

  • Catalog

    Feed approval and rich-result coverage

    Approved products in Merchant Center and pages earning a Product rich result.

  • Conversion

    Orders from organic sessions

    Add-to-basket and orders by organic landing template in GA4.

/14 · Common challenges

Common challenges in e-commerce SEO projects

  • Platform limits

    Some platforms cannot noindex filter URLs or create static facet paths. The fix may be a setting, an app or developer work; we write and verify the specification.

  • Product data sources

    When feed, page and schema come from different systems, mismatches are inevitable; moving to one source is an integration task we specify.

  • Marketplace algorithm changes

    Amazon, Trendyol and Hepsiburada change ranking rules without notice. We monitor listings and adapt titles; we do not promise positions.

/15 · Strategic considerations

Strategic considerations before you start

How SEO Evaluate approaches e-commerce SEO

We treat the store and the marketplaces as one catalogue: product data, title structure and content priority are defined once and adapted to each channel, removing most feed disapprovals and duplicate content at the source.

We are clear about what we do not do. We do not build, migrate or theme stores on Shopify, WooCommerce or any other platform; we run SEO and marketing on the store you have and coordinate implementation with your developer. We do not operate marketplace accounts, orders or logistics.

We do not promise numbers. We start with the audit, deliver the rule table and category architecture in writing, and report monthly which decision moved which template. Native production in Turkish, English, Arabic and Persian lets cross-border stores publish product content per market.

/18 · Frequently asked questions

E-commerce SEO: frequently asked questions

How is e-commerce SEO different from regular SEO?

Scale and rules. A corporate site can be handled page by page; a store has thousands of products, variants and filter combinations, so e-commerce SEO writes rules per URL type: which facets are indexed, how variants canonicalise, what happens to sold-out products and how the feed aligns with schema.

Should I invest in marketplaces or in my own store?

Treat them as complementary. Amazon, Trendyol and Hepsiburada deliver demand quickly; your own store carries brand search, long-tail category queries and a customer relationship no platform controls. The same product data serves both; budget follows each channel's share and dependence risk.

Should I start with category pages or product pages?

It depends on demand. Fashion, home and beauty are dominated by generic category searches, so categories come first; electronics and spare parts are searched by model name, so product pages lead. The audit shows which template carries demand.

Should filter pages be indexed?

Only facets with real search demand, such as colour or material combinations like 'black dress'. Those get a static URL, a unique title and brief content. Size, price band, sort order and multi-facet combinations stay noindex and canonicalise to the parent; internal search results are never indexed.

What should I do with out-of-stock product pages?

If the product will return, keep the page live, update availability on the page and in Product schema, and show similar products. If it is discontinued, 301-redirect to the closest alternative; if none exists but the page has links, redirect to the parent category; otherwise return 410.

Is there an SEO difference between Shopify and WooCommerce?

Both work with the right rules; the difference is control. Shopify fixes URL structure and some canonical behaviour at platform level; WooCommerce leaves more to plugins and developers. We write the rules and verify implementation with your developer; we do not set up stores.

Should I add review ratings to Product schema?

Only if genuine customer reviews are collected and visible on the page. A rating that is not on the page violates Google's structured data policies and can cost the rich result. Price and availability follow the same rule: schema, page and feed must match.

Official PartnerMeta · Google Partner · TikTok Marketing Partner
  • Meta
  • Google
  • TikTok

Next step

Request an SEO audit

Tell us where you are today; we will scope the work, set priorities and outline the first 90 days together. No commitment, a written assessment.