# Refreshing pages that rank just off page one

> Queries at positions 8 to 20 with steady impressions are the cheapest traffic to win. How to find them in Search Console and decide which page to refresh.

Source: https://netweft.com/blog/refreshing-pages-in-striking-distance
Updated: 2026-10-15

**Sort Search Console queries by impressions, keep those with an average position between 8 and 20, group them by the page that ranks, and refresh the page that collects the most impressions first. Track the queries before the change ships so the result is measurable.**

A query at position 12 with thousands of impressions is a page Google already
considers relevant and nearly good enough. Moving it onto page one is usually
a refresh of an existing page rather than a new one, which makes these queries
the cheapest traffic a site can win. The range people call striking distance
is roughly positions 8 to 20.

## 1. Find the queries

On [Search performance](/docs/search-performance), open **Search Console**,
choose the 90-day window so one bad week does not decide anything, and show
**Search queries**.

1. Sort by **Impressions**, highest first.
2. Read down the **Position** column and keep the queries between 8 and 20.
3. Skip queries with a handful of impressions. A position that rests on ten
   impressions moves with every recrawl.

**Export CSV** keeps the list for the next steps. Reading Search Console costs
no credits.

## 2. Group them by page

Switch the table to **Search pages** and filter by the URLs the queries point
at, or work from the export. Several striking-distance queries usually land on
the same page. That page is the one to refresh: one edit can move all of them.

Rank pages by the impressions their striking-distance queries add up to, and
start at the top.

## 3. Check what the page is missing

For the first page on the list:

- **Look at who ranks above it.** In [Keyword
  research](/docs/keyword-research), run the main query as a seed and choose
  **Who ranks** to see the live top 10. Each look costs 20
  credits for the top 10 results.
- **Compare the intent.** If the top results are comparisons and your page is a
  product page, a refresh will not close the gap; the page answers a different
  question.
- **Run a small audit.** A [site audit](/docs/site-audit) with the page as the
  start URL flags a missing h1, a title that is too long or short, thin content
  and slow responses, at 1 credit a page.

## 4. Track before you change anything

Paste the queries into a [rank tracker](/docs/rank-tracking), one per line,
before the refresh ships. The tracker's history then starts at the old positions, and the next
checks show whether the edit moved them. At the default depth of
20, a check costs 40 credits per keyword
per device, which covers every position up to 20.

## 5. Refresh, then wait

Update the page: answer what the top results answer, tighten the title around
the main query, and link to it from related pages. Then wait two or three
weekly checks before judging it. Record what you changed in the project's
research log under [context](/docs/project-context), so the next refresh
starts from what worked.