Search Console shows what your archive is about. Read it as a verdict.

A brief says what you want your blog to be about. Google decides what it is about from what you actually published, and the only place that decision is written down is the query list in Search Console's Performance report. Once an archive exists, the gap between the two lists is the editorial agenda. You can close it deliberately or concede it deliberately, but leaving it unread is a choice too.

The brief is an intention. The query list is a verdict.

Every brief we receive opens with a positioning statement: procurement software for mid-sized manufacturers, bookkeeping for creative agencies, a portal for property managers. That statement is what the company hopes to be found for. It is not evidence of anything.

Google's Performance report groups your search traffic by the queries people actually typed, and it counts impressions as well as clicks. Impressions are the useful half. A click tells you a reader was interested; an impression tells you Google considered your page a plausible answer to that question at all. Read the query list sorted by impressions and you are reading how the index has filed you.

Six months into a new archive, the two lists rarely match. The procurement company finds itself shown for how to write a purchase order and for a competitor's product name. The agency bookkeeper surfaces for freelance tax questions it wrote one post about. Nobody decided this. It accumulated, one post and one internal link at a time.

Every gap needs one of three answers

The mismatch comes in two shapes. Some queries show you that you never intended to own, and some subjects you intended show no queries at all. Each line in either list needs a decision, and there are only three available.

You can close the gap: the intended subject is right, so you write the posts that deepen it, retitle the ones that use your internal vocabulary instead of the buyer's, and link the archive toward the pages that should own the query. You can adopt the drift: the unintended query turns out to be real demand from people who buy, so it goes into the brief and earns a cluster of its own. Or you can concede it: the query is real but the people typing it are not your customers, and you stop feeding it.

Conceding is the answer teams resist, and it is often the right one. A recruitment-flavoured query that brings in job seekers, or a definition query that brings students, will happily absorb a year of posts. We have argued that the weekly readers of a B2B blog are rarely the buyer. A query list sorted by volume will pull the archive toward whoever searches most, and that is seldom who signs.

What the report cannot tell you

The report is a lower bound, and a skewed one. Google's own deep dive into performance data explains that anonymized queries, those not issued by more than a few dozen users over a two-to-three month period, are left out of the tables entirely. They count toward the chart totals but never appear as rows. In a narrow B2B market, that is where many of the questions that precede a purchase live.

So the query list overrepresents the common phrasing and underrepresents the specific one. It cannot replace the sales calls we recommended as the source of a young archive's first fifty subjects; it can only show you which of those subjects Google has connected to you so far. The report also notes that results are specific to the time, place, device and history of the person searching, so a query appearing in your list does not mean you will see yourself when you type it.

It is also slow. In the first quarter of a new archive the list is mostly noise, which is one more reason a flat first ninety days is the expected outcome rather than a warning. The comparison starts paying once the archive has a few months of history behind it.

An engine can read the gap. It should not settle it.

Comparing a brief with a query list is mechanical work, and it suits a machine. Ours can cluster the queries by the page they land on, set them against the subjects the brief named, and flag the drift each month without anyone opening a spreadsheet.

What it should not do is act on that list by itself. A model told to chase every query it is shown for will write about everything, and Google's people-first guidance names that pattern among its warning signs: using extensive automation to produce content on many topics, in the hope that some of it performs. That is the failure we described in the cornerstone on AI content, and an automated blog is exactly the machine that can commit it at scale. Whether a query belongs to your customers is a commercial judgment, so the gap goes back to the approver as a question, not forward to the writer as a task.

Read the query list as a review of the brief

If you accept this, the quarterly content meeting changes its subject. The question stops being how much traffic the blog brought in and becomes whether the archive is about what the brief says it is. Each gap gets one of the three answers in writing, and the brief is amended to match.

That makes Search Console the market's running review of your positioning, delivered free and in the buyer's own words. Most teams open it to check a number. The more useful reading is the list underneath.