Striking distance keywords are queries where your pages rank between positions 5 and 20 — close enough to page 1 that relatively small improvements can produce large traffic gains, but not yet generating meaningful clicks. The case for building a weekly workflow around them is straightforward: they have better ROI than almost anything else in SEO because the foundational work — content creation, domain authority, topical relevance — is already done.
The concept is simple. Executing it systematically is where most teams fall down, because GSC makes it genuinely inconvenient to work with this data at scale.
Step 1: Extract the Striking Distance Keyword List
Open GSC → Performance → Search Results → set date range to 90 days (90 days gives stable averages; 28 days has too much volatility for average position). Enable Average Position in the metrics bar.
The native GSC interface doesn't offer position-range filtering in the UI, but the API does. If you're working at any meaningful scale (more than a few dozen target keywords), use one of these approaches:
- GSC API query with
dimensionFilterGroupsfiltering forposition BETWEEN 5 AND 20— full documentation in Google Search Central - BigQuery export of GSC data, then SQL query filtering
WHERE average_position BETWEEN 5 AND 20and ordering bysum_impressions DESC - Manual export from GSC UI (up to 1,000 rows) sorted by average position, then filter in a spreadsheet — workable for smaller sites
The output you want: keyword, average position, impression count, click count, CTR — sorted by impressions descending within the 5-20 position filter.
Step 2: Group by Parent Page
Individual keywords matter less than the pages they're associated with. A page at position 14 for 12 different related keywords is a better optimization target than a page at position 14 for one keyword — because a single improvement to that page can lift all 12 keywords simultaneously.
Switch to the Pages view in GSC and filter for the specific queries in your list. Or, in your BigQuery export, join query data with page data to see which URLs are the sources of your striking-distance keywords. Group by URL, sum the impressions, count the qualifying keywords. Sort by total impressions. The top 10-20 URLs become your priority list.
Step 3: Diagnose Each Priority Page
For each page on your priority list, answer four questions before touching anything:
- What is the primary intent of the top-ranking page for this query? Does my page match that intent, or is it off by one step (informational vs commercial, etc.)?
- What does the top-ranking page cover that mine doesn't? Spend 10 minutes reading the #1 result. Look for data, examples, sub-topics, or formats that are absent from your version.
- What is the internal link situation? Does the page receive internal links from high-authority pages on the site? If not, that's often the lowest-effort fix.
- Is the title tag aligned with the primary query? Not just containing the keyword but matching the framing that users expect.
Step 4: Prioritize Actions by Effort vs. Impact
Rank the interventions by effort required:
- Low effort (1-2 hours): Title tag rewrite, meta description update, adding internal links from 3-5 related pages, fixing heading hierarchy
- Medium effort (half day): Adding a new section to cover a missing sub-topic, adding a comparison table, adding a specific FAQ section for PAA queries
- High effort (full day+): Full content rewrite, adding original data or case studies, building external links to the specific page
Start with low-effort interventions and measure before escalating. Many page 2 keywords in positions 11-15 move to page 1 with nothing more than a title tag fix and 3-4 new internal links. Spending a day on a full content rewrite before testing the cheap interventions is a common waste.
Step 5: Implement and Note the Date
Make your changes, note the exact date in a tracking sheet, and set a reminder to check results in 4-6 weeks. Most on-page changes show movement within 4-8 weeks. Internal link additions can show faster — sometimes 2-3 weeks — because Googlebot crawls them quickly from already-indexed pages.
Step 6: Measure and Recalibrate
After 6 weeks, run the same striking-distance keyword report. Check positions for the keywords you targeted. Track:
- Position change per keyword (before and after)
- Click change for the affected page
- Whether the page moved from striking distance to page 1
- Which intervention types produced movement and which didn't
The pattern will tell you what works on your specific site and in your specific niche. Internal links move some sites quickly; content depth matters more in others. After 2-3 cycles of this workflow, you'll have a calibrated understanding of which lever to pull first.
The AI-Era Adjustment
Averi's 2026 playbook adds a new dimension to striking-distance analysis: whether AI Overviews are present for the target query. Pages cited in AI Overviews earn 35% more organic clicks, even when organic CTR overall is suppressed by the presence of the AI Overview.
For striking-distance keywords where AI Overviews are active, the optimization target shifts from "rank higher" to "get cited in the AI Overview." The factors that correlate with AI Overview citation — structured answers, specific data points, clear authority signals — overlap significantly with what moves rankings anyway, but the end goal is different.
A Note on Average Position as a Metric
GSC average position is an average across all impressions, devices, locations, and query variations. A keyword that shows position 12 in aggregate might be at position 8 on desktop and position 18 on mobile. If you're optimizing for desktop-heavy commercial queries, the mobile-influenced average understates your desktop opportunity.
For a more accurate picture, apply a device filter when checking positions for your priority keywords.
The Weekly Cadence
The workflow above doesn't need to be done weekly — it should be done monthly or quarterly, with the weekly check being simpler: pull the 30-day position data for pages currently in optimization, verify movement is happening, flag any page that's moved into or out of the striking-distance range.
Consistency matters more than frequency. One systematic pass per month over the striking distance list, with clear notes on what was changed and when, produces more measurable progress than ad hoc optimization whenever someone has time.
The data to make all of this work is sitting in GSC right now. The constraint is usually accessing it at the right scale and organizing it into an actionable priority list — which is exactly what a proper export and BigQuery workflow solves.
