Search Console numbers that look wrong and are not

Several numbers in Google Search Console look like errors and are not. The four we run into most are web addresses starting with http that sit at position one, pages with impressions but no searches behind them, dates that do not match your calendar, and positions that shift in a week without anything changing on your site. Each has an explanation, and knowing it saves you from fixing a problem that does not exist.

1. http addresses at position one

On an appliance repair client's site, Search Console kept reporting http versions of the home page and the booking page long after the site moved to https. They looked like normal results with unusually good positions.

The booking page was the clue. When we inspected it with Google's URL Inspection tool, the answer was "URL is unknown to Google". It had 510 impressions over 90 days, and an address Google has never crawled cannot rank in ordinary results. The http home page sat at position 1.0 to 1.1 for general searches such as "appliance repairs". That is the local map listing, not a blue link.

What these rows are is the website and appointment links on the business's Google Business Profile, which still point at http addresses. Search Console credits clicks from the profile to them. That makes them a free way to see profile clicks when you have no direct access to profile data. On this site that series fell from 35 clicks to 19 across two fortnights and then to 5 in the latest week, which was a 70 week low, while the normal https page clicks were flat. It was the only series tied to bookings that moved.

What to do: before you fold http into https, look at it separately. Then update the links on your profile to https. It measures website clicks only, not phone calls, which we cover in our post on the Google Business Profile and the map pack.

2. A page with impressions and no searches

The /about page on our own site showed 95 impressions at position 12.0 over 90 days. That looked like a page close to page one. When we filtered the data by that page to see which searches brought it there, we got exactly one row over both 90 and 180 days, a single impression in Portuguese from a leaked chatbot prompt.

Search Console does not list searches that too few people made, to protect privacy. A page whose traffic is spread across many rare searches shows real impressions and almost no names. Writing an answer for it would mean guessing at the question.

What to do: add up the impressions of the searches you can see and compare that with the page's total. If the named searches account for almost none of it, skip the page and note why. A dry result is still a result.

3. Dates that do not match your calendar

Search Console assigns each day to US Pacific time. On our own tooling, a nightly job set to run on a UTC schedule requested a day that Google was still filling and skipped the oldest complete day. Nothing failed. The rows were all there and the counts looked plausible, but the numbers kept shifting after they should have settled.

For a business in Sydney this means the day in a report is not your day, and the last day or two are still moving. Do not judge a campaign or a change on yesterday's figure. If you build your own reporting, take the date from Google's calendar and not from your computer's clock.

4. A position that jumped when nothing changed

Comparing positions across mid-September 2025 is unreliable. When Google stopped supporting a setting that returned 100 results per search, the average position on that same site moved from about 35 to about 21 in a single week. The site had not changed. The measurement had.

For anything that spans that month, compare clicks, not positions. Our post on why average position misleads explains the second problem with it, which is that a page's average blends searches it was never meant to win. That post also covers the impressions that arrive from places you do not serve.

Why these cases matter for a small site

The common thread is that Search Console reports what Google saw, grouped in ways that are not obvious. On a site with a handful of clicks a week, one oddity can outweigh everything real in the report. The http rows on the booking site were links from a business profile, the Portuguese impression was the only named search on a page, and the position shift came from Google changing how results are collected. None of them was a fault in the website, and none needed a code change.

The practical cost of misreading them is wasted work. A team that sees a drop in http clicks may start rewriting pages, when the real action is updating a link on a profile. A team that sees 95 impressions at position 12 may spend a day writing an answer for a question nobody asked. Spotting the oddity first costs a few minutes.

A short habit that helps

Each time a number surprises you, ask three questions before you act:

1. Which address is this, and has Google crawled it?
2. How many searches are actually behind it?
3. Did the way it was measured change?

How this fits our plans

Reading these reports properly each month is a large part of the SEO add-on. For smaller checks, our free website audit is a start. Plan prices are on the pricing page, and you can get started to ask us to look at yours.