Position 11 is the worst rank in SEO. You did the work, you beat almost everyone, and you sit one row below where anybody looks. The click-through rate falls off a cliff between the bottom of page one and the top of page two, so those rankings earn impressions and nothing else.
The queries stuck there are also the cheapest wins you have. They do not need a new article or a link campaign. They need a title rewrite, a section that answers the question properly, or an internal link from a page that already carries weight.
Finding them by hand is the slow part. Export the Search Console query report, filter by average position, sort by impressions, then read a few hundred rows trying to work out which ones are worth the effort. Most of what I used to pick was blog traffic that was never going to buy anything.
Free Guide Mentioned in Video
- Search Console MCP Setup Guide
- The Page-Two Prompt
Connecting Claude to Search Console removes the export step. An MCP server sits between the two, so Claude can pull the position-band report itself and read the live numbers instead of a spreadsheet you prepared for it. You ask for positions 11 to 20 over the last 90 days and get every query in that band with its impressions, clicks, CTR, average position, and the page currently ranking.
The part that changes the work is the intent split. Claude sorts the same list into informational queries, the how and what and why searches, and commercial queries, the ones with buying, comparison, pricing, or “best X” intent. Those two groups need different fixes.
An informational query stuck at 14 usually needs depth. The page answers the question, but thinly, and the results above it answer it better. A commercial query stuck at 12 usually needs proof: a comparison table, real pricing, a case study, a link from a page Google already trusts.
Different diagnosis, different fix, and different value to the business. The commercial ones get done first, because those are the rankings that turn into pipeline rather than pageviews.
In the clip you can see the whole thing run in one pass: the question, the band report coming back, and the two tables that come out of it. The setup takes an afternoon, and after that the report is a question you ask rather than a file you build.
