In short: An assistant asked for a product recommendation is answering a question about fit, not about specifications. Most product pages carry the specifications and nothing that answers fit.
The sentence that gets a product named is the one that says who it is for, what it works with, and who should buy something else. Almost no store has it in text.
This is an editing job on the twenty products that carry your revenue, not a rebuild of the catalogue.
The Question A Buyer Actually Asks
Nobody asks an assistant for a list of dimensions. They ask whether a thing will work for their situation: a flat with no drill, a machine from 2019, a team of four, a kitchen with a specific fitting.
Answering that requires a judgement, and a judgement needs a source. A page that lists 14 attributes and a marketing paragraph gives a system nothing to quote, because nothing on it says what the attributes mean for a person.
The test: read your product page and try to answer, from the page alone, "would this work for me if I have X". If you have to already know the category to do it, so does the system, and it will use a page that does the work instead. That page is often a forum thread.
Three Sentences Most Pages Are Missing
Who it is for. Stated as a situation rather than as a persona. "Fits standard 15mm copper pipe" is a fit statement. "Perfect for home improvers" is not, because it excludes nobody and answers no question.
What it works with. The models, sizes, standards or systems it is compatible with, named individually. This is the single most retrievable kind of sentence on a product page, because compatibility questions are the most common shape of buying question and they have checkable answers.
Who should buy something else. The most uncomfortable and the most effective. A page that says this product is wrong for a particular case is a page a system can use to answer safely, and the sentence costs you a sale you were going to lose to a return anyway.
Specifications Are Not The Answer, But Keep Them
A table of attributes is genuinely useful and reliably reproduced in generated answers, which is why it belongs in a table rather than in prose.
The mistake is treating it as sufficient. Specifications support the answer and are not the answer, in exactly the way a heading supports a section without being it. Keep the table, and put one plain sentence above it that says what the table means.
Reviews, And Where They Actually Help
Review text is the only material on a product page that is not written by the seller, which is what makes it useful to a system trying to answer a question about fit.
Two practical consequences. Reviews that arrive through a script are frequently absent from the initial HTML, so check whether yours are in the response rather than assuming. And never seed them, because a fabricated review is the one failure here that is both detectable and fatal to everything else on the domain.
The uncomfortable implication of The Role of Citations and Sources: a heavily cited community site discussing your product can be worth more than your own product page. That is not an argument to stop improving the page. It is an argument that being present and accurate where your category is discussed is product work rather than a separate marketing activity.
Where To Spend The First Week
- List the ten questions a buyer asks before choosing in your category. Compatibility, sizing, suitability, and what goes wrong.
- Take the twenty products that carry most of your revenue.
- For each, write the three sentences: who it is for, what it works with, who should buy something else.
- Put them above the specification table, in the page body rather than in a tab.
- Ask your ten questions on three assistants and record whether you are named, before and after, with the dates.
That last step is the part that gets skipped and the only one that tells you whether any of it worked.
Key Takeaways
- Buying questions are about fit rather than specifications, and most product pages answer only the second.
- Three sentences are usually missing: who it is for as a situation, what it works with named individually, and who should buy something else.
- Compatibility statements are the most retrievable content on a product page because the questions have checkable answers.
- Keep specification tables. They are reliably reproduced, and they support an answer rather than being one.
- Check that review content is in the initial HTML, and never seed reviews.
Check yourself
Before you move on
Not scored, not recorded, and not part of the certificate. Both answers are settled by a sentence in this lesson, and the reasoning appears whichever option you pick.
- 01
Why does a complete specification table often fail to get a product named in an answer?
- 02
Which of the three missing sentences is described as the most uncomfortable and the most effective?