Audit a product page against buyer questions
Use before rewriting a product page, to find what information is missing rather than what reads badly.
Fill in before running
Replace each placeholder with your own detail. The more specific you are, the less the model invents.
- {{PAGE_CONTENT}}
- {{CATEGORY}}
- {{PRICE}}
- {{CUSTOMER_QUESTIONS}}
- {{RETURN_REASONS}}
Getting a better result
- Run this before any rewrite. Most underperforming product pages are missing facts, not adjectives.
- The filler list is usually a third of the page and deleting it costs nothing.
- Take the "data you would need" list to merchandising as a request, not to a writer as a brief.
Questions about this prompt
When should I audit rather than go straight to a rewrite?
Before the rewrite, not instead of it. The reflex on an underperforming product page is to commission better copy, and most of these pages are missing facts rather than adjectives. Run this first so the rewrite has something to say, and expect the result to be a data request rather than a brief.
What do I need to paste in?
The full page content as it stands, the category, the price, the questions customers actually ask and the recorded return reasons. Price matters because the question set for a twenty pound item is not the question set for a four hundred pound one. Return reasons are what drive the impact ordering.
What does the audit return?
Fifteen to twenty five buyer questions marked answered, partial or absent, sorted so anything in your return reasons ranks highest, the exact data needed for the top five, and a quoted list of filler. The filler list is usually a third of the page and deleting it costs nothing.
What ruins an audit run?
Asking it to write replacement copy in the same run. The audit only works while it is still allowed to say absent, and a run that produces copy quietly answers the gaps with invented material. Take the data list to merchandising as a request rather than handing it to a writer as a brief.