SEO product descriptions: how to write them, with examples

Someone who types a product search usually knows what they want and is comparing options. They search for a product type plus a qualifier: 'insulated water bottle 750 ml', 'trail running shoes wide fit', 'M8 stainless steel bolts'. Your description has to confirm, within a few seconds, that this page is that product.

Pick one main phrase per product page, the way a shopper would say it, and a handful of supporting terms: synonyms, the brand and model, and the attributes people filter on. Search Console shows which queries already bring impressions to a page, which is often a better source than a keyword tool for products you already sell.

Most shoppers scan before they read. A fixed structure helps them find the one fact they need, and it makes descriptions easier to write consistently across a catalog. Vendor research points the same way: in Salsify's 2024 consumer research, 42% of shoppers said bad product titles and descriptions are enough to abandon a cart.

When fifty shops publish the manufacturer's description word for word, Google sees fifty near-identical pages. Its documentation on duplicate URLs explains that it picks one version to show; it does not describe a penalty, but your page has no reason to be the one it picks.

Google's spam policies go further for content copied from other sites without adding value, including text that has only been lightly reworded. Its guidance on helpful content asks whether a page adds original information. For product pages, original means facts and context the supplier text lacks: how the product is used, who it suits, what it is compatible with, and the questions your customer service hears.

Use the manufacturer's data as input, not as output. The specifications are usually right; the prose is usually generic. Keep the facts, rewrite the text.

The title element and the meta description decide how your page looks in the results. Google's title link guidance sets no length limit, but titles are truncated to fit the screen, so put the product name and main phrase first. It asks for a unique, descriptive and concise title per page, without keyword stuffing or repeated boilerplate.

For snippets, Google mostly uses page content and sometimes the meta description, when that describes the page better. Again there is no fixed length. Write a unique meta description per product with the details a shopper weighs, such as the key spec and price, and preview it in the SERP snippet preview or draft it with the meta description generator.

Product structured data tells Google the name, price, availability and ratings in a form it can read. Google's product snippet documentation lists what that markup can show, and pages where shoppers can buy are covered by the merchant listing documentation, which requires a name, an image and an offer with a price. Build and check the JSON-LD with the product schema generator, and keep the price and stock in the markup equal to what the page shows.

The product below is invented, but the 'before' column is typical of supplier data. The rewrite keeps every fact and changes the order, the wording and what is explained.

Writing by hand works for fifty products. With five thousand, you need a repeatable process: a template per category, complete product data to write from, and a review step before anything is published. AI can draft the text, but it can only state facts that are in the data, so fill the specifications first. Google's helpful content guidance treats large volumes of AI text with no human review as low effort, so keep a person in the loop and check a sample of every batch.

Prioritize. Start with the pages that already get impressions in Search Console but few clicks, and with the best sellers whose descriptions are still supplier text. Then move category by category, so each template is tested on real products before it runs on the rest. The free product description generator is a quick way to see what a first draft looks like.

Run through this list before you publish a description, or use it to audit the descriptions you already have.