Google Search Console integration that turns queries into your next moves

LogNorm reads Search Console's performance data broken down by date, query and page: clicks, impressions, click-through rate and average position for each combination. These are the same four metrics Google's Performance report shows.

LogNorm only takes Google's finalised numbers, so the latest day is about two days old. Google also leaves some queries out of its reports to protect user privacy (it calls them anonymized queries), so totals by query never add up exactly to totals by page. That is how Search Console works, not a sync problem.

After every sync, LogNorm reads the last 28 days (and the 28 before, for decay) and creates or updates moves in your backlog. Each move carries the Search Console rows behind it as evidence, so you can see exactly which queries and pages triggered it.

Every move comes with an expected impact, such as "+340 clicks per 28 days at position 3", worked out from impressions and a typical click-through curve. Moves are then ranked against audit fixes, keyword gaps and competitor work in your weekly Growth Plan. Searches for your own brand are left out of orphan and cannibalisation moves, judged from the brand terms in your Company Brain.

When a move ships, LogNorm records a 28-day baseline from Search Console and measures again at 28 and 90 days. It compares like with like: the last 28 days of each window against the baseline.

• A move wins when clicks or impressions rise 20% or more, when a new page goes from zero to at least 10 clicks or 100 impressions, or when average position improves by 3 places or more.
• A move with a target page is measured on that page, counting the http, https, www and trailing-slash spellings Google might use.
• A move that has not won at 28 days gets a second chance at 90 days, and each measurement is logged with its numbers and the reason.

Without Search Console, a move can't be marked won, because wins are decided on clicks, impressions and position. See Results and measurement for the full rules.

It also feeds rank tracking and keyword research. After each sync, LogNorm records a daily position for every targeted keyword from the last 90 days: the impression-weighted average position for that exact query, plus the page that earned the most impressions.

Queries with at least 10 impressions in the last 90 days become keyword candidates, checked against search volume and difficulty before they are suggested. A weekly Google check covers targeted keywords that have no impressions yet. See Keywords.

A workspace owner or admin clicks Connect Search Console, signs in with Google and grants the read-only permission. LogNorm picks the matching property and starts the first sync straight away.

1. 1
   Pick the website

   Each website in a workspace connects on its own, so switch to the right site first.

2. 2
   Click Connect Search Console

   From the last onboarding step, Search › Performance, or Settings › Integrations.

3. 3
   Grant the permission

   Sign in with a Google account that can see the property and tick the Search Console permission. LogNorm asks for the read-only webmasters.readonly scope.

4. 4
   Confirm the property

   LogNorm prefers a domain property, then an https URL-prefix property. If none matches, you pick the property that covers the site.

LogNorm never writes to your Search Console account, and the tokens are encrypted per workspace. Disconnecting keeps the data already synced, so charts and move evidence keep working. The Search Console docs cover reconnecting and troubleshooting.

Yes, through LogNorm. A coding agent such as Claude Code or Codex connected over MCP reads the same Search Console data as your team, limited to the one website it joined, and never sees your Google tokens.

When it writes a brief, LogNorm's research step pulls in your Search Console queries next to Google results and keyword data. When it works a striking-distance move, it reads the evidence rows and updates the page in your repo. Read more in Google Search Console MCP and Agents and MCP.