Your own product page is the duplicate
Here's the sequence that quietly costs Indian fashion brands their branded search. You write product copy. You export the same copy in the marketplace feed. Three marketplaces publish it against listings on domains with vastly more authority than yours. Google picks a canonical for that near-identical text, and it isn't you.
So you end up paying to acquire a customer who searches your brand plus a product name, finds a marketplace listing, buys there, and hands a commission to a platform for demand you created. The listing wasn't stealing your traffic. Your feed handed it over.
The fix costs a copywriter, not a developer. Write the marketplace feed and your own product detail pages differently — different opening lines, different detail, different structure. Marketplace listings should be functional and specification-led, because that's how people browse there. Your own page should carry the things a feed template physically can't hold: styling context, fabric behaviour, care, the model's measurements alongside the size worn, and the reason the piece exists.
Nobody searches for 'dress'. They search for a situation.
Head terms in apparel belong to the marketplaces and will for the foreseeable future. That's fine, because head terms are also where intent is weakest. The demand that converts is specific, and it clusters into three shapes that marketplace category pages handle badly because they're generated from attribute data rather than written by someone who understands the occasion.
This is the same argument we make in ecommerce SEO, but in fashion the gap is wider — because clothing is bought for a context, and context is exactly what a generated grid can't describe.
- Edits are collections, not blog posts. If your occasion content lives in
/blogand links only to other posts, it will rank and sell nothing. Give it a collection URL with products on it. - Write the guidance a stylist would give, including what not to buy. The paragraph that says 'linen creases and that's the point, so skip it for a nine-hour travel day' is the one that gets linked to.
- Fit clusters are the most neglected and the most loyal. Someone who finds a brand that actually stocks their length doesn't go back to searching.
| Cluster | How people actually search | What ranks |
|---|---|---|
| Occasion | Outfit for a haldi, mehendi guest outfit, first-day-of-office wear, cocktail saree | A curated edit page with real styling guidance, linking to 12–20 products |
| Fabric and climate | Linen shirts for Chennai summer, breathable kurtas for humidity, chanderi versus cotton | A guide that explains the trade-off honestly, then links to the collection |
| Fit and body | Petite length trousers, plus size ethnic wear, maternity work wear, tall sizes India | A permanent collection page, not a filter state — this demand is stable and under-supplied |
Collections die every quarter. Your URLs shouldn't.
Fashion has a structural problem no other retail category has at the same frequency: four or more collection changes a year, each one launched with a campaign, links and paid traffic, then quietly deleted. Over three years that's a dozen retired URLs that once held every link the launch bought.
The default reflex — delete the page, or redirect the lot to the homepage — throws that away. Google treats bulk redirects to an irrelevant destination as soft 404s, so the link equity doesn't transfer; it evaporates. Write the retirement policy once, before the next drop, and make it part of the launch checklist rather than a cleanup task nobody owns.
- Evergreen URLs for anything that repeats.
/collections/summer-editrefreshed every year, not/collections/ss26archived every year. Season codes belong in the page content, not the path. - Retiring a collection with a clear successor: 301 redirect to the successor collection. Same audience, same intent, links preserved.
- Retiring a one-off collaboration or capsule: keep the URL live as an archive page with the story and links to current stock, especially if press coverage points at it. A page that earned real links is worth more alive.
- Sold-out individual products: keep the URL indexed with the correct availability state and visible alternatives. Stock is temporary, rankings aren't.
- Never redirect a collection to the homepage in bulk. If nothing comparable exists, send it to the parent category and accept the smaller loss.
The size guide is a ranking asset and a returns fix
Indian apparel sizing is inconsistent between brands, and the conversions between IN, UK, US and EU labelling are something buyers genuinely look up before ordering. saree blouse size chart, womens shoe size chart india, kurta size guide are real, recurring searches — and most brands answer them with a modal popup that a crawler never sees and a customer can't bookmark.
Give the size guide a real indexable URL per category. Put actual garment measurements in a table, not just labels: chest, shoulder, length, sleeve, in centimetres and inches. Add how to measure, what the fit is intended to be, and the model's height with the size worn on every product photo set.
Then look at your returns data before you argue about the priority. Ask ops what proportion of returns cite size or fit — in apparel it's usually the largest single reason. A size page that reduces that number is paying for itself twice, once in search and once in reverse logistics.
The same logic applies to the returns and exchange policy page. Indian shoppers check it before a first purchase from an unfamiliar brand, it earns branded search, and burying it in a footer link with legal phrasing costs you conversions you already paid to acquire.
Images and video are the product, so treat them like pages
In apparel, the photograph is the product description. It's also, on most fashion sites, the reason the page is slow and the reason it doesn't appear in image search.
Google Images is a genuine discovery surface for clothing — people search visually for silhouettes, prints and colours — and it's a surface where you can beat a marketplace, because your photography is yours and theirs is often the same supplier shot everyone else uses.
- Descriptive filenames and alt text.
ivory-chanderi-kurta-set-front.jpgwith alt text describing the garment, notIMG_4471.jpgwith alt text repeating the brand name. - Include images in an image sitemap, especially if the gallery loads through JavaScript. Lazy loading implemented badly is the most common reason a catalogue's photography is invisible to Google.
- Fix the hero image before anything else. It's almost always the Largest Contentful Paint element on a product page — serve it in a modern format, sized correctly, with explicit dimensions so the gallery doesn't shift the layout as it loads.
- Mark up product video with
VideoObjectwhere you have it. Try-on and drape videos answer the question static photography can't, and they're eligible for their own results. - Unique photography per SKU. Shared supplier imagery across your site and three marketplaces gives Google nothing to distinguish you with.