SEO for clothing and electronics stores in Uzbekistan
Two verticals with opposite mechanics: electronics buyers search by model name, clothing buyers by descriptive attributes. Here is what that changes in structure and content.
Different demand logic
In electronics, demand concentrates on models: people search a specific name with a part number or storage size. That makes the product page the primary entry point, and it must be indexed and optimised for the exact model name.
In clothing, demand is descriptive: colour, cut, season, size, fabric, occasion. The entry point is not the product page but the collection page — 'midi summer dresses', 'men's trainers size 45'. Individual clothing pages rarely capture search on their own.
Hence the key difference in priorities: for electronics, product and model pages first; for clothing, generating and optimising filter and collection pages.
Filters: which ones to open for indexing
Opening every filter combination is impossible — the URL count grows exponentially and crawl budget disappears. Open only combinations with confirmed demand.
A workable criterion: a one- or two-filter combination with visible demand in Wordstat or Search Console that still leaves at least ten to fifteen products. Such a page gets its own title, h1, short description and a place in the sitemap.
Everything else is closed: meta robots noindex, follow on pages, robots.txt for parameters, Clean-param for Yandex. Open filter pages should use readable URLs such as /trainers/mens/size-45/ rather than a parameter string.
The product page: mandatory minimum
A unique title with the model and key attribute, an h1 with the full name, price in soum, stock status, delivery timing for Tashkent and the regions, a specification table, several photographs and a related products block.
Manufacturer descriptions copied by every shop provide no advantage. Add what others lack: your own photos, compatibility notes, real usage experience and on-site customer reviews.
Mark the page up with schema.org/Product containing offers: price, priceCurrency "UZS", availability set to InStock or OutOfStock, and aggregateRating only where real reviews exist. Rating markup without visible reviews violates policy and invites manual action.
Stock, pricing and seasonality
When an item sells out, do not delete the page or serve a 404 if it has traffic or links. Keep 200, show 'out of stock', offer alternatives and a back-in-stock notification. For seasonal lines this matters especially: the page accrues equity for the next season.
Update soum prices on the page and in the markup simultaneously. A mismatch between snippet and page price annoys users and causes product disapprovals in Merchant Center.
Account for the Uzbek market's seasonal peaks: air conditioners and fans in spring, heaters in autumn, school uniforms and stationery in August, wedding categories in season. Seasonal content is prepared two to three months ahead, not at the peak.
Competing with marketplaces
Model-name queries are almost always dominated by marketplaces. Beating them head-on for generic queries is expensive and often unrealistic. The workable strategy is moving to more specific and local phrasings.
What gives an edge: stock available in Tashkent for same-day pickup, installation and servicing, warranty through a local service centre, expert consultation. Turn those into dedicated pages and into product page content.
Comparisons and buying guides also work, since marketplaces rarely produce them: 'how models A and B differ', 'what to choose for a 60 square metre flat'. Such material captures informational traffic before the shop is chosen.
Technical bottlenecks in catalogues
Pagination: every listing page self-canonical and indexable, with infinite scroll always backed by linked page-by-page navigation, or the crawler never sees products beyond page one.
Speed: a catalogue rendering a hundred cards with full-size images is the classic cause of poor metrics. Use modern image formats, lazy loading and a sensible per-page product count.
Product duplicates across categories: if one item is reachable at several URLs, choose one canonical address and point the rest to it with rel=canonical. Multiple URLs for one product are the most common duplication source in shops.