TL;DR
- Collect the questions that delay real buying decisions, not just phrases with search volume.
- Group questions by the choice and proof they need. Similar words can hide different needs.
- Update an existing page when it can answer the question. Create a new page only when the reader needs a distinct explanation.
- Write one evidence-ready brief before building a content calendar. Fix the source facts before asking a writer to explain them.
Why start with a buying decision?
Begin with a choice the buyer needs to make, not a headline statistic about AI adoption. Large language models (LLMs) can be part of research, but the brief still needs to specify the reader’s unanswered question.
Start with the choice a buyer is trying to make. “Industrial water treatment” is a topic. “Can we reuse wash water without harming final rinse quality?” is a decision question. The second shows which limits, facts and proof to explain.
Link that question to facts you can prove, a page and a next step. More posts alone may leave the buyer stuck.
How do you find questions worth answering?
Review recent sales calls, quote requests, support tickets and lost-deal notes. Use records you have permission to access. Strip names, contact details and private project facts before sharing notes with a writer or outside tool.
Keep the buyer’s wording and note what happened next. Did the gap delay a quote? Did it rule out the service or require an engineer? Use that context to tell real barriers from mere curiosity. Search tools can add ideas. Your own records show where buyers got stuck.
Group the questions by the decision they support. “Water reuse cost” could mean the purchase price, running costs or a sample test fee. A hub page can cover all three. Each still needs its own facts.
Use this decision map before assigning a format:
| Buyer decision | Question to capture | Useful content home |
|---|---|---|
| Recognize the problem | What makes our current setup unsuitable? | Problem guide |
| Compare approaches | Which option fits our process constraints? | Comparison page |
| Check feasibility | What must you know before recommending a system? | Application page |
| Reduce risk | What evidence would validate the proposed solution? | Testing guide or documented case |
Choose a content home before creating a URL.
Question mapping does not mean one question per page. Update the service page when the missing answer concerns the offer itself. Expand a section when related questions need the same evidence and next step. Create a standalone resource when the decision requires a distinct explanation that would overwhelm the parent page.
| Situation | Content choice | Example |
|---|---|---|
| Core scope or required inputs are missing | Update the existing service or application page | What must the plant provide before a feasibility review? |
| A narrow follow-up belongs with an existing answer | Add a section or useful FAQ | Can the team assess a site before a sample is available? |
| Buyers must compare genuinely different options | Use a comparison if the team can support both sides | What assessment criteria distinguish two treatment approaches? |
| A distinct decision needs a substantial explanation | Create a guide and link it from the relevant service page | How to prepare evidence for a reuse feasibility study |
Which questions deserve a place in the plan?
Plan both the answer and its proof. A guide can explain the choice. A test, case or third-party review can help buyers check the claims. That is our advice, not a forecast of sales gains.
Sort each question into three queues. Write now if buyers need the answer and its facts are approved. Gather proof if the question matters but the answer lacks support. Hold if the topic is outside your scope or has no clear use. A writing task should not hide a choice the business has yet to make.
If two topics are ready, pick the one tied to delays or costly mistakes in your records. Note why it comes first. Do not dress guesses up as a “GEO opportunity score.”
What does an evidence-ready GEO brief look like?
Worked example — a fictional water-treatment supplier needs its next topic. Buyers ask whether they can reuse wash water. A broad post on recycling benefits would not answer what must be checked at their plant.
The editor gathers call notes with private details removed, a sample checklist and an approved pilot-test outline. These show how the review works. They cannot prove a savings figure or that water reuse works at every site.
The transformation is: broad water-reuse topic → a buyer’s rinse-quality question → process-specific decision conditions → approved sampling and pilot evidence → a revised application page → a scoped feasibility conversation. This example does not establish actual engineering suitability.
The brief now has a clear job:
| Brief field | Completed illustrative entry |
|---|---|
| Reader / role | Plant engineer considering whether to commission a water-reuse study. |
| Buyer’s exact question | “Can we reuse wash water without harming final rinse quality?” |
| Decision to complete | Decide whether to request a scoped feasibility review and what to prepare. |
| Existing page | The supplier’s current water-reuse application page; use its real URL in a live brief. |
| Knowledge gap | The page describes benefits but omits assessment inputs and test conditions. |
| Answer boundary | Explain how suitability is assessed; no untested suitability verdict or savings promise. |
| Required evidence | Approved sampling checklist, process constraints and pilot acceptance criteria. |
| Evidence owner | Process engineer responsible for the approved assessment materials. |
| Format | Expand the application page with an input table and a linked assessment guide only if needed. |
| Main sections | What the study can answer; required inputs; how tests are scoped; what happens next. |
| Approver roles | Process engineer checks technical facts; service owner checks scope and contact expectations. |
| Body links | Current feasibility-review service scope and an approved sample-assessment checklist, if publishable. |
| Appropriate call to action | Request a review of the project inputs to agree the assessment scope. |
| Publication acceptance | Claims match approved records; required inputs are visible; links and the stated contact route work. |
| Follow-up check | Review recurring sales questions and a stable answer sample; record changes without promising attribution. |
Use the eight dimensions to catch missing answers
SignalFoundry’s eight-dimension service-page framework provides a useful review lens: fit, scope and inputs, deliverables, responsibility, evidence, cost and timing, findability and actionability, and inquiry delivery. Here we use it to check a brief, with credit to SignalFoundry.
For this brief, scope and inputs raise a question: what must the plant send first? Evidence raises another: which records back the method? Use those two checks where they help. There is no need to turn each topic into a full page audit.
Ask the engineer to fill the gaps before drafting. Then let a fresh reader name the inputs and explain why tests are needed. If they expect a promised saving, change the draft. This checks what readers grasp, not a sales gain.
Copy these fields for your next brief.
Replace the instructions with approved project facts. An unresolved field is a task for the named owner, not permission for a writer to invent an answer. Copy the field list into your working document; the full example is visible above.
| Field | What your brief must record |
|---|---|
| Reader / role | Who reads this and their responsibility. |
| Buyer’s exact question | The original question, with private details removed. |
| Decision to complete | The choice the answer should help them make. |
| Existing page | Actual URL and relevant section, or why a new page is needed. |
| Knowledge gap | What the current material cannot answer. |
| Answer boundary | What may be stated and what requires further assessment. |
| Required evidence | Named approved records, dates and permission to publish. |
| Evidence owner | Who supplies and resolves disputed facts. |
| Format | Existing-page update, section, comparison, guide or FAQ. |
| Main sections | Headings that answer the decision’s subquestions. |
| Approver roles | Who approves facts, scope and publication. |
| Body links | Verified destinations and the reason for each link. |
| Appropriate call to action | The useful action the buyer can take next. |
| Publication acceptance | Observable content, evidence, access and link checks. |
| Follow-up check | Review date, questions to repeat and business observations. |
How do you know the plan is doing its job?
Before publication, match every factual claim to the approved evidence and confirm the scope with its owner. Check that a fresh reader can identify the required inputs and next step. Read the actual page and links after release; a saved draft is not the published output.
Check if sales can use the page and if the same questions still delay quotes. Use a stable measurement protocol for answer observations. Fit the brief into the broader GEO execution plan without turning each article into a full strategy.
Use what you learn in the next brief. If your topic list has no clear link to buyer needs, review SemShift’s GEO strategy and optimization scope.