Product titles and descriptions

A store selling trail shoes lists every product under the supplier's model code, with the supplier's catalogue text as the description. The same words sit on every other retailer that stocks the shoe, so when someone searches for a waterproof trail shoe Google has dozens of identical candidates and no reason to pick the smallest store. A product page earns its place when its title says what a buyer would type and its description answers the doubt that stops that buyer adding to cart.

Three titles, one product

A product page carries a title tag (the text in the browser tab and usually in your Google result), a main heading, and the product name your platform stores. On most platforms the product name feeds all three, which is how the supplier's code ends up in your search result.

Google builds the title it shows, which it calls the title link, from several sources. Its title link documentation lists the title tag first, then the main visible heading, the text of links pointing to the page, and other prominent text. When the title tag is half-empty, repetitive, or the same boilerplate across many pages, Google replaces it from those other sources.

A pattern that holds up: what the product is, in the buyer's words, then the attribute buyers choose by, then the model and brand. "Women's waterproof trail running shoes, Ridgeline 3, by Summit Outfitters" front-loads the words a buyer types and keeps the model name for people who already know it. Google's documentation sets no character limit; it truncates titles to fit the device, so the identifying words go first and the store name last.

Use the buyer's words, not the catalogue's

Google ranks on whether a page's content matches the meaning of a search, and buyers rarely search in the manufacturer's vocabulary. The supplier calls it a "hydro-shield membrane system"; the buyer types "waterproof". The list you built in Product and category keyword research tells you those words for each product.

Two rules keep titles honest:

1. One product per page, one search per page. A product page competes for the specific product search ("Ridgeline 3 navy"); the collection page competes for the category search ("waterproof trail shoes"). Title the product page for the product and leave the category phrase to the collection, or the two pages fight. Which page catches which search explains the split.
2. Name the thing the way people ask for it, once. Repeating "trail shoes" three times in a title is the keyword stuffing Google's guidance says looks spammy to people and to Google alike.

Descriptions that answer the doubt

The manufacturer's text appears on every store that stocks the product. Google's documentation on consolidating duplicate URLs describes what happens next: near-identical pages get grouped, one is chosen to show, and the rest are folded into it. That is consolidation, not a penalty, but Google keeps whichever version it judges best, and a small store rarely wins that contest against the manufacturer and the big retailers. Copy the supplier's text and you volunteer to be the duplicate.

The fix is to write for the person who is close to buying and still hesitating. Every product has a short list of doubts: will it fit, will it last, is it right for my use, what is in the box, how does it compare to the model next to it. Answer those in plain language and the description is unique on its own, because nobody else has your answers.

A structure that works across categories:

1. Open with what the product is and who it suits, in one or two plain sentences. Google's snippet documentation says snippets usually come from page content, and this paragraph is the natural source.
2. Follow with the specifics a buyer compares: materials, dimensions, compatibility, care, as a short spec list rather than buried in prose.
3. Close with the doubts: sizing guidance, what it is not good for, what ships with it, and the sibling product to choose instead if this one is wrong.

Length is not the goal. Google's helpful content guidance says word count is not a ranking factor, and padding pushes the answer below the fold on a phone. Write what a good shop assistant would say, then stop.

The meta description is your pitch, not your ranking

The meta description is the short text under the title in a result. Google's snippet documentation says it sometimes uses it, when it describes the page better than the page text does, and otherwise writes the snippet from the page itself. It sets no length limit; snippets are truncated to fit the device. So the meta description is a pitch you might get to deliver, not a ranking lever.

Google's guidance for product pages is to put the facts a shopper wants in it, and its example includes price and manufacturer. Write one per product: what it is, the attribute that sells it, the price or price range, a shipping or returns fact if it matters. Never a list of keywords, and never the same sentence across the catalogue; Google's documentation calls out both.

What to take away

• Google builds your result's title from the title tag first, and replaces it when the tag is empty, stuffed, or boilerplate.
• A product title names the product in the buyer's words, front-loads the identifying attribute, and leaves the category phrase to the collection page.
• A description copied from the manufacturer makes your page a duplicate; one that answers the buyer's doubts is unique by definition.
• The meta description is a pitch Google may or may not show, so fill it with the facts a shopper wants, including the price.

Next

Titles and descriptions tell Google what the page sells; structured data tells it the price and the stock. Continue with Product schema and rich results.