Product descriptions for SEO: unique, useful, written for the buyer

The manufacturer’s text appears on hundreds of stores. Google has seen it. Your page adds no value if you paste it as is.

Write for the buyer first. They want to know if it fits, works in their setup, arrives with what they need, and how it compares to similar items.

Search learns from users. A useful description wins clicks, dwell time and links. That helps you across Search, Images and the Shopping tab as of 2026.

• Who it is for: the use case, the level, the context. Example: “For home bakers who need even heat in small ovens.”
• What it does in plain words: avoid jargon unless your buyers use it. Example: “Keeps coffee hot for 6 hours without leaking.”
• Sizes and fit: give measurements in common units and a size guide link. Example: chest width in cm and inches.
• Materials and care: what it is made of, where, and how to look after it.
• What is in the box: list every item and cable. If batteries or adapters are not included, say so.
• Compatibility and requirements: devices, standards, mounts, power, region.
• Variants: colours, capacities, finishes. Link the options, one image per variant.
• Delivery and returns: shipping timeframes, return window, restocking rules if any.
• Safety and compliance if relevant: certifications and warnings.
• Support: warranty length, setup guide, and a contact link.

If you sell software, swap sizes for plans and limits. Example: seats, usage caps, integrations, and what happens at renewal on /products/team-plan.

Split the page with headings. Keep the pitch short above the fold. Put full detail below. Use a table for specs buyers compare at a glance.

• H1: the product name and key qualifier. Example: “Aurora Linen Shirt, Regular Fit”.
• Intro, 2 to 4 lines: who it is for and why it is different.
• Bullets: top 4 to 6 benefits in buyer language.
• Specs table: dimensions, weight, materials, power, ports, care.
• Sections with H2s: “Sizing and fit”, “What’s in the box”, “Delivery and returns”, “Care and repair”, “Compatibility”.
• Images: one clear photo per variant with alt text that names the colour or finish.
• Reviews: show real reviews and an aggregate rating on the product entity in structured data.

A fixed page looks like this: /products/travel-sling has a short intro, four bullets, a table as above, then sections for care and returns, with images for each colour option.

There is no word count that ranks on its own. Write enough to answer the buyer without padding. Cut filler adjectives. Keep nouns and facts.

• Above the fold: 80 to 120 words that say who it is for and what it does.
• Bullets: 4 to 6 crisp lines.
• Specs table: as long as needed, but only real specs, no fluff.
• Below the fold: sections that answer the questions you see in support and Search Console.
• Avoid walls of text: break long answers with short subheadings.

Keep one URL per product. Variants share the product URL and switch content on the page, or use their own URLs when a variant has demand in search.

• If a variant has clear search demand, give it a URL and its own images and copy. Example: /products/aurora-shirt-blue-regular.
• If variants stay on one URL, keep the canonical on the product URL and update structured data to show the selected offer, price and availability.
• If you split variants onto URLs, canonical each to itself. Cross link them, and use consistent parameter names if you must use parameters.
• Avoid infinite filter combinations. Make only the few facet URLs with demand indexable and keep the rest out with robots.txt or noindex as needed.

On Shopify, /collections/handle/products/handle points to /products/handle with an automatic canonical. Do not fight it. Link to /products/handle in menus and emails to keep signals clean as of 2026.

1. 1

   Pull real questions

   Open Search Console. In Performance, filter to /products/. Export queries for a product. Add support tickets and returns reasons. Note themes by intent: sizing, compatibility, in-the-box, delivery.

2. 2

   Draft the top section

   Write 2 to 4 lines that say who it is for and what it does. Avoid slogans. Name the key differentiator. Example: “Regular fit linen shirt that keeps its shape after 30 washes.”

3. 3

   Write 4 to 6 bullets

   Benefits, not features. One clause each. Start with verbs buyers use. Example: “Dries fast after a beach swim.”

4. 4

   Build the specs table

   List only specs buyers compare. Use common units. Convert where helpful. Include care, warranty and compliance if relevant.

5. 5

   Add missing facts

   What is in the box, delivery timeframes, returns, support. Link to full policies. Keep it short on the page, detail on policy pages.

6. 6

   Map keywords without stuffing

   Use the main product name in the H1 and title. Use natural terms buyers used in your query list in headings and bullets. Do not repeat for the sake of it.

7. 7

   Images and alt text

   One image per variant. Alt text that names the variant and key attribute. Example: “Aurora shirt in blue, regular fit, front view”.

8. 8

   Structured data

   Add Product structured data with offers, price, availability, reviews if you have them. Ensure the data matches what is visible on the page.

9. 9

   Internal links

   Link to relevant categories and comparison pages. Example: “See all Regular Fit Shirts” and “Compare Regular vs Slim Fit”.

10. 10

    Publish and measure

    Ship. In 28 days, check Search Console for impressions, clicks and queries. Adjust the copy to answer new questions you see.

A fixed page looks like this: /products/aurora-linen-shirt uses “Aurora Linen Shirt, Regular Fit” in the H1 and title, bullets speak to breathability and fit, and the specs table lists fabric, weight and care, with a clear size guide link.

Example product: /products/aurora-linen-shirt. Variant: blue, regular fit. The manufacturer’s text says little about fit, care or what you receive.

Before

Aurora Shirt is made of premium linen for superior comfort and style. Designed for everyday wear with exceptional craftsmanship. Available in multiple colors.

After

Aurora Linen Shirt, Regular Fit
Breathable 100 percent linen that keeps its shape after 30 washes. Cut for everyday wear, not tight, not baggy. For warm days and travel.

Top features
• Stays cool in summer, dries fast after a beach swim
• Holds colour after repeated washes, no sheerness
• Regular fit with room in the chest, straight hem you can tuck
• Sewn-in collar stays keep the collar sharp without ironing

Sizing and fit
Model wearing M. Check our size guide for chest width in cm and inches. If between sizes, take the larger.

What’s in the box
Aurora Linen Shirt in Blue, Regular Fit. Spare buttons. No garment bag.

Specs
• Fabric: 100 percent linen, 150 g/m²
• Buttons: Corozo, reinforced
• Care: Machine wash 30°C, line dry, steam to finish
• Origin: Cut and sewn in Portugal

Delivery and returns
Ships in 2 business days from our UK warehouse. 30 day returns, free exchanges.

The after version says who it is for, what it does, sizes, materials and what is in the box. It uses headings, bullets and a specs block. It reads like a page you would trust and share.

Google shows product data in many surfaces as of 2026. Search, Images, the Shopping tab, your Business Profile and free listings in Merchant Center all use your data in different ways. Keep them in sync.

• Structured data: add Product with offers, price, currency, availability and review properties if you have them. Images should be high resolution and set in the image property.
• Merchant Center: send a feed for free listings. The price, availability and identifiers in the feed must match what is on the page.
• Reviews: use an aggregateRating on the product. Do not mark up self-serving reviews. Show the reviews on the page users see.
• Images: provide alt text that names the product and the variant. Include one image per variant so users and crawlers can see colour and finish.
• Out of stock: keep the page live, set availability in structured data, and offer alternatives. If a product is gone for good, redirect to the closest match or the category, or return 410.

On Shopify, most themes include Product structured data. Check it with the Rich Results Test. Fix image alt text per image in the admin. Titles and descriptions are native fields per product and collection as of 2026.

New products need fresh data and buyer trust. Start with the basics. Ship, then measure and improve. Avoid scaled content that only rewrites the same pitch across pages.

• Track queries and clicks in the Search Console Performance report. Watch the new queries after 28 days. Add answers to those questions on the page.
• Refresh descriptions when returns or support show a trend. If many buyers ask for fit, move sizing higher and add a photo that shows it.
• If you use AI assistance, keep it human led. Drafts are fine. Publish only pages with facts you can verify, and that add value to your range.
• Do not generate hundreds of near-duplicate pages. That can fall under scaled content abuse as of March 2024. Build one strong page per product.
• When you remove a product, follow lifecycle rules. Keep returning products live and marked out of stock. Redirect permanent removals to the best alternative or category.

If you want a quick outside view, Porteur reads your site from a URL and shows three findings you can ship today. It takes about thirty seconds, and is free.