Striking Distance Keywords: Read Faster, Not Longer

Striking distance keywords are the queries sitting at position 8 through 15 in Search Console: already proven relevant by Google, just not proven good enough yet. The usual fix list is short. Tighten the title. Add an internal link. Pad the word count.

What that list skips is the actual work behind it: reading what already outranks you. That's a two-hour tab-hoarding exercise for most people. It doesn't have to stay that way.

Where your striking distance keywords actually live

Pull them from Search Console's Performance report. Filter for average position between roughly 5 and 20, sort by impressions, and ignore anything under 100 impressions a month. A keyword sitting at position 12 with ten monthly impressions is not worth an afternoon.

Export that list. Most sites land somewhere between 30 and 150 rows, depending on how much has been published and how old the site is. That range alone tells you something useful: this is rarely a one-keyword problem. It's a stack, and stacks need triage before they need edits.

A site with 90 rows in that export and one afternoon a week to spend on it isn't choosing between fixing all 90 or fixing none. It's choosing which five matter this month, and coming back for the next five later.

Position alone is a weak signal on its own. A keyword at position 9 with 40 monthly impressions is a smaller opportunity than one at position 16 with 4,000. Sort by impressions first, and treat position as the tiebreaker between two rows with similar volume, not the other way around.

The real bottleneck is not writing, it is reading ten tabs

Every guide on this topic agrees on the fix: refresh the page, close the content gap, match what the top-ranking pages cover that yours doesn't. What none of them say plainly is how much reading that requires.

To refresh one striking distance page properly, you open the top eight to ten ranking URLs and read enough of each to know what they cover, in what order, and with what specificity. Multiply that by even 40 keywords and the audit itself becomes the project, not the editing.

This is where a stack built around reading, not writing, earns its place outside the usual SEO toolbox. The tools built to summarize a page in a paragraph exist for exactly this kind of triage. Not "should I read this," but "what does this already say, so I know what mine is missing."

What a fast competitive read needs to answer

A summary is only useful here if it answers four specific things. Anything less and the tab gets opened anyway.

• What question does the page answer first, in its opening paragraph.

• What structure carries the piece: numbered steps, a comparison table, a direct-answer block near the top.

• What does it cite that yours doesn't: a stat, a named study, a specific tool.

• What does it skip that everyone else assumes is required.

Run that against eight competing pages and a pattern shows up fast. Usually two or three repeat the same structure almost exactly. One outlier does something different, and that's frequently the page sitting at position 3.

Write those four answers down per page, even in a rough table, rather than trusting memory after the eighth tab. By page six, the details blur together, and the whole point of the exercise was to notice what's different, not to end up with eight vague impressions of "pretty similar" content.

Reading widely beats reading deeply when the goal is pattern recognition, not comprehension. A striking distance audit is the most literal version of that idea: eight shallow reads teach you more than one deep one.

Reading the SERP without opening ten tabs

Perplexity's Comet browser reads whatever tab is open and summarizes it on request, without a separate copy-paste step into a different app. For a striking distance audit, that means opening the top ten results for one keyword in ten tabs and asking for a one-paragraph read of each, one at a time, without fully reading any of them start to finish.

It's not a research tool in the deep sense, and it shouldn't be treated like one. It won't tell you why a page ranks, only what the page says. That distinction matters: the summary shows the content gap, not the authority gap. Backlinks and internal links still do their own separate work, unrelated to what the page's text covers.

For teams without a dedicated AI browser, or who'd rather paste ten URLs into a chat window than switch tools, ChatGPT handles the same triage almost as well, at the cost of one extra copy-paste step per page.

Either way, the point of this step is speed, not depth. You're not trying to understand a competing page. You're trying to know enough about ten of them in the time it would normally take to read two.

The entity-gap shortcut, and what it will not tell you

Surfer SEO's Content Editor takes a different angle on the same problem. Instead of summarizing each competing page individually, it scores a draft against the aggregate of everything the top-ranking pages mention, and flags the specific terms and subtopics missing from it.

That's faster than reading ten pages by hand, and it's the shortcut most striking distance guides quietly recommend without naming the trade-off. The limit is real: it tells you which nouns are missing, not which ones matter. A page can hit every entity on the list and still read like it was assembled from a checklist, because it was.

The two approaches pair well in practice. Use the summarize-and-skim pass first, to understand what the top pages are actually arguing and how they're structured. Then run an entity-gap check second, as a final pass to catch an obvious term everyone else covers that got missed along the way.

The mechanical fixes that rarely move anything

Three tactics show up in nearly every striking distance guide, and all three are weaker than they sound once you've read the pages that actually outrank you.

Adding an FAQ section for the sake of having one rarely helps if the questions don't match what the page's actual competitors are being cited for. Padding word count to match a competitor's length changes a number on the page, not a signal Google reads. Google's own documentation on the Performance report treats position as a relevance and quality signal, not a length contest, and the report itself won't tell you which.

Retitling a page around the exact keyword, without changing anything else, can lift click-through rate on a query that was already borderline relevant to begin with. It rarely moves a page that's stuck because the content is thin, rather than mistitled.

None of these three are wrong, exactly. They're the fixes people reach for because they don't require reading the competition first, and reading the competition is the one step that decides whether the other two will actually work.

A quick way to tell the difference: if the fix took under five minutes and didn't involve reading a single competing page, it's a mechanical fix. Mechanical fixes are worth doing, they just shouldn't be the whole plan, and treating them as the whole plan is the most common reason a striking distance list looks the same six months later.

A ten-minute triage, run twice a month

The workflow that fits into an actual week looks smaller than most guides suggest, and that's mostly the point.

Pull the striking distance list from Search Console. Pick the five keywords with the highest impressions, not the five you feel like fixing today. Run the top results through a quick summarize pass, log what's missing directly into the page's working doc as you go, and write the fix while the gap is still fresh in your head.

That logging step matters more than which tool does the summarizing. A gap noticed and not written down gets re-discovered, at cost, three months later, usually during the next audit that finds the same keyword still stuck.

Google's AI Overviews complicate the picture slightly, in a way worth naming. Citations inside AI Overviews increasingly pull from pages ranking well below the top five organic results, which means a page stuck at position 12 isn't automatically invisible anymore. It's a real reason the reading pass matters more now than it did two years ago: a page that explains a gap clearly can get cited before it ever climbs the blue links.

Five keywords a session, twice a month, adds up to somewhere between 120 and 150 reviewed rows a year on a site with a moderate archive. That's slower than a bulk rewrite sprint. It's also the version that survives being done by one person with a real week, rather than the version that looks good in a planning doc and never runs past month two.

What we'd actually keep doing

Skip the tools that promise to automate the whole audit end to end, gap analysis and rewrite included. The reading is the part that teaches something. Automating it away removes the one step where a person actually learns what the competition knows that the page in question doesn't.

Keep the twice-a-month cadence, the five-keyword cap, and the plain habit of reading before rewriting. It's not a bigger system than what most guides propose. It's a smaller one, sized to actually get used past the first week.

The list of striking distance keywords will never hit zero. New rows appear every time a page slips from position 9 to 11, or climbs from 22 into range. Treating the twice-a-month pass as maintenance, not a project with an end date, is what keeps it from turning into the kind of backlog nobody opens again.