Search
Google Search Console
Queries, impressions, positions and index coverage, per property.
Feature
The monthly deck, written · Runs in Claude Code
Turn a month of Search Console and Analytics into the report a client actually reads: what moved, why, and what happens next. It renders to a branded document, a slide deck or a CSV, and goes out by email over your own SMTP, so the reporting hour at the end of every month stops being an hour.
§ Scope
§ Limits
Stated plainly, so you do not find out later
The commentary is generated from your numbers, and a number with a plausible explanation attached is still a number that needs an owner. These are drafts for you to sign, not statements to forward unread.
§ Skills
6 of them
Each one is a single command against real data. They compose: the output of one is the input of the next.
The recurring report an agency sends, generated from live data instead of assembled by hand.
Hand a client something that looks like it came from your agency, not a spreadsheet.
Build the client deck once the numbers are in.
Send the finished report with a summary in the body and the full version attached.
Get the data out for a client deck or your own spreadsheet.
Find out what a site spent on DataForSEO, Firecrawl, Serper and tokens before you invoice for it.
§ Sources
Search
Google Search Console
Queries, impressions, positions and index coverage, per property.
Analytics
Google Analytics 4
Sessions, conversions and referral traffic through the Data and Admin APIs.
Reporting
SMTP
Emails the finished report from your own mail server, not a third party's.
Storage
Google Drive
Delivers reports into a client's Drive folder, mirroring the local tree. Scoped to drive.file, so it only ever sees what it created.
§ Elsewhere