set up olywork — https://olywork.com/llms.txt
Using olywork, show me the queries olywork.com ranked 8 to 20 for in the last 28 days with more than 50 impressions, sorted by impressions, and tell me which ones have the worst CTR.
One OAuth click for the property you own. olywork.com holds the token, not you.
Date ranges, filters and sorting are the agent's job, not yours.
Search Console lags 2 to 3 days; yesterday is preliminary data.
Your own account, so the call is never metered.
Connect once, keep the token server side, and call from any agent.
No SDK, no OAuth dance per vendor, no seats.
Google Search Console answers this job. You connect it once, olywork.com keeps the token server side, and the call is never metered.
olywork call google-search-console.performance --data '{"startDate":"2026-07-01","endDate":"2026-07-21","rowLimit":2}'Every endpoint on this connection is listed on the Google Search Console shelf.
Score a 28-day window that ends 3 days back.
That gap is expected.
The Search Console API returns your site's Google Search performance as data: clicks, impressions, CTR and average position, broken down by query, page, country, device and date. It is the same data as the Performance report, without the UI's row limits, and it is the only first-party source for what people actually searched before they reached you.
No. Search Console runs on your own Google account, so olywork.com relays the call and meters nothing. Only calls on olywork.com's own provider keys are billed.
The Google account that already has access to the property, once, through an OAuth screen. olywork.com stores the token server side; your agent never sees it.
No. The API returns only the properties your connected account can access.
Any client that can reach olywork.com: ChatGPT, Claude, Claude Code, Cursor and the rest of the supported list.