Writing for the Reader, Scoring for the Tool
Using the content score as a checklist at the end rather than a target while drafting.
What it is for
Writing towards a content score produces text that scores well and reads badly. Write for the reader, then use the score at the end as a checklist of what you genuinely forgot.
The skill
The score measures overlap with what already ranks. Chasing it while drafting produces text that reads like the average of page one, which is exactly what does not outrank page one. The order that works: 1. **Take the term list, ignore the score.** Read the terms as a checklist of subtopics the reader expects covered. That is the genuinely useful output — a gap analysis, not a quota. 2. **Write the piece for someone with the problem.** Include the terms where they belong; skip any that do not. 3. **Score at the end.** Now look at what is missing. For each missing term, ask one question: *is this a subtopic I skipped, or a synonym I already covered?* Add a section for the first. Ignore the second — a paragraph inserted to raise a number is visible to a reader and adds nothing for a search engine either. Two things the score cannot see and that decide the outcome anyway: - Whether the first 100 words answer the query. Most competing pages do not, and that is the opening. - Whether anything on the page is first-hand. Numbers you measured, screenshots you took, a mistake you made. It is the only part that cannot be regenerated.
How to install it
1. Open the tool and start a new conversation, project or template. 2. Paste the text below wherever the tool keeps standing instructions — usually called system prompt, instructions, or persona. 3. Save it so it applies to every run rather than a single message.