Striking-Distance SEO: Finding Pages 2–9 Wins

Striking-distance SEO is the practice of improving pages that already rank for relevant queries but have not yet reached the visibility threshold you care about. In practical terms, that often means pages ranking on the lower half of page one through page three, with enough impressions to show that Google and searchers already recognize some relevance.

It is a useful prioritization model because it starts with existing evidence. Instead of publishing a new page for every possible keyword, you look for a page that has demand, a clear gap, and a realistic path to improvement. That makes it a natural input for agentic SEO.

What counts as striking distance?

There is no universal position range. A site with strong authority may focus on positions 4–10. A newer site may find better opportunities between positions 11–30. The range should be wide enough to find candidates but narrow enough that the proposed action remains plausible.

It also helps to know what the number you are filtering on actually means. Google’s Performance report documentation explains that average position reflects the topmost result from your site, averaged across the period. A page reported at position 18 may have been at 9 for a week and 27 for three weeks, or it may sit steadily at 18 for one query and never appear for the rest of its group. That is why the impression floor does more work than the position band: impressions are counted, while position is averaged.

Useful filters include:

• A minimum impression threshold appropriate for the site.
• Queries that match the page’s business and search intent.
• A position range, such as 11–30, for the initial pass.
• A page that is indexed and technically reachable.
• No recent change that would make the comparison noisy.

The goal is not to promise a ranking jump. The goal is to identify pages where a focused, evidence-backed improvement is worth testing.

The four questions behind a good candidate

1. Is there real demand?

An average position by itself is not enough. A page ranking at position 18 for a query with two impressions is not the same opportunity as a page ranking at position 18 for a query with thousands of impressions. Start with impressions and the relevance of the query set. The signal-by-signal guide to Search Console evidence covers which of those numbers can carry a decision and which cannot.

2. Does the page satisfy the intent?

Read the queries together, not one at a time. Are searchers asking for a guide, a comparison, a checklist, a local service, or a product? If the page format is wrong, a title tweak or a few extra words may not solve the problem.

3. What is the bottleneck?

Common bottlenecks include:

• A title that does not make the page’s promise clear.
• Weak coverage of a subtopic visible in the query set.
• Important content buried under an unclear structure.
• Too few relevant internal links.
• A page that is indexed but isolated from the site’s strongest sections.

4. Can the change be measured?

Save the baseline before editing. Record the affected page, query group, impressions, clicks, CTR, position, proposed action, and publish date. Without a baseline, the post-publish story becomes guesswork.

There is also a floor below which measurement is not worth attempting. If a page’s query group produces a few dozen impressions a month, normal week-to-week variance will exceed any effect the change could plausibly have, and both “it worked” and “it failed” will be unsupported. Pages under that floor are not bad pages — they are simply not measurable ones, and they should be improved for readers rather than enrolled in a test. The measurement model sets out how to pick that threshold for a specific site.

A worked example

Consider a page reported at position 22 with 1,400 impressions and 3 clicks over 28 days. Grouping its queries by intent shows the shape of the problem:

Query group	Impressions	Avg. position	What it implies
”seo audit checklist” (and close variants)	900	19	Core intent, real demand, close-ish
”how to do a technical seo audit”	340	26	Same page competing on a how-to intent
”free seo audit template”	160	41	Different format expectation entirely

Three readings are possible, and the evidence distinguishes them.

If the page is a thorough checklist but ranks at 19, the bottleneck is probably not content — it is that nothing on the site treats this page as the authoritative answer. That is a linking and consolidation problem.

If the page is a short overview competing against detailed checklists, the bottleneck is coverage, and the fix is depth on the subtopics visible in the second query group.

If the page is genuinely about three different things, the honest answer may be that it should be two pages — or that the template intent should be dropped rather than served badly. Splitting a page is a strategic decision with cannibalization risk, so it belongs with a human, not an agent.

Notice what the example does not support: a claim that any of these fixes will move the page to position 5. The evidence justifies choosing one focused test and measuring it. It does not justify a forecast.

Internal links are often the first test

Internal links can clarify relationships between pages for readers and crawlers. A striking-distance page may already have enough content, but no relevant page points to it with descriptive context.

A useful internal-link test has four parts:

1. Choose a source page that is topically relevant and already crawled.
2. Choose a target page that answers the next natural question.
3. Write anchor text that describes the destination without forcing a keyword.
4. Review the surrounding paragraph so the link is useful in context.

See how agents can automate internal linking without wrecking a site for a deeper implementation guide.

A simple striking-distance workflow

1. Export page/query data from Search Console.
2. Group rows by page and intent.
3. Filter for demand and a defined position range.
4. Exclude pages with recent major changes or unresolved technical issues.
5. Diagnose the bottleneck.
6. Choose one focused action.
7. Publish it through a reviewable workflow.
8. Measure after a consistent observation window.

Do not combine a title rewrite, page expansion, canonical change, internal-link overhaul, and URL migration in one test. You will not know which change mattered.

Where the model misleads people

Striking distance is a good prioritization heuristic and a bad promise. Four failure modes recur.

Treating the position band as the opportunity. The band only says a page is visible. It says nothing about whether the page can realistically improve, whether the intent matches, or whether the competing results are institutional sites you will not displace with an internal link.

Ignoring why the page is where it is. A page at position 25 because it is thin is a different problem from a page at position 25 because it is isolated, which is different again from a page at position 25 because it is competing with a stronger page on your own site. Only the last one is fixed by consolidation, and fixing it wrongly makes things worse.

Working the list instead of the best candidate. A striking-distance export will happily return two hundred rows. Acting on all of them at once means none of the results can be attributed, and it usually means most of the effort went to pages that never had much demand.

Mistaking movement for causation. Positions drift. A page that improves after an edit may have improved anyway, particularly if a competitor changed or an update landed in the same window. The honest claim is that the change is consistent with improvement, not that it caused it.

The model earns its keep by narrowing attention. It does not, on its own, tell you the change will work.

FAQ: Is striking distance the same as page-two keywords?

Not exactly. Page two is a convenient shorthand, but striking distance is a prioritization concept. The right range depends on the site’s authority, search intent, query demand, and the type of improvement available. A position 7 page with a poor CTR can be a better opportunity than a position 19 page with almost no demand.

FAQ: How long should I wait before judging the change?

Wait long enough for the page to be recrawled and for the comparison window to contain enough data. Rankture’s agentic workflow uses a recorded baseline and a days 21–28 post-publish window for its standard verdict. Smaller sites may need more time or a higher impression threshold.

The agentic advantage

The hardest part of striking-distance SEO is not finding a list of pages. It is deciding what to do first, keeping the change narrow, and learning from the result. An agent can handle the repetitive analysis while a human controls the strategy and approval. Start with the complete agentic SEO loop, then turn the first measured win into a repeatable playbook.