SEO and GEO agent
An agent that reads your Google Search Console numbers each week, asks a small panel of AI prompts whether they cite your sites, and proposes the few findings that matter.
Last verified 2026-10-07
In the web app
What the SEO and GEO agent does
The SEO and GEO agent works for one of your roles: every Monday at 06:30 Zurich time it reads your Search Console numbers, asks a small panel of AI prompts whether the answers cite your sites, and proposes at most 5 findings on your approvals desk.
Like every agent it only prepares: it never publishes or changes a site, and nothing is created until you approve.
Allow Search Console
Search Console is asked for only when you want it, per Google account: under Settings, Accounts, choose Allow Search Console at the account. Google then asks you for read-only access to your Search Console data, and nothing changes for the accounts you leave as they are.
Remove Search Console stops zonask from reading it for that account and pauses the account's SEO and GEO agents; you get a notice once. Google can only take back all of zonask's access at once, so zonask does not revoke anything there; to remove zonask's access completely, disconnect the account or remove zonask in your Google account's security settings.
Set up the agent
Under Agents, open Add SEO and GEO agent at the role and fill in the setup.
- Google account: an account where you allowed Search Console.
- Search Console properties: Show properties lists the properties the account can see, such as sc-domain:capptoo.ch; pick 1 or 2. More properties need a second agent in another role.
- Your domains: up to 5 of your own domains, such as capptoo.ch; the panel counts a prompt as cited when an answer cites one of them or a property's domain.
- Prompts: up to 10 questions people might ask an AI assistant, such as which agency in Zurich builds Drupal websites, each in German, French, Italian or English.
Save setup says "SEO and GEO agent saved."; Change setup changes it later.
What is read, and what is not kept
For each property zonask reads, read only, the clicks, impressions, click-through rate and average position of the last 7 complete days against the 4 weeks before, the top 25 queries and pages, and the sitemaps with their errors and warnings.
Search Console's numbers lag about 2 days, so the week ends 3 days before the run.
These numbers are read when the agent runs or when you open the report, and are never stored.
When Search Console does not answer, the report says "Search Console did not answer. zonask tries again next Monday."
The prompt panel
Search Console has no numbers for AI answers, so the agent asks your prompts itself: each prompt goes once a week to an AI model that searches the web, and zonask keeps only the domains the answer cited and whether one of yours was among them. The answer's text is dropped.
Each prompt is one web search and counts towards the agent's monthly budget like every model call.
Findings on the desk
Each finding waits on your approvals desk as one proposal, for example capptoo.ch: clicks for "drupal agentur zürich" down 42 % (31 to 18). Create a task to review the page? It comes with the numbers it rests on.
A finding is a drop, an opportunity, a sitemap error or a gap in the AI answers, such as a prompt panel where your domains are cited for 3 of 10 prompts while other sites are cited for the rest.
Approve adds the task in the agent's role; Reject drops the finding. A week without anything worth your time says "No findings this week."
The report
Search report at the agent shows each property's clicks, impressions, click-through rate and position with the change against the 4 weeks before, such as "1'240 clicks, minus 8 %", the top 5 rising and falling queries and pages, sitemap issues, the panel, such as "Cited in 3 of 10 prompts", and the findings of the last run.
On Monday the morning plan email has a section "Search this week" with one line per property.
What is kept for 30 days
The findings (their sentence, numbers and suggested task) are encrypted and deleted after 30 days, also when you approved them; a rejected finding is deleted at once. Of the panel only whether each prompt was cited is kept.
In Claude or ChatGPT
Ask, for example, how capptoo.ch did in search this week: get_seo_report answers with each property's numbers, the panel and the findings, and a short summary such as "capptoo.ch last 7 days: 1'240 clicks (minus 8 %), position 14.2; cited in 3 of 10 AI prompts".
create_agent adds a role's SEO and GEO agent with its setup and update_agent changes it; both show the setup first and save it only after your confirm.
The findings wait in list_approvals, and answer_approval approves or rejects them. Allowing or removing Search Console happens only in the browser.