Google Search Console tells you how your website appears in Google Search and which results bring people to it. Its Performance report is useful once you stop treating every red percentage as a problem and start asking what changed for a particular page and audience.
This guide is about reading the data, not connecting your website. If you haven't verified ownership yet, start with the Search Console setup walkthrough. You don't need a paid reporting tool for the review below.
The Four Metrics, in Plain Language
Open the Search results Performance report and enable clicks, impressions, average CTR and average position. Keep the selected property and search type in mind: the figures describe that report, not every visit to your business.
| Metric | What it describes | What it doesn't prove |
|---|---|---|
| Clicks | Clicks from Google Search results to your site. | Unique visitors, leads or sales. |
| Impressions | Recorded appearances of your result. Counting rules depend on the result type. | That someone carefully read your listing. |
| Average CTR | Clicks divided by impressions, expressed as a percentage. | Whether your content or business is successful on its own. |
| Average position | The average position of the topmost result for the property or grouping being measured. | A fixed ranking that everyone sees. |
These definitions follow Google's Performance report overview. For example, 60 clicks from 3,000 impressions produces a CTR of 60 ÷ 3,000 × 100 = 2%. Those are invented numbers, not an industry benchmark or a result from this website.
A useful reading habit: say “this page received 60 recorded search clicks in the selected period,” not “60 people visited the website.” The second statement changes both the unit and the scope.
Why Average Position Isn't Your Website's Rank
A property-level average mixes many searches. If two results from your site appear in one search, Google uses the topmost position for the property's position calculation. Different search features also have different counting rules. Google's clicks, impressions and position documentation explains those details.
Consider this deliberately simplified, hypothetical example. In the first period, your only 100 impressions are at position 3. In the next period, those 100 appearances remain at position 3, and you gain another 100 at position 15 for new searches. The average moves from 3 to 9: ((100 × 3) + (100 × 15)) ÷ 200.
The average looks worse, but nothing in this example lost its old position. Your visibility expanded. Real reports contain more variation, but the lesson holds: before rewriting a page because its average changed, check which queries and pages entered the mix.
Use position as a diagnostic clue alongside clicks and impressions. A filtered query-and-page trend is usually more useful than a single site-wide number. It still represents an average, not a promise about the result you'll see in a manual search.
Set Up a Fair Comparison First
Before interpreting the chart, make the comparison repeatable:
- Confirm the property. Check that you're looking at the intended domain or URL-prefix property, especially if you manage multiple sites.
- Keep the search type consistent. Start with Web for an ordinary website review. Don't compare one period's Web results with another period's Image results.
- Compare equal periods. Use the date comparison control. Two complete 28-day periods are a practical starting point because they contain the same weekday mix, not because 28 days is a Google requirement.
- Record active filters. A page, query, country or device filter can explain an apparently missing chunk of traffic. Clear old filters before beginning a different question.
Google's filtering and comparison instructions cover those controls. For a seasonal business, also compare a similar season when you have enough history. A winter service shouldn't be judged only against summer demand.
Use completed days for routine decisions. The freshest figures can be preliminary and change as processing continues; Google distinguishes that data in its report data notes. A quiet morning isn't evidence that yesterday's page edit failed.
Move from the Whole Site to One Useful Question
Start with the Pages table. Choose a page that matters to the business, apply its page filter, then open Queries. You're now asking: “What searches brought this particular page into results?” That's a more actionable question than “How is our SEO doing?”
Read the visible queries for meaning, not just volume. For a consultancy's service page, “technical SEO audit cost” and “what is SEO” suggest different needs. The first may call for clearer buying information; the second may belong in an educational guide. Use our search intent guide before assuming both should lead to the same content.
Next, split by device or country only when it helps answer the question. A mobile decline might deserve a mobile-page check. A country difference might reflect an audience you don't serve. Avoid slicing a small dataset until every row contains one impression.
It can also help to separate searches containing your brand from other searches. A simple query filter can create a useful subset, but aliases and spelling variations need thought. Some properties have a branded-query filter; availability and classification aren't universal. Google's dimension documentation explains the limitations.
Don't turn every query into a new article. If several searches ask the same underlying question, improving one suitable page may be the better decision. The keyword research guide explains how to group topics and map them to pages.
Three Patterns Worth Investigating
1. Impressions rise, CTR falls, clicks rise
Here's another hypothetical example, using the same report scope in both periods:
| Period | Impressions | Clicks | CTR |
|---|---|---|---|
| Earlier | 3,000 | 60 | 2% |
| Later | 6,000 | 90 | 1.5% |
Clicks increased by 50%, even though CTR fell by 0.5 percentage points. First inspect the new query and page mix. Broader visibility could explain the change. Then ask whether the extra clicks reach useful pages and lead to appropriate next steps. Neither “CTR down” nor “clicks up” is a complete business verdict.
2. Impressions and clicks fall together
Find where the loss is concentrated before deciding on a fix. Is it one URL, a whole directory, a device group or most of the site? Compare the timing with known site changes and seasonal demand. Google's traffic-drop guide covers technical issues, changing demand, ranking changes and reporting anomalies as possible causes.
My first task would be to list the affected pages and dates. If an important page also fails to open or has an unexpected indexing status, investigate that evidence with the indexing troubleshooting guide. A chart shape alone doesn't identify the cause.
3. CTR falls while the comparable slice looks similar
If the same page and query group has broadly similar impressions and position, review how the page is presented and whether it still answers the search need. Check the visible search result as a snapshot, not a definitive reproduction of everyone else's results.
A title experiment might be reasonable if the existing title is vague. Write down the problem, proposed change and review period first. Keep the title accurate; promising something the page doesn't deliver isn't a useful test. See the on-page meta tag guide for implementation.
Why the Numbers Don't Always Match
Query rows aren't a complete search log. Privacy-protected queries are omitted from the table, and other reporting limits can hide rows. Some hidden-query data can remain in chart totals, but applying a query filter changes what's included. Most performance data is attributed to Google's chosen canonical URL. These are documented reporting behaviors, not evidence that an export is broken.
Chart totals and table sums can measure different groupings. Property-level aggregation and page-level aggregation aren't interchangeable. Exported visible rows shouldn't be treated as a complete ledger you can always reconcile to the headline chart.
Search Console clicks won't necessarily equal GA4 organic sessions. The tools measure different events and use different processing rules. Consent, JavaScript tracking, time zones and channel scope can also affect a comparison. Google's data-discrepancy notes explain common reasons. Don't force agreement by changing tags without diagnosing the difference.
Use Search Console to study Google Search visibility and clicks. Use properly configured analytics to examine behavior after arrival and meaningful actions. Our GA4 setup guide covers that separate measurement job.
A Small Review Routine You Can Repeat
Set aside a short, regular review and leave with one decision, not a long list of unexplained percentages:
- Save the scope: property, dates, search type and filters.
- Find one meaningful change: a page with lost clicks, new relevant queries or a persistent mismatch between intent and content.
- Check an alternative explanation: seasonality, query mix, recent deployment or a reporting difference.
- Choose a proportionate action: inspect a broken URL, clarify an answer, improve a relevant internal link, or deliberately make no change.
- Log what happens next: URL, evidence, hypothesis, edit date and when you'll review comparable data again.
For a new site with little data, the sensible outcome may be “keep publishing useful material and collecting a baseline.” One click becoming two is a 100% increase, but not strong evidence of a repeatable improvement. You can still check important URLs, site navigation and whether each page serves a clear need.
For a broader investigation, use the SEO audit checklist. Performance data helps prioritize questions; it doesn't replace inspecting the website.
Need Help Deciding What to Investigate?
I offer a free initial review of a small selection of public pages, with up to five priority findings or next steps by email. It's not a comprehensive audit. Search Console analysis, a multilingual crawl or implementation would need a separate agreed scope and any necessary access.
Request a free website reviewFrequently Asked Questions
Where to Go Next
- Connect and verify your Search Console property if you haven't started collecting data.
- Turn relevant queries into a content plan without publishing a page for every keyword.
- Set up GA4 measurement to study what visitors do after arriving.
I'm a developer who moved into technical SEO. I trace search problems through crawling, rendering, indexing, templates, content and performance, then implement the fixes instead of handing over a generic export. Request a free website review and I'll review your site personally.