Skip to content
EightySixOS

How to Find SEO Opportunities in Google Search Console

Learn what clicks, impressions, CTR and position actually mean in Search Console, and how to spot real opportunities hiding in the data.

August 202610 min read

At a glance

  • Clicks, impressions, CTR and position each tell you something different, read them together, not alone
  • Average position is an average across every impression for a query or page, not a fixed rank
  • Striking-distance queries (roughly positions 5-15) are usually your fastest wins
  • High impressions with low CTR often points to a title and description problem, not a ranking problem
  • Day-to-day position swings are normal noise, judge trends over weeks, not days

Google Search Console is the only place you get to see, in Google's own words, how your site actually performs in search results: what people typed, what pages showed up, and whether anyone clicked. Most business owners open it, glance at a chart going up or down, and close it again. That chart is not the point. The opportunities are buried in the query and page tables underneath it, and finding them takes a specific way of reading the data, not just staring at a trend line.

This guide walks through what each metric actually measures, how to compare time periods properly, and then the specific patterns worth hunting for every time you open the Performance report.

What the four core metrics actually mean

Search Console's Performance report is built around four numbers. They sound simple, but each one has a precise definition worth understanding before you try to act on it.

  • Clicks: how often someone clicked through from a Google search result to your site.
  • Impressions: how often a link to your site appeared on a search results page, whether or not anyone scrolled to see it or clicked it.
  • CTR (click-through rate): clicks divided by impressions, shown as a percentage. It answers "of everyone who saw this result, what share clicked it?"
  • Average position: where your page tended to rank, on average, across every impression it received.

That last one deserves more explanation, because it is the most commonly misread metric in the whole report. According to Search Console's own documentation, position is "a relative ranking of the position of your link on Google, where 1 is the topmost position." Average position takes every single impression a query or page received over the date range, whatever position it happened to rank at that moment, and averages them together. This matters because a single query can rank at wildly different positions depending on the exact phrasing someone typed, their location, their device, and what else Google decided to show alongside your result that day. A page might rank 3rd for one variation of a search and 14th for another, and Search Console reports "position 8.5" for that query, an average that no individual searcher ever actually saw. Position is a summary of a spread, not a single fixed rank you hold.

Query data versus page data

The Performance report lets you look at the same metrics through two different lenses, and switching between them is where most of the useful analysis happens.

  • Query data shows you the actual search terms people typed before your site appeared. This tells you demand and intent: what people are searching for.
  • Page data shows you which URLs on your site received the clicks and impressions. This tells you supply: what content is actually catching that demand.

The real analysis happens when you combine them. Click into a specific page and look at the queries feeding it, or click into a specific query and see which pages of yours are competing for it. That combination is where most of the patterns below come from.

One limitation worth knowing upfront: Search Console does not show every query. To protect user privacy, queries made very rarely, or ones that could contain personal or sensitive information, are grouped and left out of the query table entirely (Google calls these "anonymized queries"). They are still counted in your totals and charts, just not listed by name. If your click and impression totals do not fully add up when you sum the visible query rows, this is usually why.

Comparing date ranges properly

The single most common mistake in reading Search Console is comparing the wrong two things. Looking at "yesterday versus the day before" or eyeballing a jagged daily line and reacting to a dip is not analysis, it is noise-chasing. Search data is naturally lumpy day to day: weekends behave differently to weekdays, news events shift search behaviour temporarily, and Google's own systems introduce natural variance.

Use Search Console's built-in comparison feature to set two ranges of equal length back to back, for example the last 28 days against the 28 days before that, or the last 3 months against the previous 3 months. Equal-length, adjacent periods are what let you separate a real shift from ordinary fluctuation. If you want to account for seasonality (a landscaping business searched for differently in July than January), compare the same period to a year earlier as a second check, not instead of the adjacent-period comparison.

Also account for the data delay: Search Console typically shows data 2 to 3 days behind real time, and this can occasionally stretch further during periods of high processing load, per Search Console's data documentation. Don't read anything into the last two or three days on the chart, that data is still settling.

Opportunity pattern 1: high impressions, low CTR

This is a page or query getting seen a lot, but not clicked much relative to how often it appears. It shows up in the data as a row with a large impression count and a CTR well below what similar-position rows are achieving.

This matters because impressions without clicks usually means one of two things: either your title and meta description aren't convincing the searcher this result answers their question, or the page ranking is genuinely the wrong page for what that searcher wants (a mismatch covered separately below). If the page itself is a good match for the query, this is almost always a title and description problem, and it is one of the cheapest wins available because you are not creating new content, you are rewriting an existing tag.

A query with 4,000 impressions and a 1% CTR sitting at position 6 is worth more attention than a brand-new page with 40 impressions, because the audience is already there.

For a full walkthrough of fixing this specific pattern, see How to Improve Google Search CTR With Better Titles and Descriptions.

Opportunity pattern 2: striking-distance queries and pages

Striking-distance queries are ones sitting roughly between position 5 and position 15, close enough to page one (or close enough to the top of page one) that a focused improvement could realistically move them there. Sort your query table by position and scan this band specifically, rather than only looking at your best or worst performers.

This matters because the click-through-rate gap between position 10 and position 4 is usually far larger than the gap between position 20 and position 15, so a small move in this range tends to produce a disproportionately large increase in actual clicks. These are also generally your lowest-effort wins: a page already ranking at position 8 has already proven Google considers it relevant, it usually needs reinforcement rather than a rebuild. Improving the on-page content, adding more depth, tightening internal links to that page, are the kinds of changes that tend to move a striking-distance page rather than requiring an entirely new page.

Opportunity pattern 3: growing queries

A growing query is one where impressions, clicks, or both are trending upward over consecutive comparable periods. You spot this by comparing your current date range against the prior equivalent range at the query level, sorted by the biggest positive change in clicks or impressions.

This matters because it tells you demand is increasing for something you already rank for, which is exactly the moment to reinforce it: adding more detail, updating the content to stay current, adding it as an anchor for internal links from related pages. Growing queries are also an early signal of a genuine shift in what your customers are looking for, worth noticing before a competitor does.

Opportunity pattern 4: declining queries

The inverse of growth: a query or page where impressions, clicks, or average position are trending in the wrong direction across two comparable periods. Again, this only means something if you're comparing equal-length adjacent ranges, not two arbitrary days.

This matters because a real decline usually has a specific, findable cause: a competitor published something stronger, the page went stale relative to what's now ranking around it, a technical issue affected how the page is being crawled or indexed, or the underlying search demand for that term is genuinely shrinking. Declining queries are worth investigating precisely because they are rarely random, something changed either on your page, on a competitor's page, or in what people are searching for.

Opportunity pattern 5: pages that only partially answer the search

This pattern shows up as a page earning a reasonable number of impressions for a query, but with weak CTR and a middling position that doesn't move even after other improvements. Often the underlying issue is that the page addresses part of the topic the query implies, but not all of it.

For example, a service page about "gutter cleaning" might be earning impressions for "gutter cleaning cost" without ever mentioning price, or a page about a specific repair might be getting impressions for a broader "how to fix" query without covering the beginner steps. Google has decided the page is topically relevant enough to show, but the content itself doesn't fully deliver on what the searcher wanted, and that shows up as a plateau in position and CTR that content tweaks to titles alone won't fix. Expanding the page to genuinely and directly answer that query is usually what moves it. For the mechanics of doing that without starting from scratch, see How to Improve an Existing Web Page Without Rewriting Everything.

Opportunity pattern 6: query and page intent mismatch

Sometimes the wrong page on your own site is the one ranking for a query, or worse, no page on your site directly answers the intent behind a query you're still getting impressions for. You spot this by clicking into a query and checking which URL is actually earning the impressions, then asking honestly whether that's the page a searcher typing that exact phrase would want to land on.

This matters because Google is doing its best to match a query to the most relevant thing it can find on your site, but "most relevant available" and "actually right" are not the same thing. If your homepage is earning impressions for a specific service query because you don't have a dedicated page for that service, that's not a ranking problem, it's a content gap. The fix is building or restructuring content so the right page exists to directly answer that specific intent, rather than trying to force an unrelated page to rank better for it.

Opportunity pattern 7: new search terms appearing

Periodically, entirely new queries show up in your query table that weren't there in previous periods, terms the business didn't anticipate people would use. Spotting these means actually scanning the query list occasionally rather than only sorting by volume or filtering to known terms.

This matters because new queries are a direct signal of how real customers are actually describing what they need, in their own words, which is often different from the language the business uses internally. A landscaper might start seeing impressions for "no-mow lawn alternatives" or a plumber for a brand name of fitting they didn't think to target. These terms tell you where the market's language is moving, and they're worth building content around before the term becomes competitive.

The limits of this data, and why you shouldn't chase daily swings

Search Console is genuine first-party data from Google, but it comes with real constraints worth respecting:

  • Data is typically delayed by 2 to 3 days, and that delay can stretch further during periods of high load, so the most recent few days on any chart are incomplete and should not be judged yet.
  • Very low-volume and potentially sensitive queries are grouped and withheld from the query table to protect searcher privacy, even though they're still counted in your overall totals. You will never see every single query that led to a click.
  • Average position is exactly that, an average across every impression, every query variant, and every context a page appeared in. It is not a single stable rank you can screenshot and treat as ground truth.
  • Search Console shows you correlation, not proof of causation. If you change a page and its position improves the following week, that's a good sign, but Google's ranking systems change constantly for reasons unrelated to your edit, so treat any single before-and-after as a hypothesis worth watching over a longer period, not a confirmed result from one data point.

Positions fluctuate constantly, sometimes by several places, for reasons that have nothing to do with anything you did. A page moving from position 6 to position 8 overnight and back to 6 the day after is normal variance, not a problem to react to. Judge patterns over weeks using the comparison method described above, not by refreshing the report daily and reacting to single-day movement. The opportunities in this guide are the ones that show up as consistent, comparable-period trends, and that consistency is what separates a real signal from ordinary noise.

EightySixOS Solo

Want EightySixOS to flag when something like this needs your attention?

Solo is being built to watch your own site, tell you what changed and why it matters, and point you to the right Guide when there is work to do. Coming soon.