Good product descriptions do two jobs at once: they answer the questions a shopper would otherwise ask a salesperson, and they give Google enough original, specific text to understand and rank the page. The working formula is simple to state and hard to do at scale. Lead with who the product is for and the one or two reasons to choose it, follow with a scannable block of specifications in a consistent format, add the practical details people worry about (size, fit, care, compatibility, what is in the box), and write all of it yourself rather than pasting the manufacturer's text that a hundred other stores already use. If you are planning a store with an ecommerce website development partner in Pune, the description is not something to "fill in later". It shapes the product template, the data you collect, the feed you send to Google and how much work your team does every time a new product goes live.
This guide is for owners and catalogue managers of Indian D2C brands, retailers moving online and manufacturers selling direct. It covers why copied and thin descriptions hold stores back, how to structure a description so it works on a phone, how to write for different kinds of products, how to handle hundreds or thousands of SKUs without producing junk, how AI drafting fits in, and what the website itself needs to support all of this.
Why most online store descriptions underperform
Review a few dozen small Indian stores and the same problems repeat.
- Manufacturer copy pasted unchanged. The supplier's paragraph is on the brand site, on the marketplaces and on every reseller. Google has many near-identical pages to choose from and usually prefers the bigger or older site. Your page adds nothing it cannot find elsewhere.
- One line, or nothing. "Premium quality cotton kurta. Buy now." A shopper with a question about fabric weight, lining or wash care has no answer and leaves to look elsewhere, or orders, guesses wrong and returns it.
- Specifications buried in a paragraph. Dimensions, material and compatibility are written as prose, so a shopper scanning on a phone cannot find them, and they are inconsistent from one product to the next.
- Templated text with the name swapped. Three hundred products share the same 80 words with only the product name changed. That is close to duplicate content inside your own site.
- Claims nobody can check. "Best in India", "100% guaranteed results", "doctor recommended" with no source. These erode trust and, in regulated categories such as health, cosmetics and food, can create real legal exposure.
Google's own guidance on creating helpful content asks whether a page provides original information and substantial value compared with other pages in search results. A copied supplier paragraph fails that question by definition. Its guidance on duplicate content is more relaxed than many people fear (there is no "penalty" for some duplication), but when many pages carry the same text, Google picks one to show and filters the others. Usually that is not you.
What a product description is actually for
Before writing a word, be clear about what the description must do for your particular store. It is usually some mix of these:
| Job | What it means in practice |
|---|---|
| Answer pre-purchase questions | Size, fit, material, compatibility, what is included, how to use, how to care for it |
| Reduce returns | Set accurate expectations about colour, feel, scale and limitations |
| Differentiate | Explain why this product rather than a similar one, in your store or elsewhere |
| Help search engines | Provide unique, specific text that matches how people search for the product |
| Support ads and feeds | Supply clean text for Google Merchant Center and Meta catalogues |
| Build the brand | Sound like a real business with a point of view, not a parts list |
A ₹400 phone case and a ₹40,000 sofa need very different amounts of description. The sofa buyer wants dimensions, frame material, foam density, fabric options, delivery and assembly details and care. The phone case buyer wants to know it fits their exact model and what it is made of. Length should follow the decision, not a target word count.
Structure: a layout that works on a phone
Most Indian shoppers browse on mobile, so a wall of text is the enemy. A structure that works across most categories:
1. The opening: who it is for and why
Two to four sentences, visible without tapping "read more". Name the product plainly, say who it suits and give the main reasons to choose it. Avoid generic adjectives. Compare:
- Weak: "Experience unmatched comfort with our premium cotton kurta, crafted for the modern woman."
- Better: "A straight-cut everyday kurta in 60s cotton cambric, light enough for Pune's April afternoons and lined at the yoke so it is not see-through. Knee length on a 5'4" frame, with side pockets."
The second version answers four questions a shopper would otherwise have to ask. It is also unique to your store.
2. Key benefits or features as short bullets
Three to six bullets, each one a concrete fact with its benefit. "Side seam pockets deep enough for a phone" is useful. "Stylish and elegant" is not.
3. Specifications in a consistent table
Specs should come from structured product data, not be typed into the description by hand. A table makes them scannable and keeps every product consistent:
| Attribute | Example value |
|---|---|
| Material | 100% cotton cambric, 60s count |
| Fit | Straight, relaxed through hips |
| Length | 44 inches (size M) |
| Sleeve | Three-quarter |
| Care | Machine wash cold, dry in shade |
| Country of origin | India |
In a WooCommerce store these usually live as product attributes; in Shopify, as metafields. Either way, entering them as data rather than prose means the same values can power filters, comparison tables, structured data and feeds.
4. Practical details shoppers worry about
This is where many returns are prevented. Depending on the category:
- Size and fit: model's height and the size worn, how the cut runs, a link to a size chart.
- Scale: dimensions with a reference ("about the width of an A4 sheet"), a photo in use.
- Compatibility: exact model numbers, what it does not fit.
- What is in the box: every item, including what is not included (batteries, adapters, wall fixings).
- Care and storage: washing, cleaning, shelf life after opening.
- Usage: how to use, how much, how often, for consumables.
5. Trust details specific to the product
Warranty terms, certifications you can actually document (with the certificate number or a link), ingredients lists, and any legally required declarations. Store-wide policies such as returns and delivery should be linked from the product page, not re-typed into every description where they will go out of date.
6. Optional: a short FAQ
For products that generate repeat questions on WhatsApp or in reviews, a few short Q&As at the bottom help. Pull them from real customer messages. Keep them product-specific; generic store FAQs belong in a help centre.
Writing for different kinds of products
A single template does not fit every category. Some patterns that work:
Fashion and apparel
Fabric, weight or GSM where you know it, how it feels, how it drapes, transparency, lining, stretch, fit relative to standard sizing and wash behaviour (does it shrink, does colour bleed). Include the model's measurements and size worn. Describe colour honestly, especially where screens distort it: "a muted olive, greener than it looks in daylight photos" saves a return.
Home, furniture and decor
Exact dimensions, weight, materials of each part, finish, assembly requirements and time, weight capacity, and whether it will fit through a standard door or lift if it is large. Room-setting photos plus a dimension diagram do more than adjectives.
Electronics and accessories
Compatibility first, with exact model numbers. Then specs that matter for the decision (capacity, wattage, connectors, cable length), what is in the box, warranty and who services it. Avoid copying the long manufacturer spec sheet verbatim; select what matters and link to the full sheet as a PDF if needed.
Beauty, wellness and food
Ingredients, usage, quantity, shelf life, storage, suitability (skin type, dietary), and only claims you can substantiate. These are categories where regulators take an interest in claims, so avoid medical or "cures" language unless you have the approvals to back it. If you are unsure, take advice before publishing; a toned-down description is cheaper than a notice.
B2B and industrial products
Specifications, standards met, tolerances, minimum order quantity, lead time, documentation available (datasheets, test certificates) and how to request a quote or bulk price. Many B2B buyers want to download a datasheet; offer one.
Search: using keywords without writing for robots
People search for products in specific ways: "cotton kurta with pockets", "6 seater teak dining table", "iPhone 15 silicone case". Your description should naturally include the words a buyer uses, because the buyer uses them too.
Practical rules:
- Product name (H1) should be descriptive. "Aria Kurta" means nothing to a searcher; "Aria Straight Cotton Kurta with Pockets – Olive" carries the product type, key feature and colour.
- Use the phrases customers use. Check your site search logs, Search Console queries, customer WhatsApp messages and marketplace listings for how people describe the product. A Pune shopper may search "kurti" rather than "kurta"; a B2B buyer may search by a part number.
- Do not stuff. Repeating "cotton kurta for women online India" six times makes the page worse for humans and is listed by Google as a spam practice (keyword stuffing). Mention the important phrase where it fits naturally and spend the rest of your words on substance.
- Avoid near-duplicate variant pages. If the same kurta comes in five colours, one product page with colour variants usually beats five pages with identical text. If each colour must be its own page (for example, separate SEO demand), write something genuinely different for each.
- Keep the visible text and structured data consistent. Your Product structured data should describe what the page actually shows: the same price, availability and name. We go into this in our guide to product page structure and Product markup.
Category pages need their own copy too, written differently from product descriptions. Our guide to collection and category pages that rank and convert covers how they fit together.
Product feeds: the description Google Shopping sees
If you advertise on Google Shopping or show free listings, your product description also goes to Google Merchant Center through a feed. Google's product data specification allows up to 5,000 characters of plain text in the description attribute, asks that it describes the product accurately and matches the landing page, and says not to include promotional text such as "free shipping" or text in all capitals. Google's specification also includes a separate structured description attribute intended for descriptions created with generative AI, so check the current specification if you use AI to produce feed text.
What this means for the build:
- The feed should pull from the same product data as the page, so the two never drift apart.
- Promotional banners ("Diwali sale 30% off") belong in promotions or sale price fields, not in the description text.
- HTML formatting in descriptions may be stripped or mishandled in feeds; write so the text still reads well as plain text.
Meta catalogues work on similar principles. A clean description field serves both.
Scaling: how to write for hundreds or thousands of SKUs
The honest problem for most growing stores is volume. A 2,000-SKU store cannot hand-write a perfect 300-word description for every product before launch. A workable approach:
Prioritise by revenue and search demand
Sort products by sales, margin and search demand. Hand-write or deeply edit descriptions for the top 10 to 20 percent first: bestsellers, high-margin items and products people search for by name. These pages carry most of the revenue and most of the search opportunity.
Write category templates, then make each product specific
For the long tail, build a structured template per category: which attributes are required, what the opening must say, which practical details are mandatory. Writers (or a supervised AI draft, see below) then fill in the specifics. The template ensures consistency; the specifics make each page unique. A template with only the name swapped is not enough.
Fix the data first
Most description problems at scale are data problems. If material, dimensions and compatibility are missing or inconsistent in your catalogue, no writer can produce good copy. Clean product data before launch is the single biggest time saver. Our guide to preparing your product catalogue data before the store is built walks through a spreadsheet structure.
Use real customer language
Reviews, returns reasons and pre-sale WhatsApp questions tell you exactly what each description is missing. If three customers return a jacket because "it runs small", that sentence belongs in the description.
Set a refresh routine
Descriptions decay. Specs change, suppliers change materials, claims become outdated. Review bestsellers quarterly and update when a product changes. Do not change the publication date to fake freshness; update the content and let the change speak for itself.
Using AI to draft descriptions without producing junk
AI tools can turn structured product data into a readable first draft quickly. Used carefully, that is a genuine saving. Used carelessly, it produces thousands of interchangeable paragraphs full of words like "elevate", "seamless" and "premium" that tell shoppers nothing and add no original value.
Google's guidance is that using AI is not against its policies in itself, but that generating many pages without adding value, primarily to manipulate rankings, falls under its spam policy on scaled content abuse. For a store, the practical line is:
- Feed the AI facts, not just a product name. Give it the attributes, materials, dimensions, real customer questions and your brand's tone guide. Without facts, it invents.
- Have a person check every claim. AI tools confidently state things that are not true: wrong materials, invented certifications, incorrect compatibility. In a product description, that becomes a misleading claim from your business.
- Edit out filler. Remove generic adjectives and replace them with specifics.
- Do not publish at a volume you cannot review. If nobody can check 2,000 AI drafts, publish fewer, better ones and work through the rest.
What the website needs to support good descriptions
This is where the build matters, and where an ecommerce website development partner in Pune earns its fee. Ask for:
| Feature | Why it matters |
|---|---|
| Structured attributes or metafields per category | Specs entered once, reused in tables, filters, schema and feeds |
| A product template with defined sections | Opening, bullets, spec table, details, FAQ all render consistently |
| Opening visible without tapping on mobile | The most important text is actually seen |
| "Read more" for long content that stays crawlable | Collapsed text in the HTML is fine; text loaded only after a click may not be |
| Size charts and guides as reusable blocks | Update once, applies to every relevant product |
| Product-level FAQ field | Answers real questions without bloating the main description |
| Feed generation from the same data | Merchant Center and Meta stay in sync with the page |
| Bulk import and export | Catalogue managers can edit descriptions in a spreadsheet and re-import |
| Revision history | You can see who changed what, and roll back mistakes |
Collapsed "read more" sections deserve a note. Content hidden behind a tab or accordion that is present in the page's HTML is generally fine for search, and it keeps mobile pages tidy. Content that is only fetched from the server after a click is riskier, because crawlers may never see it. Ask your developer how the "read more" is implemented.
A worked example: rewriting one description
Here is an illustrative before-and-after for a fictional stainless steel water bottle.
Before (supplier text, also on 40 other sites):
"Premium quality stainless steel bottle. Keeps water hot and cold. Leak proof. Best for office, gym and travel. Buy now at best price."
After:
Opening: "A 750 ml double-wall stainless steel bottle that fits a standard car cup holder and the side pocket of most office backpacks. Keeps drinks cold for roughly a working day in our own testing; the steel cap seals for carrying on its side."
Bullets: food-grade 304 stainless steel inside (state only if the supplier's test certificate confirms it); powder-coated exterior that does not sweat; wide mouth fits ice cubes and a cleaning brush; steel cap, no plastic touching the drink.
Spec table: capacity, height, diameter, weight empty, materials, dishwasher safety, warranty.
Details: hand-wash recommended to protect the coating; not suitable for carbonated drinks (pressure builds up); what is in the box.
Notice that every line answers a question, two lines prevent likely complaints, and the temperature claim is qualified because it depends on conditions. If you cannot verify a figure such as "hot for 12 hours", do not print it.
Common mistakes to avoid
- Writing descriptions after the store is built. The template, attributes and feed depend on decisions about content. Plan them in the brief.
- One template for every category. Furniture and cosmetics need different fields.
- Store policies typed into every product. They go out of date. Link to the policy page.
- Unverifiable superlatives. "Best", "No. 1", "guaranteed". Remove them unless you can prove them.
- Copying competitors' descriptions. As well as the search problem, it can infringe their copyright.
- Ignoring marketplaces. If you also sell on marketplaces, consider writing different, shorter copy there so your own store has the fullest version.
- Never updating. A description that contradicts the product now in the box drives returns and bad reviews.
How Govindani helps with product content
We build WooCommerce, Shopify and custom stores with product templates designed around the content: category-specific attributes, spec tables, size-guide blocks, product FAQs, feeds that match the page and bulk editing for catalogue teams. Where clients want help with copy, we work from their product data and their own staff's knowledge rather than supplier text. If you are planning a new store or want to fix descriptions on an existing one, see our ecommerce website development service, our SEO service, or contact us and call 092019 58274.
Frequently asked questions
How long should a product description be?
As long as it needs to be to answer the buyer's questions. A simple accessory might need 80 to 150 words plus a spec table; a high-value or technical product may need 300 words or more, with dimensions, materials and care. Focus on answering questions rather than hitting a word count.
Can I use the manufacturer's product description?
You can, but it rarely helps. The same text appears on many other sites, so Google usually shows a bigger or older page instead of yours. Use the manufacturer's facts and specifications, then write your own opening, benefits and practical details.
Do product descriptions help SEO?
Yes. Unique, specific descriptions give search engines text to understand the product and match it to searches, and they help shoppers decide, which supports conversions. Copied or very thin descriptions give Google little reason to rank your page over others.
Is it okay to use AI to write product descriptions?
Using AI to draft is acceptable if a person checks the facts and adds real detail. Publishing large volumes of unreviewed, generic AI text adds little value and can fall under Google's scaled content abuse policy. Always feed the tool real product data and verify every claim before publishing.
Should every colour or size have its own product page?
Usually not. One product page with variants for colour and size keeps descriptions unique and avoids near-duplicate pages. Create separate pages only when there is genuine separate search demand and you can write distinct content for each.
Sources:
- Google Search Central: Creating helpful, reliable, people-first content
- Google Search Central: Spam policies (keyword stuffing, scaled content abuse)
- Google Search Central: Guidance about AI-generated content
- Google Merchant Center: Product data specification (description attribute)
- Google Search Central: Product structured data
About the author: written by the Govindani Infotech ecommerce team in Pune, who build WooCommerce, Shopify and custom online stores, including product templates, catalogue structures and Merchant Center feeds for Indian D2C brands and retailers.