A position band is an opportunity filter, not an instruction
Prioritize relevant queries near useful visibility ranges when the existing page can satisfy the intent. A modest-volume service query can be more actionable than a broad term that requires an entirely different offer.
Queries near prominent results can identify pages worth inspecting, but position alone does not establish value or effort. Determine whether the question is relevant and whether the destination can provide a substantially better answer.
A worked example
A hypothetical page appears around position 12 for a niche technical procurement question with few estimated searches. Another appears similarly for a broad student query. The first may be a stronger commercial fit even though the second has more apparent demand.
How to apply it
- Group relevant visible queries and inspect their current destinations.
- Identify a concrete answer gap, technical issue or misleading snippet.
- Choose an improvement justified by the gap rather than adding keywords mechanically.
What the result can establish
Track the chosen group with a consistent market and period. Search Console averages are not a fixed page-two location for every searcher. Improvement should be judged by relevant discovery and supported inquiries, not a promise to cross a particular position threshold.
Reference: Google: Search Console performance report.
Supporting documentation
Google: Search Console performance reportGoogle Ads: keyword estimates and competition definitions