Page section order and argument flow
Use when a long page has all the right sections but they arrive in the wrong order.
Fill in before running
Replace each placeholder with your own detail. The more specific you are, the less the model invents.
- {{SECTION_ORDER}}
- {{PRIOR_KNOWLEDGE}}
- {{BUYER_QUESTIONS}}
- {{SCROLL_DATA}}
Getting a better result
- Take the buyer question order from sales calls rather than from what the page currently implies.
- Price usually needs to arrive earlier than marketing wants and later than the visitor wants; argue it with data.
- Move sections before you rewrite them, since order changes what each section still has to do.
Questions about this prompt
When do I reorder rather than rewrite the sections?
When a long page has the right sections arriving in the wrong order and the instinct is to rewrite the copy. Order changes what each section still has to do, so move first and rewrite afterwards. It deliberately leaves the copy inside sections alone, which keeps the argument about sequence rather than about wording.
What do I need in front of me before running it?
One line on each section in its current order, what the visitor already knows on arrival, the buyer questions roughly in the order they get asked, and scroll depth if you have it. Take the question order from sales calls rather than from what the page implies, or you will simply confirm the existing order.
What comes back, and which part is worth acting on?
A position table, the sections answering questions nobody has asked yet, questions no section answers, the full recommended order with a reason for each move, and a scroll depth read. Point two is the main failure mode and the part to act on, since each entry names the earlier section that has to land first.
What is the mistake that costs me here?
Assuming a cold visitor when the traffic is warm. The right order differs, and the prompt follows what you put in prior knowledge rather than a default. Where price should sit is genuinely arguable, since marketing usually wants it later and the visitor wants it sooner, so settle that with scroll and exit data rather than taste.