What a product page has to do. The lesson covers the ten parts every product page is built from, where each one sits on a desktop screen and a phone, the four jobs a page does and the six kinds of question buyers bring to it. You then copy your own page out, part by part, into pdp-teardown-notes.md and see what is there and what is missing.
How to score your page out of 10. Each of the five pillars, result clarity, time expectation, objection coverage, trust signals and action guidance, scores 0, 1 or 2, and every score needs a quote from your page. You learn the caps that hold a score down and what the total says: fix lines, or rework the page. The scored audit is saved as pdp-teardown.md.
How to turn the audit into fixes. Every fix is typed as PUBLISH, REWRITE or DECIDE and ranked by how many buyer questions it answers. You then write the top three, with a source tag on every sentence, and run the checks that keep delivery, returns and review lines within your policy. The ranked fixes and rewrites are saved as pdp-rewrites.md.
The six prompts from the SOP & AI Prompts pack, run in order in one Claude conversation on one of your own product pages. They copy the page out part by part, score it on the five pillars with a quote behind every score, rank the fixes and write the top three rewrites with a source on every sentence. You leave with all three files saved.