Reading SEO reports

Search Console Impressions but No Clicks: What a New Site Can Check

Check a relevant query and page in Search Console before deciding what to change.

Your new site is appearing in Google Search Console, but the clicks column is still empty. The report does not say why: the queries, the page, its position and the search result may each offer clues. A new site may have only a short reporting history, so start with a specific query and page before deciding what to change.

Here is a small example from our own site, SEOHabit. On October 31, 2026, our preliminary rolling 24-hour Search Console view showed 50 impressions and one click across the property. One visible query, “comprobar seo,” had five impressions and no clicks. The property total covers different queries and locations; the zero-click figure belongs to that one Spanish-language query, not the whole property. This preliminary view is not a daily user count or a controlled test. Five impressions are too little to tell us whether that query's page, title, position, or search intent needs work. We do not know whether those impressions became customers.

For perspective, one click out of five impressions would be a 20% CTR; the difference from zero clicks is just one event. Find the page associated with a relevant search, and read the two together before treating a percentage as evidence of a problem.

Start with the report's scope

Open Search Console's Search results Performance report for your verified property. Pick Web search and a completed date range, such as the last 28 days if your site has that much history. A shorter history may still be useful for finding questions, but it will leave less evidence for judging them. Record the dates, country, device, and any filters you use. The 24-hour view is preliminary; Google says recent data can change as processing continues. Don't compare a partial latest day with an entire earlier day as if they were equivalent.

Turn on impressions, clicks, CTR and average position. Google's Performance report guide defines CTR as clicks divided by impressions. For each recorded impression, Google uses the topmost position for the property or page being measured; average position averages those position values. A query with more impressions contributes more position values to that average than a query with fewer impressions. A sitewide average across many queries is not the rank of your most important keyword. Results also vary by location, device and other context, so a manual search that does not reproduce a result is not proof the report is wrong.

Search Console measures Google Search activity. It does not tell you how many distinct people visited your site or whether they became customers. If you also use analytics, review the relevant landing page and meaningful actions separately, subject to your consent and measurement setup. Do not add the two tools' user and click counts together.

Find one relevant query and its page

In the Queries tab, sort by impressions and look for a query a potential customer might use. Brand searches and non-brand searches answer different questions, so examine them separately. A query that happens to include your brand could be someone looking specifically for you; a non-brand query may be a broader discovery opportunity. Search Console does not expose every query: anonymized queries and other reporting limits can make table rows differ from chart totals. Do not add the visible query rows and call that the whole site's search traffic.

Click a relevant query to filter the report, then open the Pages tab. Choose a displayed page relevant to the query and inspect its impressions, clicks and average position in the same date range. If the page has only a few impressions, record the observation without drawing a conclusion from its CTR. Add country and device filters if those matter to your audience and the remaining sample is useful. Google documents the filters and their limitations. Property-level and page-level aggregation can count appearances differently: two pages from one property on the same results page for a query count as one property impression but one impression for each page. Keep the same aggregation when comparing figures.

Read the page as someone who just searched that phrase. Does it answer the question or offer the service the query suggests? Can a visitor tell what the page does from the opening screen? If the query is relevant but the page only mentions it in passing, add the missing explanation or link to a genuinely useful page that already answers it. If the query has a different intent from your business, do not force the page to target it merely because impressions appeared.

Treat position and the snippet as clues

A low average position for a relevant query can help explain why a result receives little attention, but it does not tell you a single fixed rank or identify the cause. Compare that query and page over a consistent period; avoid diagnosing a site from a mixed sitewide average. When a relevant query and page have impressions across multiple completed periods, inspect the page's title, main heading and description. Are they accurate and specific about what the visitor will find? Correct a vague or misleading title when you can identify the problem. Do not promise a result that the page cannot deliver just to seek a click.

Google generates title links using several sources, including page titles and headings, and primarily generates snippets from page content, sometimes using the meta description. A rewritten description may never be displayed for a particular search. If you do inspect a live result, note the query, country, device and date; treat it as one observation rather than everyone's search experience.

Change one useful thing and keep the old evidence

Suppose you find a page about choosing an SEO tool that gets repeated impressions for a query about checking a homepage. Before editing, save the page URL, query, period, country, device, impressions, clicks and position. Write down the actual mismatch you observed: for example, the page lists tools but never explains how to perform a first check. This is an illustrative example, not a result from a customer.

If a homepage-check walkthrough belongs on that page, add a concrete walkthrough. If an existing page already covers it, make the relationship clear with a useful internal link instead. Record the date and what changed. Later, compare the same page and query using the same filters and an equivalent completed period, leaving enough time for data to accumulate and for Google to recrawl. Search demand, results and other changes can move at the same time, so a before-and-after comparison alone does not establish that your edit caused a change. With little data, the honest result may still be “too early to tell.”

A technical check can help identify a specific page issue, but it cannot explain every missing click or predict a ranking. Our website SEO checker offers a limited first homepage check after registration and adding a site. You choose when to start it; the first check does not require DNS verification. Review any finding against the page and make changes in your own environment. Recheck the relevant page manually or use an available check under your account's existing allowance. Ownership verification and subscription requirements still apply to other capabilities. The Search Console query and page evidence remains a separate step.

At the next review, return to the same page and query. Compare the saved figures with the same filters, and keep an unanswered result open if the data remains sparse.