Hack #013 · Measurement

Search Console forgets after sixteen months. Keep your own copy.

We started writing a daily row per query into our own database last week. The first day of data told us something four months of looking at the dashboard had not.

2026-09-05 · 3 min · we hit this one ourselves

By Chen Deng · OxOne, Calgary AB

Do this

Search Console keeps a rolling sixteen months and averages everything inside it. Pull the API once a day into a table you own — date, query, page, impressions, clicks, position. It is a short script and it is the only way to ever prove a change worked.

Two things about the Search Console dashboard make it a bad memory.

It only holds sixteen months, rolling. And every number it shows you over a range is an average, so a page that sat at eleven for eighty days and jumped to four for ten of them reports as a nine and looks like nothing happened.

16 moall Search Console will ever hold, rolling
6columns you need to store
$0the API is free and so is the storage at this size

Both are fixable in an afternoon, and the fix is not a subscription.

What to store

One row per query per page per day. Six columns:

date | query | page | impressions | clicks | position

That is the whole schema. A small business generates a few thousand rows a month, which is nothing. Pull it on a daily schedule and never delete any of it.

Use the Search Console API rather than the export button. Manual exports get done twice and then stop, which is the failure mode this is meant to prevent. A service account, a scheduled job, no browser involved.

What it gives you that the dashboard cannot

What our first day said

Every page of ours that ranked for anything was a blog post. Not one service page — the pages that exist to sell something — was ranking for its own subject.

That had been true for months. It was visible in the dashboard the entire time, in the sense that the data was on the screen and nobody had ever sorted it that way. Putting it in a table where we could ask questions of it took ten minutes to answer a question we had not thought to ask.

The part that stings later

Why averages hide it

A page at position eleven for eighty days that jumps to four for ten of them reports as a nine over the quarter. The dashboard is not wrong. It is answering a different question than the one you asked.

Nobody needs this data on the day they build it. You need it in March, when someone asks whether the work done in September moved anything, and the honest answer is that the evidence expired.

Start it before you need it. It is the same argument as verifying Search Console in the first place, one level up, and it has the same shape: the cheapest day was a year ago and the second cheapest is today.

Every one of these came out of work we actually did. If you would rather not do it yourself, book a free 30-minute diagnostic and we will tell you which of these your business is losing money to.

More on this Google Ads management in Calgary Everything we have written