Use the range as a starting filter

Queries with average positions around eight to twenty can reveal pages worth reviewing, but the range is not a universal opportunity score. Average position compresses many appearances. A page may perform differently by country, device, or exact wording, and a commercial query may face very different competition from an instructional one.

Begin with a meaningful date window and enough impressions to understand the pattern. Export candidate rows, then add the associated page and business relevance. The result should be a manageable review queue, not a commitment to rewrite every row that falls inside a numeric band.

Check whether the existing page fits

Open each candidate page and write a one-sentence description of the searcher's likely task. Does the page actually help complete that task? If a comparison query lands on a generic company page, adding another paragraph may not solve the mismatch.

Look for missing decision aids: a worked example, setup steps, constraints, screenshots, or a clear answer near the beginning. Prioritize improvements your team can substantiate. A precise explanation supported by real product knowledge is more defensible than copying headings from the currently visible results.

Hypothetical example: two equal positions

Imagine two query groups both averaging position twelve. One concerns a feature your product supports and leads to an incomplete setup guide. The other asks for an unrelated free utility that your product does not provide. Their positions are similar, but their business value and content fit are not.

The team chooses the setup guide. It adds tested instructions, explains prerequisites, and connects the guide from the relevant documentation hub. It does not build a misleading utility page merely because the second query has impressions. Prioritization should reflect usefulness and credible differentiation as well as exposure.

Score effort and evidence separately

Use simple columns: reader fit, business fit, current evidence, missing information, effort, and owner. Keep these judgments visible rather than hiding them inside a single opaque score. If several candidates share one template defect, fix that defect before commissioning independent rewrites.

Choose a small first batch so you can review the work carefully. Record what changed and why. Avoid expanding all articles to the same length; a concise troubleshooting answer may need one exact diagnostic step, while a buying guide may need substantial comparison evidence.

Review the same cohort after editing

Revisit the original query-page pairs rather than celebrating any site-wide traffic increase. Check impressions, clicks, and whether the intended page remains the destination. Add newly emerging relevant queries to a separate observation list so they do not silently change the original comparison.

Some useful improvements will not produce an immediate measurable gain. Others will coincide with external changes you cannot control. Keep those limitations in the report. The purpose of the position filter is to allocate editorial attention intelligently, not to promise that every selected page can move into a particular ranking position.

PUT IT TO WORK

Position identifies candidates; intent, evidence, and business fit decide which deserve work.

Sources & further reading

Official documentation informs this guide. Examples are illustrative, and product interfaces or limits can change.

THE WORKSPACE WE'RE BUILDING

From search signals to a useful first draft.

SERP.so is in development. Join the waitlist for a workspace that connects research, content review, and publishing.

Join early access ↗