What does Kwern ask Google for?

The read-only Search Console scope. Kwern can read search analytics and nothing else: submitting a sitemap, adding a property or deleting one all come back refused.

Every agent of the product can read a connector's data, but the SEO agent is the one built on this one: its weekly audit reads what the crawl found against what Search Console says, which is the difference between a page that is broken and a page that is simply losing.

What is a ranking drop?

A query that fell three places or more since the window before it, with what it used to rank and what it lost. That is the list an audit starts from.

Which numbers does it keep?

Clicks, impressions, CTR and average position, day by day. A total over a range sums the clicks and the impressions and takes CTR and position as the mean of the days weighted by impressions, which is the only honest way to average a rate.

Is this the same connection as Google Analytics?

One grant, two connectors. Removing the Google account removes both; unbinding the GA4 property leaves Search Console reading.

Google Search Console

Search Console is the only place that tells you what people typed before they did not click. Kwern reads it so the SEO agent can argue about a page from the queries it already ranks for.

What Kwern reads

Search performance, day by day

Clicks, impressions, CTR and average position for the site, day by day.

Queries and pages

The queries and the pages behind them, head first.

The queries that fell

The queries that fell three places or more since the window before.

Kept day by day

clicks, impressions, CTR, average position. Every day ever seen is kept and never windowed, so a range you ask for a year from now still answers.

What Kwern can change

Nothing

Nothing. The grant Kwern holds reads and cannot write, so there is no proposal that ends here.

How the connection is made

Connecting the account

One Google authorization covers Search Console and Analytics together. Kwern asks for the read-only scope of each and keeps the refresh token so the grant survives the hour.

Binding it to a product

A Search Console site. The same Google account can also bind a GA4 property, as its own connector.

What Kwern never does

Never a write

Kwern never submits a sitemap, adds a property or deletes one. The scope it holds is read-only and Google refuses the rest.

The head, not the tail

Twenty-five rows of queries and twenty-five of pages per window: an audit reads the head of the distribution, not the whole tail.

Questions

The agents that use it

Every agent of the product reads what this connector syncs. These are the ones that work on the same surface:

SEO Agent

Crawls the site every week and turns what it finds into pull requests on the repository that serves it.

GEO Agent

Probes the engines that answer questions and fixes what keeps your pages out of their answers.

Competitors Agent

Re-reads your competitors' public pages every week and writes one digest of what substantively changed.

Writer Agent

Writes the day's article from a roadmap Kwern keeps for your site, with the front matter done; you publish it.

The other connectors

App Store Connect Apple Ads Google Play RevenueCat Stripe PostHog Google Analytics 4 Google Ads X Reddit LinkedIn GitHub

Read on

Connecting Google Search Console, step by step

What to click, what each sync leaves behind, and what to do when the connection breaks.

The MCP server

Read the last sync of every connector, and approve what waits, from your own MCP client.

Someone is asking for what you built today.

On Reddit, on X, in ChatGPT's answers. Kwern finds them every morning and drafts the reply in your voice; you decide what goes out.