A product page serves two readers at once. The first is a shopper who hesitates, compares and looks for the one precise answer that will make up their mind. The second is a set of machines: the search engine that has to understand the page, the comparison service reading the feed, the conversational assistant looking for a fact to cite. A good product page satisfies both without sacrificing one to the other, and that depends less on writing talent than on method.
Here is that method, in the order it applies, from the first document you open to the final review.
Gather the information before writing a line
Most weak product pages are weak before the writing even starts: someone began typing without knowing exactly what they were selling. The first step is therefore to build the product file.
That file brings together the supplier’s spec sheet, the manufacturer’s page, photos of the packaging and label, user manuals, as well as identifiers (manufacturer part number, EAN code). For a product the store makes itself, it means the internal specifications: materials, dimensions, process, care instructions.
From this file, you draw up the list of established facts, each with its source. Anything that is written nowhere does not go on the page. This discipline also has a legal basis in some markets: in France, article L111-1 of the Consumer Code requires sellers to disclose the essential characteristics of the goods before the contract is concluded, and consumer protection rules in the US and UK make similar demands about accurate product claims. The product page is the first place where that obligation plays out.
The last item in the file: what buyers are looking for. Pages already ranking well for the query, questions sent to customer service and reviews left on comparable products reveal the information shoppers expect, but also the vocabulary they actually use.
The product title
The title is the most-read element on the page, by customers and by Google alike. It must identify the product without ambiguity, which generally means four components: the brand, the product type, the model, then the characteristic that sets this SKU apart from its siblings (capacity, color, power, vintage).
Compare “Elegance Insulated Bottle” with “Aldérane Cime Stainless Steel Insulated Bottle 750 ml, Glacier Blue.” The second title answers the customer’s questions in advance and matches the precise queries typed by a shopper who already knows what they want.
The name displayed on the page and the title tag can differ: the latter often adds the store name or a key benefit. Google sets no length limit on the title tag but truncates the title shown in results according to screen width, so the essentials must come first. Google’s main insistence is on a distinct text for every page: identical titles from one SKU to the next prevent users from telling them apart.
The short description
In WooCommerce, the short description appears next to the price and the add-to-cart button. This is where the customer decides whether to keep reading. Two to four sentences, or a short list of key points, are enough: what the product is, who it is for, what makes it different.
Every claim must be concrete. “Keeps drinks cool” says nothing. “Keeps a drink cold for 24 hours, according to the manufacturer’s tests” is informative, provided the spec sheet says so.
The long description
The long description develops what the short description announces. It is rarely read in full; it is scanned. So structure it with subheadings that match the customer’s questions: use, materials, care, compatibility, what is in the box.
The guiding principle is to translate each feature into a consequence for the user. A double-wall stainless steel body interests no one in itself; the fact that the bottle does not sweat inside a bag does. The feature supplies the proof, the consequence supplies the reason to buy.
As for length, it cannot be decreed. A USB cable does not need eight hundred words; a mattress calls for more. The right measure can be read in the pages already ranking for the query: match their level of coverage, then add what they lack. This approach is detailed in our article on writing product pages with AI.
Finally, the description must belong to the store. Supplier copy, reused word for word by every reseller, brings nothing to a search engine that already knows the original. The issue is covered in our article on duplicate content.
Specifications and attributes
A spec table complements the description without replacing it. It serves the customer comparing two SKUs: dimensions, weight, materials, capacity, compatibility, warranty.
In WooCommerce, these specifications should be entered as attributes rather than left in the text alone. A global attribute powers the store’s filters, the Google Shopping feed and the structured data, whereas a value buried in a paragraph only serves reading. The difference between global and custom attributes is the subject of a dedicated article.
Identifiers belong here too. The GTIN, often called the EAN or UPC, goes into the field WooCommerce provides for it and directly affects visibility in Google Shopping: see our guide to EAN and GTIN codes.
Images
Photos convey what text cannot: appearance, scale, texture. An effective set combines a main view on a neutral background, detail shots, a lifestyle photo that shows scale, and the packaging when the customer receives it as is.
Every image deserves alt text that describes what it shows, for screen readers first and for search engines second. Our article on alt text lays out the rules.
The information that removes the last doubts
At checkout time, the customer looks for practical answers: delivery time and cost, return policy, availability, warranty. This information must be reachable from the product page without forcing anyone to open the terms and conditions.
A short FAQ can group the questions specific to the product: “Is it dishwasher safe?”, “Is the replacement cap sold separately?” It has value when it reflects questions actually asked, far less when it paraphrases the description.
Customer reviews round out the whole. They are not written by the store, but their presence is prepared: a visible slot, a request after delivery, public replies to critical reviews.
The SEO side of the product page
Ranking a product page relies on a few precise elements rather than on keyword density.
- The target query: one main phrase, the one the buyer actually types, placed in the title, in the first sentences of the description and in the URL.
- The title tag and meta description: unique for each product. Google sets no maximum length for the meta description and only displays it when it describes the page better than the content itself; it remains an opportunity to summarize the offer. See our meta description guide.
- Product structured data: it describes the product, its price and its availability in a format Google reads directly. Our article on structured data details what WooCommerce outputs by default.
- Internal linking: links to the category, complementary products and buying guides.
Review before publishing
Reviewing a product page is first about facts, then about style. A short checklist is enough.
- Does every number, material, origin or certification appear in a source from the product file?
- Does the title identify the exact SKU, variant included?
- Are the attributes filled in, in the right format, and consistent with the text?
- Do the price, availability and GTIN on the page match those in the feed?
- Does the text avoid unsupported superlatives and boilerplate repeated from one page to the next?
For points that go beyond the product page itself, this checklist connects with our WooCommerce SEO checklist.
Going from ten product pages to a thousand
Applying this method to ten products takes care; applying it to an entire catalog takes a tool. That is the purpose of Fichewise, a WooCommerce plugin that builds each product’s file from verified sources, writes the complete product page, then submits it to a factual review before your approval. It is licensed and runs either on your own API keys (the cost is then limited to that of the API, around €0.25 per product page) or through the managed service with credit packs, with no key to manage; prices are on the pricing page. The Features page describes each of these steps.