Audit whether a page answers its question directly
Use when a page targets a question but you suspect the answer is buried.
Fill in before running
Replace each placeholder with your own detail. The more specific you are, the less the model invents.
- {{QUESTION}}
- {{PAGE_TEXT}}
Getting a better result
- If the closest answer sits past 40 percent of the page, that is usually the whole problem.
- Run the audit again after editing to check the score moved for the right reason.
- Keep the replacement block as plain paragraph text; assistants lift prose more reliably than styled callouts.
Questions about this prompt
When should I run this rather than extracting citable claims?
When a page was built for one specific question and you suspect the answer arrives late. Claim extraction tells you what is quotable anywhere on the page. This is narrower: it asks whether {{QUESTION}} is answered at all, and how far down a reader has to go before anything resembling an answer appears.
What do I need in front of me?
The target question worded as a reader would type it, and the full page text including the preamble you are tempted to trim. The position figure in step one is a percentage through what you pasted, so cutting the introduction beforehand hides the exact delay the audit exists to measure.
What does it give me back?
The closest passage quoted with its position on the page, five scores out of five, a plain yes or no, a ranked list of remaining sub-questions and a replacement block of 60 to 90 words. The position figure is the finding. Anything past forty per cent usually explains the whole result.
What is the mistake that costs me?
Placing the replacement block under the H1 and leaving the original buried answer where it sits. Two answers to one question compete, and the lower one often carries older wording. Move or delete the old passage, then rerun and check the directness score moved for that reason rather than by luck.