The playbook
Search Intent: Template and Field Guide
This search intent template turns a broad task into a record another person can use. It captures query, task, expected format, 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
Searches containing “examples,” “template,” “calculator,” and “pricing” often imply different deliverables. Inspect current results and the wording of the query together. If the visitor expects an editable template, include an actual reusable structure rather than merely describing why templates are useful.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| query | Record the query associated with this page or query record. Use a stable reference so later updates can be matched. |
| task | Record the task associated with this page or query record. Keep the value specific enough for another owner to interpret. |
| expected format | Record the expected format associated with this page or query record. Keep the value specific enough for another owner to interpret. |
| page decision | Record the page decision 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 query. Use the same reference throughout the record so notes are not attached to the wrong item. Then examine the formats and offers present in current results. This establishes the information required before the worksheet becomes a request for action.
Next, separate learning comparison purchasing and tool use. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as sending tool-seeking visitors to a long article with no tool, rather than a broad instruction to “improve performance.”
Finally, match the content and next action to the dominant task. Put provide the requested functionality or target a different question 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 | Sending tool-seeking visitors to a long article with no tool |
| Action | Provide the requested functionality or target a different question |
| First check | Examine the formats and offers present in current results |
| Follow-up check | Match the content and next action to the dominant task |
| Outcome to define | task completion by landing page |
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 task 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 task completion by landing page connected to the item so the team can later assess whether the action was useful.
Keep page purpose visible throughout the work. A technically valid page can still fail to answer the reader’s question. Separate access and discovery problems from content problems so that the assigned action matches the cause.
Skip the manual steps. Let AgentixSEO run this for every client.
Start now