Daily SEO loop: AI agents read Search Console and prepare your drafts

Organic search is a job of regularity. The data is available every day in Search Console, but reading it, cross-checking it and turning it into a list of actions takes time, so it gets opened once a month, when someone thinks of it. Meanwhile, a query ranked eleventh waits for a small push, a much-viewed page keeps a title that does not make people want to click, and a question that people ask still has no page. These are reading and method tasks, with known criteria, and they suit AI agents as long as publishing stays in human hands.

The inspiration: a loop that runs every day

The starting point is a use reported by Hermes Agent users, summarized in a card about the daily SEO loop: read Search Console, draw opportunities from it, prepare the content. The idea is to turn an irregular chore into a rhythm: every morning an up-to-date list, and drafts for what deserves to be written.

We keep the loop and remove automatic publishing, which would mean connecting a CMS and letting an agent write online. Atako applies the idea with two agents whose work stops at the wiki: the decision to publish stays yours.

What the two agents do

The scenario deploys two agents. The first is connected to your Search Console, the second works from the project wiki.

The SEO analyst reads every day at 7:30 the performance of the last twenty-eight days, by query and by page, with clicks, impressions, click-through rate and average position, and compares it with the previous period. It keeps only what matches your topic. It spots four types of opportunities: queries ranked eighth to twentieth, which have real impressions and which a small effort can bring to page one; much-viewed pages whose click-through rate is well below that of their position, whose title and description need rework; queries that appear without a dedicated page, hence a new article to write; pages that dropped, to refresh. It writes the result in the wiki page "SEO opportunities": at most fifteen rows, with the figures, a one-sentence recommendation and a status "To validate".

The SEO writer runs every day at 10:00. For each row you have validated, it writes a draft in a new wiki page: the target query, the search intent, a proposed title and meta description, the structure, the text, suggested internal links and the sources. For a click-through rate problem, it proposes three titles and descriptions; for a refresh, the list of changes and the rewritten passages. It writes in the language you gave, or in that of the query, and says in the chat when the draft is ready.

What the agents do not do

The limits are part of the design. Neither agent publishes anything: the scenario connects no CMS, and the agents have no way to write on your site. The analyst is read-only on Search Console: it changes neither the sitemaps, nor the settings, nor the properties. Neither contacts anyone.

The analyst never sets a row to "Validated": only the human does, and the writer does not write on a row that is not validated. The agents do not guess. Figures are given as Search Console returns them, with the period, and the analyst says when the volume is too low to conclude or when the data lags by a few days. The writer invents no fact, figure or quote, cites the sources it opened and marks "to verify" what it is unsure of. This split is the principle of a design with human validation.

How to set it up in Atako

From the page of this use case, deployment takes four steps.

1. Connect Search Console. Give read access to a service account or a dedicated account, added as a user of the property. The connection is checked before anything is created.
2. Enter your context. Give the property as it appears in Search Console, for example sc-domain:example.com, the topic and audience of the site, and if needed the language of the drafts. The agents use them to keep only relevant queries and to write in your voice.
3. Deploy. A single action creates the two agents and the "Daily SEO" project. The agents are provisioned and receive their first instructions on their own.
4. First result, then a daily rhythm. The analyst writes the first "SEO opportunities" page and summarizes its three best rows in the chat. The writer explains how to validate an opportunity. Then the analyst schedules its own 7:30 run and the writer its 10:00 run.

If you do not have an account yet, creating one starts your trial and the scenario is set up right after. If your administrator has not allowed you to create agents, the deployment tells you so and stops there.

Where to see the results

The list of opportunities is read in the wiki of the "Daily SEO" project, page "SEO opportunities", and the drafts in the "Draft: ..." pages of the same wiki. Each agent's daily summary is read in its chat. On the Atako floor, the two agents appear with their current activity.

To validate an opportunity, set its status to "Validated" in the page, or write it to one of the agents. The draft arrives at the writer's next run.

Guardrails

The access is deliberately narrow. The Search Console connection is granted read-only with five tools: properties, performance, sitemaps and URL inspection. An agent that sees a short list of tools uses them more reliably than an agent lost in a catalog of hundreds, and above all, what is not granted cannot happen. The writer has no integration access at all: it reads the wiki and the public web, and writes in the wiki.

The account you connect is your first guardrail: limited to reading one property, it bounds the possible damage. The access is stored encrypted, and you can remove it at any time.

Human validation sits at the decision points. You choose the opportunities worth pursuing, you review and edit each draft, and you publish it yourself.

What to expect

Expect useful lists mostly if your site already has some traffic: on a recent property with few impressions, the analyst will say so rather than manufacture opportunities. Search Console data lags by a few days, and rare queries are sometimes anonymized there. The drafts are a solid starting point, not a text to publish as is: they need your eye on tone, facts and internal links. The value comes from regularity: every morning an up-to-date list, and every opportunity you keep arrives with a draft to review rather than a blank page.