Striking Distance Keywords: The Page-Two Playbook for Operators

Page two is not a graveyard

Monday standup. Someone wants a net-new pillar on a trending topic. Meanwhile your pricing page sits at position 9 for a buyer query pulling four thousand impressions a month and converting almost none of them to clicks. That position-9 URL is the cheapest growth on your entire site, and it is the one nobody is talking about.

Striking distance keywords are queries where you already rank on the bottom of page one or the top of page two, close enough that focused on-page work can move clicks materially. Google has already decided your URL is a plausible answer. Users already see your brand in the results. The gap to the top five is usually depth, snippet alignment, and internal link support, not a brand-new URL competing from zero history.

This is the public version of how we run page-two operations: detect striking distance in Search Console, classify the signal so you fix the right thing, rank the work by leverage instead of stakeholder volume, expand the keeper URL, redistribute internal links, and prove the click recovery on the same queries. No volume worship from third-party estimates. No publishing reflex. Just the queries Google already shows you, ordered by what they are worth.

Quick answer: five-step striking distance workflow

Run these in order. Skipping straight to publishing a new post is how operators leave the easiest clicks on the table.

1. •Filter Search Console queries to position greater than 4 and less than 21, impressions above 100, over a twenty-eight to ninety day window.
2. •Map each striking query to one keeper URL: one intent, one URL, no new sibling page.
3. •Classify the signal: true strike, low CTR, decay, or cannibalization. They need different fixes.
4. •Rank candidates by impact (impressions times click gap times commercial proximity) against effort.
5. •Expand the keeper URL, relink from authority pages, and measure the same query cluster for twenty-eight days before any net-new publish.

Most striking distance work is same-week effort on a page that already exists. That is why it should outrank a research-heavy new pillar most weeks, even when the new pillar feels more exciting.

What striking distance means, and what it is not

Treat position as a band, not a single number. Impressions and commercial intent matter more than an arbitrary cutoff. A query at position 11 with four hundred impressions on a money page is worth more than a query at position 6 with twelve impressions on a glossary term nobody buys from.

Striking distance is not a reason to spin up a new URL on a topic you already cover. It is not a thin two-hundred-word patch bolted onto a stale guide. And it is not a license to chase position 28 on a fantasy keyword from a tool export. The discipline is choosing the existing URL with the most latent clicks and making it genuinely better.

How to find them in Google Search Console

Search Console is the only honest source for this work because it shows real impressions and positions from Google, not estimated volume from a third-party database. Here is the manual path.

1. •Open Performance, then Search results. Toggle on clicks, impressions, CTR, and average position so all four columns show.
2. •Set the date range to the last twenty-eight days compared to the prior period, or widen to ninety days for low-traffic sites.
3. •Add a position filter: greater than 4 and less than 21. This isolates the striking distance universe.
4. •Sort the Queries tab by impressions, descending. High impressions plus a page-two position means real demand Google thinks you almost answer.
5. •Click each candidate query, switch to the Pages tab, and note the ranking URL. That is your keeper.
6. •Export to a sheet, then ignore anything under roughly one hundred impressions in the window. It is too small to trust.

Pair this with GA4 where it is connected. A page can rank in striking distance and still fail after the click. If engagement is weak on the landing page, the fix may be on-page experience, not ranking depth. Read the GSC and GA4 combined workflow for how to merge demand and behavior into one weekly loop.

Classify before you expand

Page-two work fails when classification fails. A position-9 query with collapsed CTR does not need eight hundred more words, it needs a better title. Two URLs alternating on the same query do not need expansion, they need consolidation. Use this matrix before you open the CMS.

The keyword cannibalization workflow and the low CTR recovery workflow cover those branches in depth. This article assumes you have a clean true strike: one keeper URL, real impressions, and room to make the answer better.

Prioritize by leverage, not by spreadsheet row order

A filtered Search Console export gives you twenty to two hundred candidates. Alphabetical order is not a plan. Rank every strike on four dimensions you can defend with evidence instead of opinion: impact, effort, confidence, and execution readiness.

Tie-break in that order: impact, then effort, then confidence, then execution. A moderate strike you can ship Friday beats a high-impact strike that needs a two-week research sprint. The Mission Brief Method covers this ranking discipline in full, and the article on prioritizing website improvements shows how it sorts a real backlog.

The strike execution playbook

Once a strike is ranked, ship it on the keeper URL. Resist the urge to start a sibling page midway through.

1. •Confirm the keeper URL: one intent, one URL. Do not create a new page for a query you already rank for.
2. •Audit the top five results live. Note their format, depth, freshness signals, and structured data.
3. •Map the gaps: missing subtopics, outdated stats, a weak or absent FAQ, thin examples a reader actually needs.
4. •Expand the body to match intent, not to hit a word count. Information gain is the goal.
5. •Update the title and H1 only if query alignment genuinely improved, and never in a way that cannibalizes an adjacent URL.
6. •Add FAQ structure where People Also Ask competes for your query cluster.
7. •Relink from two or three authority pages using descriptive, varied anchors from your URL library, no exact-match stuffing.
8. •Relink onward to related cluster pages where the reader journey continues.
9. •Update the publish date only after a meaningful change, never as a cosmetic trick.
10. •Open a Growth Order and set a twenty-eight day measurement window before you move on.

A labeled scenario

Illustrative labeled example. Not a customer export.

Ranked against the backlog, this strike outranks a proposed net-new blog post on the same theme. Impact is high because the page is commercial and impressions are real. Effort is same-week. Confidence is high after the Search Console trend confirms over two cycles. Execution is ready because the owner has CMS access and the pillar can link down to it.

• Expanded the FAQ to answer seat pricing, trial cost, and annual versus monthly directly.
• Tightened the title to lead with the buyer query, matched the H1, rewrote the meta to answer in the first sentence.
• Added two contextual internal links from higher-authority comparison and integration pages.
• Logged a Growth Order with a frozen baseline and a twenty-eight day window.

The revenue attribution playbook explains why commercial proximity earns the top of the queue here. A small click gain on a pricing page usually beats a large gain on a page nobody buys from.

From manual export to a continuous queue

The manual workflow works until it does not. A monthly export is stale by the second week, carries no ranking of what to do first, and forces you to re-find the same striking queries every cycle. At portfolio scale it collapses entirely.

Run this loop on connected Search Console data: tag striking distance alongside decay, cannibalization, and internal-link gaps, rank the top as orders not charts, draft expansions grounded in your Knowledge Base with human review, and answer judgment calls with your own data instead of generic advice.

Failure modes operators repeat

• Publishing a new URL that collides with a page already ranking in striking distance, splitting the cluster.
• Thin patches that add words without addressing the intent shift visible in the current top results.
• Skipping the relink pass, so the page sits at 11 while the pillar above it never links down.
• Spending a sprint on position 28 when near strikes with real impressions sit unworked.
• Ignoring a collapsed snippet, fixing depth on a page whose real problem was presentation.
• Declaring failure at forty-eight hours. Most on-page changes need two to four weeks to register.

“Page two is an option book, not a graveyard. The operators who win are the ones who exercise the cheap options before they buy new inventory.”

. Operator principle