Start with page ownership
Before writing, name the page that currently owns the user job. If the answer is unclear, the next task is an inventory, not a new draft. Record each relevant URL, its primary promise, the evidence it contains, and the action it asks the reader to take.
This simple step exposes most collisions. Two pages with different titles can still compete when both help the same person make the same decision.
The page threshold
A strong candidate can answer yes to the following questions without relying on keyword wording alone.
- Would a reader arrive with a different goal from the parent page?
- Can the page make a complete promise instead of repeating an introduction elsewhere?
- Is there primary, firsthand, or observed evidence available now?
- Does the page have a clear parent, proof link, and next step in the site journey?
- Can someone own its accuracy and maintenance cadence?
Reasons to keep the topic as a section
Keep the topic inside an existing page when it answers a supporting question, uses the same evidence, shares the same next action, or would be too thin without repeating its parent. A section can still be substantial. It simply remains accountable to one stronger page promise.
A search phrase appearing to be specific is not enough. The useful distinction is the job, proof, and journey behind the phrase.
Reasons to stop altogether
Sometimes the current page already answers the job with credible evidence. Sometimes the branch is interesting but irrelevant to the site's audience. Sometimes no one can maintain the source material. In each case, no page action is a defensible outcome.
Recording that decision prevents the same weak idea from returning to the backlog under a new title a month later.