--- name: google-search-console-weekly-keyword-report description: "Every Monday: clicks, impressions and position for your top queries, what moved since last week, and the pages to work on first. Use when the user asks for this, or when it runs on a schedule." --- # Search Console weekly keyword report Every Monday: clicks, impressions and position for your top queries, what moved since last week, and the pages to work on first. For anyone who owns a site's organic traffic and opens Search Console every Monday to see what moved. The agent pulls the last 7 days of query data, lines it up against the 7 days before, and writes down only what changed: the queries that gained or lost clicks, the ones whose position slipped, and the new ones. You stop scrolling the Performance report and start the week with five lines you can act on. ## Two ways to get the data Use the API or MCP route when you have an MCP server, a CLI or an API token for the app. Otherwise, if you can drive a browser the user is signed in to (Claude in Chrome, a Playwright or Chrome DevTools MCP server), use the browser route. Say which one you used. ## Route A: API or MCP server ### What you need - Read access to the Search Console property (`sc-domain:example.com` or a URL-prefix property). - A way for the agent to call the Search Console API: a Search Console MCP server, or a service account added as a user on the property with `GOOGLE_APPLICATION_CREDENTIALS` set. If something is missing, say what and stop; do not invent numbers. ### Steps 1. **Pull this week's queries** (Google Search Console): Call `searchanalytics.query` for the property with `dimensions: ["query"]`, the last 7 full days (Search Console lags about 2 days) and `rowLimit: 250`. Keep clicks, impressions, CTR and position. 2. **Pull the week before** (Google Search Console): Run the same query for the 7 days before that, so every query has a this-week and a last-week row. 3. **Find what moved**: Join the two weeks on the query. Flag gains and drops in clicks of 20% or more (with at least 10 clicks), position changes of 2 or more places, and queries that are new this week with at least 50 impressions. 4. **Write the report**: Total clicks and the change, then up to 5 winners, 5 losers and 5 new queries, each with clicks, position and the page that ranks for it. ## Route B: the browser ### What you need - Signed in to Google in this browser with an account that has at least Restricted access to the Search Console property. If something is missing, say what and stop; do not invent numbers. ### Steps Start at https://search.google.com/search-console/performance/search-analytics. The user is signed in already; never type passwords or codes, and ask if a sign-in page appears. 1. **Open the Performance report**: The URL opens the property picker when the account has several properties; choose the site, then Performance > Search results. Leave Search type on `Web`. 2. **Compare the two weeks**: Click the Date filter, open the Compare tab, choose `Compare last 7 days week over week` and click Apply. Turn on all four tiles above the chart (Total clicks, Total impressions, Average CTR, Average position) so the table shows them for both periods with a Difference column. 3. **Read winners, losers and newcomers**: On the Queries tab, sort by the Clicks difference for the gains, then the other way for the drops. Keep gains and drops of 20% or more with at least 10 clicks, position changes of 2 or more, and rows with no clicks or impressions in the earlier week and at least 50 impressions now. 4. **Find the ranking page**: For each query you keep, click its row (this adds a Query filter), switch to the Pages tab and note the first page, then remove the filter with the x. Up to 15 queries is a few minutes of clicking. 5. **Export when the table is full**: The table and its exports stop at 1,000 rows per tab. For a site with more queries, use Export > Download CSV, keep the same thresholds and finish the comparison in a spreadsheet. Note: The UI caps each table and export at 1,000 rows, so large sites get their top queries only; the API returns up to 25,000 rows per call. Both routes carry the same 2-day data lag. The comparison is the same one the report draws, so for a quick look the browser route is the faster one. ## The report - **Clicks this week** and the change against last week. - **Winners**: up to 5 queries with the biggest gains in clicks. - **Losers**: up to 5 queries that dropped, with their old and new position. - **New queries** that started showing up this week. - One line on what to do first, for example "Refresh /pricing: it lost 3 positions for 'invoice software'". ## Post it to Briefkin When `BRIEFKIN_TOKEN` is set, or `~/.config/briefkin/env` exists (the installer from https://briefkin.dev/docs writes it), also send the result to the user's Briefkin board as one card. Keep the `item_key` the same on every run so the card updates in place, use a new `event_id` per run, and put today's real numbers in place of the example ones. If the request fails, say so once and carry on. ```bash [ -n "${BRIEFKIN_TOKEN:-}" ] || . ~/.config/briefkin/env curl -sS -X POST "${BRIEFKIN_URL:-https://briefkin.dev}/v1/events" \ -H "authorization: Bearer $BRIEFKIN_TOKEN" \ -H "content-type: application/json" \ -d @- <<'JSON' { "v": 1, "event_id": "google-search-console-weekly-keyword-report/", "item_key": "google-search-console-weekly-keyword-report", "project": "example.com", "source": "Search Console weekly keyword report skill", "kind": "metric", "title": "Organic clicks this week", "metric": { "label": "Organic clicks", "value": 4812, "better": "higher", "period_start": "", "period_end": "" }, "glance": [ { "type": "Grid", "props": { "columns": 3 }, "children": [ { "type": "Stat", "props": { "label": "Impressions", "value": "182k", "delta": 9 } }, { "type": "Stat", "props": { "label": "Avg position", "value": 11.4, "delta": -6, "better": "lower" } }, { "type": "Stat", "props": { "label": "CTR", "value": 2.6, "unit": "%", "delta": 4 } } ] }, { "type": "Badges", "props": { "items": [ { "label": "↑ invoice template", "tone": "ok" }, { "label": "↑ free invoice maker", "tone": "ok" }, { "label": "↓ invoice software", "tone": "bad" } ] } } ], "widget": [ { "type": "Table", "props": { "columns": [ "Query", "Clicks", "Change", "Position" ], "align": [ "left", "right", "right", "right" ], "rows": [ [ "invoice template", 1204, "+18%", 3.1 ], [ "free invoice maker", 860, "+31%", 4.6 ], [ "invoice generator", 512, "+4%", 6.2 ], [ "invoice software", 288, "-22%", 9.8 ], [ "receipt template", 141, "new", 12.4 ] ] } }, { "type": "Callout", "props": { "text": "Refresh /pricing: it slipped from 6.4 to 9.8 for \"invoice software\".", "tone": "warn" } } ], "size": "md" } JSON ``` Widgets come from the Briefkin catalog (https://briefkin.dev/v1/catalog). Without a token, just give the user the report. Set `period_start` and `period_end` to the window the number covers: the tile names it from them ("Last 7 days", "Today", "This month"). For a count right now (open items, a balance), send `"period_label": ""` so no period shows; for another name, send it as `period_label` (at most 24 characters). ## Run it on a schedule Suggested: Mondays at 9:00 (`0 9 * * 1`). From cron, with the agent signed in on that machine: ```bash 0 9 * * 1 claude -p "Run the google-search-console-weekly-keyword-report skill" # Codex: codex exec, Gemini CLI: gemini -p, Copilot CLI: copilot -p, OpenCode: opencode run ``` Or use the agent's own scheduler (Claude Code routines, Codex automations, Claude or ChatGPT scheduled tasks): https://briefkin.dev/skills/google-search-console-weekly-keyword-report#schedule Source: https://briefkin.dev/skills/google-search-console-weekly-keyword-report