# Page section order and argument flow

> Use when a long page has all the right sections but they arrive in the wrong order.

## املأها قبل التشغيل

- `{{SECTION_ORDER}}`
- `{{PRIOR_KNOWLEDGE}}`
- `{{BUYER_QUESTIONS}}`
- `{{SCROLL_DATA}}`

## البرومبت

```
You are checking the order of the sections on a long page. You are not rewriting the copy inside them.

SECTIONS IN CURRENT ORDER, ONE LINE ON EACH: {{SECTION_ORDER}}
WHAT THE VISITOR ALREADY KNOWS ON ARRIVAL: {{PRIOR_KNOWLEDGE}}
QUESTIONS A BUYER ASKS, ROUGHLY IN THE ORDER THEY ASK THEM: {{BUYER_QUESTIONS}}
SCROLL DEPTH DATA IF AVAILABLE: {{SCROLL_DATA}}

Produce:
1. A table: Position | Section | Question from {{BUYER_QUESTIONS}} it answers | Question it assumes is already answered | Verdict (keep here, move earlier, move later, merge, cut).
2. Every section that answers a question the visitor has not asked yet. This is the main failure mode, so name each one and say which earlier section has to land first.
3. Any question in {{BUYER_QUESTIONS}} that no section answers, and where it belongs.
4. The recommended order in full, with a one line reason for each move you made.
5. Given {{SCROLL_DATA}}, which sections almost nobody reaches, and whether the fix is moving them up or cutting them.

Constraints: work from {{SECTION_ORDER}} as given and do not invent sections. Do not assume a cold visitor if {{PRIOR_KNOWLEDGE}} says otherwise, since the order for a warm visitor differs. Where {{SCROLL_DATA}} is missing, mark point five unavailable rather than guessing depth. No em dashes.
```

## كيف تحصل على نتيجة أفضل

- 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.

---

من مكتبة برومبتات QuQi - https://www.quqi.io/ar/prompts/page-section-order-argument-flow