The playbook
Search Intent: Metrics and Measurement
Measure search intent by defining task completion by landing page precisely enough that two people can reproduce the result from the same records. Keep the reporting unit, date basis, and scope visible. Without those definitions, a change in the report may reflect a changed calculation rather than a changed customer outcome.
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.
Create a metric definition
| Definition field | What it must explain |
|---|---|
| Measure | task completion by landing page |
| Unit | What one page or query record or completed outcome represents |
| Included records | The scope identified by query and task |
| Date basis | The event date or period used to include a record |
| Exclusions | Tests, duplicates, or other records outside the agreed definition |
| Source owner | analytics owner |
Separate delivery checks from outcome measures
A delivery check asks whether the team completed a specific task, such as examine the formats and offers present in current results. An outcome measure asks what happened for the user or business afterward. Keep both visible. Completing the task is useful evidence of execution, but it does not by itself prove that the broader outcome improved.
Worked arithmetic example
Suppose an illustrative review includes 80 eligible records, and 60 satisfy the explicitly defined completion condition. The completion share is 60 ÷ 80 × 100 = 75%. This is hypothetical arithmetic, not an industry benchmark or a predicted improvement. It describes only the population and condition you defined.
For search intent, explain the condition before applying that calculation. If the question is whether the team can match the content and next action to the dominant task, a record counts only when the evidence demonstrates that condition. Do not replace missing outcomes with successful ones just to complete a report.
Compare like with like
Keep the scope, date basis, and exclusions consistent between observations. If task changes meaning between periods, note the change and rebuild a comparable view where possible. A rate can also move because the composition of the underlying group changed, even when individual performance did not.
Investigate an unexpected result
- Check whether the underlying query records are complete.
- Look for this known failure: sending tool-seeking visitors to a long article with no tool.
- Verify that the process still includes: separate learning comparison purchasing and tool use.
- Reconcile a sample with the original record before changing the operating plan.
Use the report to choose an action
If the evidence supports a correction, provide the requested functionality or target a different question. Record when the change occurred and what should be checked next. Keep uncertainty visible when the sample is small or the observation period is incomplete. The purpose of measurement is a better decision about task completion by landing page, not a favorable-looking number.
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