The playbook
Keyword Clustering: Template and Field Guide
This keyword clustering template turns a broad task into a record another person can use. It captures keyword, intent group, evidence, then connects that information to a decision. Copy the table into your working document or system and create a separate record for each item in scope.
Put the task in context
Normalize capitalization and spacing before grouping terms. Then compare the required answers: “sales pipeline stages” and “sales pipeline examples” may overlap substantially, while “sales pipeline software pricing” adds a different buying task. Semantic similarity alone does not establish separate-page demand.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| keyword | Record the keyword associated with this page or query record. Use a stable reference so later updates can be matched. |
| intent group | Record the intent group associated with this page or query record. Keep the value specific enough for another owner to interpret. |
| evidence | Record the evidence associated with this page or query record. Keep the value specific enough for another owner to interpret. |
| proposed page | Record the proposed page associated with this page or query record. Keep the value specific enough for another owner to interpret. |
| Decision field | Entry instructions |
|---|---|
| Observed problem | Describe the actual condition and where it was observed. |
| Recommended action | State the smallest action that resolves the documented problem. |
| Evidence | Link to the record, observation, or test supporting the action. |
| Owner and next review | Name the accountable person and when the decision should be revisited. |
How to complete the worksheet
Begin with keyword. Use the same reference throughout the record so notes are not attached to the wrong item. Then normalize spelling and remove exact duplicates. This establishes the information required before the worksheet becomes a request for action.
Next, compare reader intent and expected result format. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as grouping phrases only because they share a word, rather than a broad instruction to “improve performance.”
Finally, check ambiguous groups against current search results. Put split groups where the required answer or page format changes in the action field only when it addresses the observed condition. If the problem is different, change the action. The template is a structure for judgment, not a reason to apply the same fix everywhere.
Illustrative completed decision
| Part | Illustrative entry |
|---|---|
| Problem | Grouping phrases only because they share a word |
| Action | Split groups where the required answer or page format changes |
| First check | Normalize spelling and remove exact duplicates |
| Follow-up check | Check ambiguous groups against current search results |
| Outcome to define | distinct validated intent groups |
Adapt the fields without losing meaning
You can add fields required by your team, but each should change a decision or preserve necessary context. Keep factual observations separate from recommendations. If intent group changes, record the new value and its effective date instead of silently rewriting the context of an earlier decision.
Use the record in a handoff
Ask the receiving owner to explain the next action using only the worksheet. Missing context becomes visible quickly during that exercise. Repair the record before applying the structure to a larger batch. Keep distinct validated intent groups connected to the item so the team can later assess whether the action was useful.
Search results and indexing decisions are not controlled by the publisher. Record what your team changed and what was observed afterward. Avoid turning a correlation between a release and a traffic change into a claim of proven causation.
Skip the manual steps. Let AgentixSEO run this for every client.
Start now