The playbook
Keyword Research: Worked Examples
The following keyword research examples illustrate how to move from an observed problem to a practical decision. They are hypothetical operating scenarios, not customer results or performance benchmarks. The central question is whether the work helps improve qualified organic visits without losing the context needed to judge it.
Put the task in context
Compare “CRM software” with “CRM implementation checklist.” The first may call for product evaluation, while the second calls for an operating resource. Capture country, language, date, and data provider beside volume estimates. Do not add close-variant estimates together as though they represent entirely separate audiences.
Example 1: establish a usable starting point
A team begins working on keyword research but cannot consistently describe query and intent for the same item. The immediate task is collect queries from customer questions and Search Console. The team records the current state, identifies the source of each value, and resolves conflicting information before making a broader change.
The useful output is a page or query record that another person can interpret. This example does not require assuming an uplift. Success at this stage means the next decision can be made using a shared set of facts, with missing information explicitly identified.
Example 2: correct a specific failure
In a second situation, the team observes picking phrases solely because they have a large search estimate. It proposes the correction: compare the query intent with the offer and the page a visitor expects. Before applying that correction everywhere, the owner checks whether the same cause is present in other affected items. A common symptom alone does not prove that all items need the same repair.
| Decision | Illustrative reasoning |
|---|---|
| Observation | Picking phrases solely because they have a large search estimate |
| Likely correction | Compare the query intent with the offer and the page a visitor expects |
| Verification task | Group phrases by the task behind the search |
| Result to inspect | Choose one useful destination for each intent |
After the change, the owner repeats the relevant task and records what happened. If the condition remains, the team returns to the evidence rather than declaring the process complete. The example illustrates a repair cycle; it does not claim a particular commercial result.
Example 3: extend a process after it works
A third team already has reliable records for a small scope and wants to expand. It compares the next group with the first: are query, intent, volume source defined in the same way, and does the intended outcome remain qualified organic visits? Differences are written down before the earlier process is reused.
Expansion is appropriate when the assumptions still hold and an owner can review exceptions. Where the new group has different needs, the team adapts the process and tests again. Reusing the structure is useful; reusing a conclusion without checking its conditions is much less reliable.
Apply the examples to your own work
- Write the current problem in observable terms using query.
- Choose which of the three examples matches the stage of the work.
- Complete this action first: collect queries from customer questions and Search Console.
- Keep the resulting evidence and review qualified organic visits on a consistent basis.
Keep a dated record of the page or query being examined. Search interfaces and external references can change. A saved observation should include enough context to distinguish an old issue from the current state.
Skip the manual steps. Let AgentixSEO run this for every client.
Start now