What Are Striking Distance Keywords? Find and Prioritise Them

What are striking distance keywords?

Striking distance keywords are queries where your site already ranks close to valuable search positions, commonly in the average position range of 4 to 20. That band is a working heuristic for opportunity spotting, not a universal rule every team must copy.

These terms already collect impressions, so you are rarely starting from zero. A tighter intent match, clearer title, stronger page structure, or better internal links can be enough to compete for higher clicks without building a new URL.

What does within striking distance mean in SEO?

Within striking distance means the page is near enough to chase stronger visibility. It does not mean a ranking gain is guaranteed, timed, or permanent.

Search Console positions are averages across devices, locations, and result layouts, so one number can hide uneven performance. Use the label to shortlist work, then confirm intent, business fit, and whether the ranking URL can beat what currently sits above you before you commit a sprint.

Which striking distance keywords are worth working on?

Worth means business value plus shippable effort, not “anything in positions 4 to 20.” SEO leads and agencies should rank candidates with a simple checklist before briefing writers or developers.

• Search intent: prefer commercial, comparison, or decision-stage queries when pipeline matters.
• Business relevance: the query must map to a service, product, or page you actually want to grow.
• Impressions: enough search demand that a lift is visible in the same GSC property.
• Clicks and CTR: solid impressions with weak clicks often point to title, snippet, or intent gaps.
• Ranking stability: steady averages are easier to plan around than volatile one-week spikes.
• Implementation effort: favour fixes you can publish and verify this cycle over unbounded rewrites.

Examples of striking distance keywords

Use clearly hypothetical comparisons. A query such as “SEO retainers for SaaS” around position 7 on a service page is often worth work: intent is commercial, the URL can convert, and proof, pricing clarity, or sharper headings may improve both relevance and CTR.

A broad informational query such as “what is a backlink” at position 14 on a thin glossary post is usually lower priority if it does not support sales or retention goals, even when raw impressions look attractive. Score opportunity by outcome, not by how close the average position sits to page one alone.

How to find striking distance keywords in Google Search Console

Google Search Console is the fastest source of truth because it reflects queries and URLs your property already earns. Work from Performance data, pick a position band that matches your risk tolerance, then inspect the page behind each query before you write a brief.

• Open Search Console and select the correct property (domain or URL-prefix).
• Go to Performance, then Search results.
• Choose a stable date range (often 28 or 90 days) and optionally compare to the previous period for trend context.
• Filter Average position to your striking-distance band, for example roughly 4 to 20 (adjust to how aggressive your team is).
• Open the Queries tab, sort by impressions or clicks, and note volume versus current CTR.
• Export or label the shortlist so owners, URLs, and next actions stay clear across clients or brands.

Check the ranking page for each query

Query totals can hide the wrong URL winning the impressions. Click a promising query, switch to Pages, and confirm which path Google associates with it.

If an outdated blog post outranks the service URL you care about, fix cannibalisation, consolidate, or retarget the brief to the URL you want to win. On the chosen page, check intent match, missing sections competitors cover, title alignment with how people phrase the query, and internal links from stronger related URLs.

Separate country and device patterns

Blended averages mask real opportunity. Filter by country when you have priority markets, and split mobile versus desktop when SERP features or layouts differ.

A query that looks like position 12 overall may already sit near the top on mobile in one country and lag on desktop elsewhere. Prioritise the slice that can move clicks soonest, ship the change on that URL, then verify in the same filtered Search Console view after Google recrawls rather than trusting a single sitewide average.

How to turn a keyword opportunity into a page-level fix

Group every related striking distance query around one primary URL before you edit anything. That single decision stops cannibalisation and keeps the fix measurable in Search Console.

Pull the queries that share the same intent and already send impressions to the same page (or to near-duplicate URLs). Assign one primary URL per cluster. Secondary URLs should support that page with internal links, not compete for the same SERP.

Refresh an existing page or create a new one?

Default to refreshing the URL that already ranks. A new page only helps when no existing URL matches the intent, the current page cannot cover it without confusing the reader, or you would dilute a strong conversion path. New URLs change the reader journey and often need nav or messaging approval, so treat them as a product decision, not an SEO default.

Compare your primary URL with the live results for the head query:

• Intent match: does the page answer what the top results actually satisfy (guide, comparison, tool, definition)?
• Answer depth: is the direct answer thin, buried, or missing in the first screen?
• Snippet strength: do title and meta description reflect the query and the real offer?
• Internal links: do relevant hub and supporting pages point to this URL with clear anchor text?

Write the diagnosis as a page-level brief: primary query, supporting queries, intent gap, and the smallest change set that closes it. If two URLs already rank for the same cluster, consolidate or clearly differentiate before you add content. Ship one focused fix per primary URL so you can verify what moved.

How to optimise pages for striking distance keywords

Optimise the primary URL against the gap that keeps you in positions 4 to 20, not a generic keyword list. A tight pass on snippet, intent, and cannibalisation beats a full rewrite that restates the query without helping the reader decide.

Match the fix to the ranking problem

Striking distance work is not cold-start content. You already have relevance and some authority. Prioritise what moves CTR and clarity first, then deepen substance only where SERP winners prove a gap.

Use this focused checklist on the primary URL:

• Snippet and CTR (often the fastest win): rewrite title and meta so the offer matches the head query, promise a clear outcome, and drop unverified claims. Weak titles keep strong pages stuck below the fold.
• Intent gaps: if you rank but lose to a different page type, change structure and substance (steps, comparison, local detail) rather than padding word count. Match what top results deliver, then add trade-offs and mistakes they skip.
• Direct answer early: 1 to 2 plain sentences under the main heading that answer the searcher before the detail. Helps both humans and AI overviews.
• Cannibalisation: if two of your URLs split impressions for the same query, pick one primary, consolidate or redirect the weaker page, and point internal links at the winner. Extra near-duplicate pages rarely push you into the top 3.
• FAQs and schema: only questions your audience and Search Console show people ask; mark up only what is visible (Article or FAQ when the page truly has those).
• Internal links: support the next step with verified URLs such as how to publish well or request indexing when those steps are part of the workflow.

When the work is content, ship one coherent refresh aimed at the diagnosed gap. When it is title, meta, or on-page hygiene, keep the diff small so verification is obvious. Do not change core navigation or marketing messages in the same pass unless you have approval. The goal is a page that deserves the query, then a clean signal you can measure.

How to verify changes and measure whether they helped

Split the work into two gates: confirm the fix is live and correct, then evaluate search and business outcomes over a comparable window. Do not treat a position blip as proof.

Verify the published fix

Before you judge rankings, check implementation:

• The intended URL returns 200 and is indexable (no accidental noindex, canonical clash, or login wall).
• Rendered HTML shows the new title, answer block, FAQs, and links users and crawlers should see.
• Internal links resolve to the verified destinations you meant to use.
• If you rely on a CMS or deploy pipeline, confirm the production revision, not only staging.

Request indexing only after the live page is correct. Recrawl key templates if many URLs share the same component.

Measure clicks and conversions, not position alone

In Search Console, compare a post-release period with a matched pre-release period for the primary URL and its query cluster. Look at query-to-page mapping, clicks, impressions, and CTR together. Watch whether supporting queries consolidate onto the primary URL instead of splitting across duplicates.

Tie the same window to site outcomes you already track (sign-ups, demo requests, qualified leads), not vanity rank. Seasonality, SERP features, and competitors move too, so avoid promising a recovery date, a guaranteed lift, or inclusion in AI answers. If nothing meaningful moves after a fair sample, reopen the intent diagnosis rather than adding more keywords to the same weak page.

Build a striking distance workflow your team can ship

Run striking distance work as a closed loop: hand off one page, ship a small fix, then verify against Search Console before the next item. Name owners and success criteria up front so the pass does not stall in review.

• Handoff owner (SEO lead): picks one primary URL, the query group it owns, and the single proposed fix (title and meta, opening answer, FAQ, or internal links). Prefer the live page over a new slug.
• Ship owner (writer or engineer): implements only that fix, keeps scope to metadata, FAQ, schema, and links first, and marks the change live with a deploy note.
• Verify owner (same lead or analyst): checks impressions, average position, and clicks on that URL in Search Console after the change is indexed, not vanity page count.

Success criteria stay simple: the target queries hold or improve average position on the chosen URL, and clicks move with visibility. If nothing shifts after a fair crawl window, revise the brief once; do not open a second URL for the same group.

Queue the next striking distance item only after verification is logged. That rhythm keeps agencies and in-house teams shipping fixes they can prove, instead of stacking unmeasured edits.