# Three meanings hiding behind a running keyword

Companion to /learn/keywords/search-intent/

## Outcome
Separate similar-looking searches by the actual job the user expects the app to perform.

Fictional example, not a client result.

## Scenario
PaceStart is a fictional beginner running app. The team groups “running routes,” “running tracker” and “running plan” together because each contains running. Yet one person wants somewhere to run, another wants a record of a run, and another wants help deciding what to do tomorrow. PaceStart mainly provides progressive training plans.

## Reasoning
Write a plain-language expectation for each query before assigning priority. Inspect representative search results as contextual evidence, not as a definitive statement of every user’s intent. Check reviews, interviews and the product workflow where available. A query can have mixed intent; record that ambiguity instead of forcing it into a confident label.

## Action
Prioritise planning language when the product demonstrates a usable plan. If tracking exists only as a supporting feature, explain its role accurately. Avoid promising route discovery if the app has no route database. Connect the chosen intent to the opening screenshots so people can recognise the answer to their question immediately.

## Trap to avoid
Do not equate shared vocabulary with shared intent. “Budget planner” may refer to personal spending, event planning or a business forecast. A useful cluster groups a similar expected outcome, not merely similar words.

## Advanced considerations
For mixed-intent phrases, decide whether a broader promise would improve comprehension or dilute it. Record the trade-off. You may choose a narrower phrase with a clearer fit rather than compete for an umbrella term that demands features you do not offer. Validate the opening message with people who resemble the intended audience, and ask what they expect to happen after installation.

## Exercise
A competitor ranks for all three phrases. Does that establish that PaceStart should target all three too?

## Suggested answer
No. The competitor may serve a broader product need or attract a different audience. Inspect what it actually offers. Competitor visibility can generate a research question, but your own product support determines whether the promise is defensible.

## Your worksheet

### Exact query and market
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Expected user action
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Likely audience and context
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Evidence supporting the interpretation
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Ambiguous or competing meanings
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

### Product fit and matching screenshot proof
Answer:
Evidence:
Uncertainty:
Owner:
Next action:

## An intent assessment with confidence and a challenge
Continue the fictional PaceStart running-app example. Confidence here concerns the interpretation, not a probability of ranking or conversion. A useful intent record includes the evidence that could overturn it.

Illustrative intent hypotheses. These are not measured distributions of searchers.
Query and interpretation | Confidence boundary | What would challenge the interpretation
Running plan / decide which session comes next | Plausible fit with a progressive training product; validate locally | Relevant users expect coaching features the app lacks
Running tracker / record a completed activity | Meaning may cover GPS, manual logs or device integrations | Research shows a required tracking mode is unsupported
Running routes / find somewhere to run | Route discovery seems likely but the use context is unresolved | Users mainly want to save familiar routes rather than discover new ones
Beginner running / ambiguous task | Audience cue is clearer than the desired workflow | Users split between plans, route ideas and injury-related advice

### Use a short validation interview
Show a phrase without your proposed headline and ask what the person would expect an app to do. Ask them to describe the first task after opening it, the information they would need and what would disappoint them. Then show the listing and ask what they think it promises. Keep responses separate from your interpretation. A small qualitative review can reveal misunderstandings; it does not measure market-wide demand.

### Handle mixed intent explicitly
When answers differ, record the alternatives instead of selecting the one that makes your product look best. Decide whether the listing can serve a coherent subset with an honest promise. For “beginner running,” a training-plan app can explain progressive sessions while avoiding claims about route discovery or medical advice. A broad query does not require a broad unsupported product promise.

### Connect intent to an acceptance check
Before approving creative, ask whether a person expecting the selected job can identify the relevant product evidence. For a training plan, show a genuine next-session workflow rather than an unrelated activity chart. If the research suggests that the essential workflow is absent, revisit targeting. Better captions cannot solve a fundamental product mismatch.

## Continue reading
- /learn/keywords/relevance/
- /learn/keywords/competitor-research/
- /learn/conversion/value-proposition/