Find pages ranking 4 to 20 on Google and what to change on each

By

Use SEO Bot's Quick Wins check to list pages ranking 4 to 20 on Google, see the clicks each could gain at position 3, and get the edits to make.

Some of your pages are almost there. They show up for a search thousands of times a month, but at position 6, or 9, or on page two. Nobody clicks that far down, so the impressions turn into a handful of visits.

These are the cheapest wins in SEO. The page already ranks, Google already thinks it’s relevant, and a better title or one missing section can move it up a few spots. The hard part is finding them. Search Console has the data, but it doesn’t tell you which pages are close, how much each one is worth, or what to change.

SEO Bot has a check called Quick Wins that does that. It reads the last 28 days of Search Console data, keeps the searches where a page ranks between 4 and 20, and estimates the clicks each page would get at position 3. Then it reads each page and writes the edits.

At the end you’ll have a ranked list of pages, a checklist of edits per file, and a follow-up that checks in 4 weeks whether they moved.

What you need

SEO Bot runs on macOS 14 or later, on Apple silicon and Intel Macs. After purchasing it, download the app zip from your Polar receipt, unzip it, and move SEO Bot.app into Applications. The receipt also has the MIT-licensed source code of the same version.

Quick Wins needs Google Search Console, connected in the app’s Settings. In the Google Cloud console, turn on the Search Console API, create an OAuth client of type Desktop app, paste its ID and secret into SEO Bot’s Settings, and click Connect with Google. SEO Bot only asks for read access, and the check costs nothing to run.

The commands here use seobot, the command line tool inside the app. Install it with SEO Bot → Install Command Line Tool…. It goes into ~/.local/bin, so add that folder to your PATH if your shell can’t find it. Everything also works from the app’s sidebar.

Before you start, check that Search Console is connected:

seobot status
Search Console  connected
DataForSEO      not set up
Plausible       not set up

Set up data sources in the SEO Bot app's Settings. Data: /Users/flavio/Library/Application Support/SEO Bot

The site, pages, searches and numbers in this tutorial are examples. hostingpicker.dev is a fictional hosting comparison site, with its source in /Users/flavio/dev/hostingpicker.

Add the site with its Search Console property and source folder

Quick Wins needs to know two things about your site. The first is its Search Console property, like sc-domain:hostingpicker.dev. That’s where the searches and positions come from, and without it the check stops before it fetches anything. The second is optional but makes the report far more useful: the folder with the site’s source. With it, SEO Bot turns /static-site-hosting/ into src/posts/static-site-hosting.md, so every edit names a file. Without it, you get page paths and find the files yourself.

Add the site with its source folder:

seobot add https://hostingpicker.dev --source ~/dev/hostingpicker
Added hostingpicker.dev.

When Search Console is already connected, add picks the matching property for you. If you added the site before connecting Google, set the property yourself. seobot edit changes only the options you pass:

seobot edit hostingpicker.dev --search-console sc-domain:hostingpicker.dev
Updated hostingpicker.dev.

In the app, both fields are in Site Settings…, under Source folder and Search Console property.

Run Quick Wins on the last 28 days

The check does two passes. First it asks Search Console for 28 days of data twice: once per page, to learn your own click rate at each position, and once per page and search, to find the close ones. A search counts when it ranks between 4 and 20 and has at least 30 impressions. Then SEO Bot downloads the top 25 pages and reads their title, H1, headings, meta description and text. That second pass is what turns numbers into edits. It’s also why the site has to be reachable while the check runs.

seobot run quick-wins --site hostingpicker.dev

Progress goes to stderr, and the report prints as Markdown when it’s done:

Fetching Search Console data…
Reading 3 pages…
# Quick Wins for hostingpicker.dev

Oct 16 – Nov 12, 2026 · Run Nov 16, 2026 at 7:18 AM

3 pages rank just below the top for searches that could bring about 980 more clicks every 28 days.

## Numbers

- Pages: 3 (with searches at positions 4 to 20)
- Potential clicks: +980 (every 28 days, at position 3)
- Searches: 10 (close to the top 3)

The period ends a few days before the run date, because SEO Bot asks Google for final data only. In the app, click Quick Wins in the sidebar, then Run.

The run is saved. List it with:

seobot reports
ID        SITE               TOOL        DATE              FIXED  SUMMARY
91856746  hostingpicker.dev  quick-wins  2026-11-16 07:18         3 pages rank just below the top for searches that could bring about 980 more cli

The summary is cut at the column width. The first few characters of the ID are enough for every other command.

Read the potential clicks for each page

The Potential number is what sorts the report, so it helps to know where it comes from. For each search, SEO Bot multiplies its impressions by the click rate a result gets at position 3, then subtracts the clicks the page already gets. The click rate isn’t a generic industry number. It’s your own: SEO Bot takes the median click rate of your pages at each position, blends it with a typical curve where you have few pages, and never lets a lower position beat a higher one. A page’s potential is the sum over its searches.

How Quick Wins picks and ranks pagesSearches at positions 4 to 20 with at least 30 impressions are kept. Each gets a potential from impressions times your click rate at position 3, minus current clicks. Pages are sorted by total potential, and the top 25 are read to write the edits.NoYes28 days of SearchConsole dataSearch at position 4to 20 with 30+impressions?IgnoredPotential =impressions x yourCTR at position 3 -clicksAdd up per page,sort by potentialRead the top 25pagesEdits: title, H1,H2s, metadescription, length,internal links

Example 1: a page that ranks 6.8 for its main search

Here’s the finding for /static-site-hosting/:

### /static-site-hosting/

https://hostingpicker.dev/static-site-hosting/
File: src/posts/static-site-hosting.md
+342 clicks · Where to host a static site in 2026 | Hostingpicker
Clicks: 55 · Impressions: 3,890 · Potential: +342

- Put “free static site hosting” in the title. It brings 2,600 impressions at position 6.8, and the title doesn't mention it.
- Use “free static site hosting” in the H1 too.
- Give “host static website free” its own H2 (820 impressions, position 9.1). The text mentions it, but no heading does.
- Link to /static-site-hosting/ from 2 or 3 related pages, with “free static site hosting” as the anchor text.

  - **free static site hosting** (+227): Position 6.8 · 2,600 impressions · 38 clicks
  - **host static website free** (+75): Position 9.1 · 820 impressions · 9 clicks
  - **static site hosting comparison** (+36): Position 7.4 · 410 impressions · 6 clicks
  - **hostingpicker github** (+4): Position 5.0 · 60 impressions · 2 clicks

The page gets 2,600 impressions for “free static site hosting” and 38 clicks. On this site, a result at position 3 gets about 10% of impressions, so that’s around 265 clicks. Minus the 38 it has, that’s the +227. The page’s title is about where to host a static site, but it never says “free”, the word people search with. That’s the first edit.

Notice “hostingpicker github”. It’s listed, but no edit targets it. Searches with words like “github”, “login” or “download” are people looking for another site, so SEO Bot never builds advice around them.

Turn each finding into edits on the page

The findings are the data, and the Tasks section is the to-do list. It’s sorted by file, so you open each file once. Each task is one of a small set of edits, checked in order: the main search goes in the title and the H1, searches the page barely mentions get a new section with an H2, searches the text covers but no heading names get an H2, a missing meta description gets added, and a short page that ranks below 8 gets expanded. Then every page gets internal links with the main search as anchor text. When a task changes existing text, “Find” quotes it.

## Tasks

Each heading is a file to edit, relative to /Users/flavio/dev/hostingpicker, with the page it builds. "Find" is the text to look for in it.

### src/posts/static-site-hosting.md

Page: https://hostingpicker.dev/static-site-hosting/

- [ ] Put “free static site hosting” in the title. It brings 2,600 impressions at position 6.8, and the title doesn't mention it.
  Find: “Where to host a static site in 2026”
- [ ] Use “free static site hosting” in the H1 too.
  Find: “Where to host a static site in 2026”
- [ ] Give “host static website free” its own H2 (820 impressions, position 9.1). The text mentions it, but no heading does.

The title rewrite is the one edit to do carefully. A title brings in every search the page ranks for, not just the one in the task. So keep “static site” in it and add “free”, rather than swapping the whole thing. If a page already ranks on page one and the problem is the click rate, that’s a different check, Title and CTR Fixes.

Example 2: a thin page further down

/coolify-review/ ranks 12.6 for “coolify review”, on page two. Its advice is different:

- Give “is coolify free” its own H2 (380 impressions, position 14.2). The text mentions it, but no heading does.
- Cover “coolify vs dokku” (240 impressions, position 17.9). The page barely mentions it, so add a section about it with its own H2.
- Add a meta description that mentions “coolify review”.
- The page has 305 words. The results above it likely go deeper, so expand it to cover the searches listed for it.

The title already has the main search, so there’s nothing to fix there. The problem is depth. The page has no meta description, it never discusses Dokku, and it’s 305 words long. SEO Bot only suggests expanding a page under 500 words when its main search ranks below 8. The static hosting page is longer and ranks 6.8, so it didn’t get this task. Here a new “Coolify vs Dokku” section and an “Is Coolify free?” heading are worth more than any title.

The internal links come last, under Across the site, because they’re edits on other pages:

### Across the site

- [ ] Link to /cheap-vps-hosting/ from 2 or 3 related pages, with “cheap vps hosting” as the anchor text.
- [ ] Link to /static-site-hosting/ from 2 or 3 related pages, with “free static site hosting” as the anchor text.
- [ ] Link to /coolify-review/ from 2 or 3 related pages, with “coolify review” as the anchor text.

Quick Wins doesn’t pick the pages to link from. Find orphan and weakly linked pages shows the Internal Links check, which suggests the paragraph and anchor for each link.

Hand the report to a coding agent

You can work through the Tasks by hand. If you use Cursor or Codex, the report can go to them instead. seobot prompt prints the prompt an agent needs. It points at the saved report, explains the job in one paragraph, and tells the agent to work in the source folder. The interesting part is the instruction to keep the existing voice and not pad the text. Without it, “expand this page” tends to come back as filler.

seobot prompt latest --site hostingpicker.dev --tool quick-wins
Use the Quick Wins report SEO Bot made for hostingpicker.dev (https://hostingpicker.dev/) to improve the site.

3 pages rank just below the top for searches that could bring about 980 more clicks every 28 days.

Improve these pages so they move up for the searches listed under each one. Apply the changes the report suggests in the page sources: titles, H1s, new sections for searches the page doesn't cover yet, and a meta description where it's missing. Keep the existing voice and don't pad the text.

The rest names the report file, tells the agent to work in /Users/flavio/dev/hostingpicker, and to run seobot fixed with a note when it’s done.

Read the prompt before you send it. It tells the agent to verify the result, then commit and push the changes on its own, without force-pushing. If your site deploys on push, that’s a live change. Add --cursor or --codex to open a new agent with the prompt, which waits for you to send it. In the app, Fix with Cursor and Fix with Codex do the same. Right-click a finding for Fix This with Cursor or Copy Prompt for This to send one page.

If you’d rather feed the data to your own script, add --json to seobot report. Each finding has the page url, its file, and an items list with every search and its potential.

Mark the report fixed and check again in 4 weeks

A better title doesn’t move a page the next morning. Google has to recrawl it, positions settle over days, and Search Console’s final data lags behind. So SEO Bot waits 4 weeks before it judges a Quick Wins fix. Marking the report fixed records what changed and which findings you skipped, and schedules that follow-up. Without the mark, the next run is just another list. With it, the follow-up tells you how many fixed pages it no longer flags.

Example 3: a page that didn’t load on the second run

Say you run the check again before handing it off, and meanwhile /coolify-review/ started returning an error. The run still lists the page, with this task instead of the edits:

### src/posts/coolify-review.md

Page: https://hostingpicker.dev/coolify-review/

- [ ] The page didn't load, so SEO Bot couldn't check it. Make sure “coolify review” is in its title and H1.

SEO Bot only reads pages that return a 200 with HTML, so a 404, a server error or a timeout all end up here. The search data still comes from Search Console, which is why the potential is the same. There’s no internal link task for the page either. Fix the URL, check it in a browser, and run the check again. Each run saves a new report, and older ones stay in seobot reports.

When the changes are live, mark the report fixed. Here we skip the Coolify page on purpose:

seobot fixed 7fe9 --skip /coolify-review/ --note "New title and H1 on /static-site-hosting/, two new sections on /cheap-vps-hosting/ (4c9e2a1)"
Marked 7fe978f7, Quick Wins for hostingpicker.dev as fixed on Nov 16, 2026.
Skipped 1 finding:
  https://hostingpicker.dev/coolify-review/
Note: New title and H1 on /static-site-hosting/, two new sections on /cheap-vps-hosting/ (4c9e2a1)
Follow-up on Dec 14, 2026: Run Quick Wins again and check whether the pages moved up for their searches, for the 2 fixes from Nov 16.

The follow-up is in the to-do list:

seobot todo --site hostingpicker.dev
December 2026
  Dec 14  29cb9363  hostingpicker.dev  Run Quick Wins again and check whether the pages moved up for their searches, for the 2 fixes from Nov 16.

Running seobot fixed again replaces the mark. To take it back, seobot fixed 7fe9 --undo clears it and removes the follow-up:

seobot fixed 7fe9 --undo
Cleared the fixed mark on 7fe978f7, Quick Wins for hostingpicker.dev.

Marking and undoing only touch SEO Bot’s records. SEO Bot never edits your files, so Git is the undo for the edits themselves.

Let it run every 2 weeks

You don’t have to remember to rerun this. While the app is open, SEO Bot reruns Quick Wins on its own every 2 weeks and adds new findings to To Do, with Fix buttons. seobot check does the same from the terminal, and seobot check --dry-run lists what it would do without running anything.

Quick Wins pairs well with two other checks. Find pages that lost Google clicks covers pages going the other way, and Find and fix keyword cannibalisation covers two of your pages splitting one search. If one search shows up under two pages here, fix that first. How to run SEO checks from the terminal shows how the other reports go to agents the same way.

If something looks wrong

  • If seobot run quick-wins stops with “Search Console isn’t connected. Connect it in Settings.”, open SEO Bot’s Settings, paste the OAuth client ID and secret, and click Connect with Google.
  • If it stops with “Pick the Search Console property for hostingpicker.dev in the site’s settings.”, the site was added before Google was connected. Run seobot edit hostingpicker.dev --search-console sc-domain:hostingpicker.dev.
  • If it stops with “Your Google connection expired or was revoked.”, click Disconnect, then Connect with Google in Settings. An OAuth client in Testing gets its refresh token expired after 7 days, as Google’s token expiration rules say.
  • If the report says “No pages rank between positions 4 and 20 with enough impressions to be worth a push.”, no search on the site has 30 impressions in that range over 28 days. A new site often gets this.
  • If a page’s only task is “The page didn’t load, so SEO Bot couldn’t check it.”, open the URL in a browser. It has to return a 200 with HTML.
  • If a Tasks heading shows a page path instead of a file, SEO Bot couldn’t match the URL to a file. Check that Source folder points at the project root.
  • If a search you care about has no edit, check its words. Searches with “github”, “login”, “download” and similar are treated as looking for another site, and look-alike typos of words on the page are skipped too.
  • If Run Again is greyed out after marking the report fixed, that’s the follow-up waiting for 4 weeks of new data. seobot run quick-wins still runs it early.

Get SEO Bot

Run 16 SEO checks on your websites and turn each report into concrete work for you, Cursor or Codex. Includes a native Mac app, CLI and full MIT source.

See SEO Bot → · Read the docs · $20. See the app page for tax details, with full source code.

More tutorials for my apps →

Want me to talk about your product? You can sponsor this site.