inemaSEO 5 — With Agents: Claude Code and Codex Doing the Repetitive Work|INEMA.CLUB-PRO

Lesson 6 · 16 min

Automatic weekly report and the agent that reads it and proposes

The observer closes the machine: every week, a script gathers non-branded Search Console data, the indexing of the key pages, and the position of the target queries into one report. An agent reads it and proposes three actions, each with the line that justifies it. You approve what becomes a task.

Start the lesson
A small business owner reads a printed report with simple charts, pen in hand, at a table with coffee.

In this lesson you will

  1. 1What goes into the report and where each number comes from
  2. 2Schedule it without losing control: cron generates, you commit
  3. 3The request to the agent: three proposals, each with evidence
  4. 4Reading a real INEMA week

Goal: generate the non-branded weekly report and ask the agent for 3 proposals with evidence, which you approve before they become tasks.

01From Search Console to the approved task

Tap each block.

Click each block in the diagram to see what it does.

The script measures; the agent suggests; you choose what to do this week.

02How INEMA runs the observer

Tap each step.

1. The script

In INEMA's SEO project, a script runs the non-branded export, inspects the key URLs, reads the positions of the target queries, and writes the report compared with the previous week. With the no-API option, it only rebuilds the report from what is already saved.

The public version of the export is the method's gsc_semanal.py; the report around it fits in a short script that the agent can build for you.

03The export, the schedule, and the request to the agent

gsc_semanal.py needs your Search Console credential (free, see the script header).

Weekly non-branded export (public, inemaSEO method)
export GSC_SITES="sc-domain:yoursite.com"
export GSC_MARCA="yoursite|your name|common typo"
export GSC_QUOTA_PROJ="<your Google Cloud project>"
python3 tools/gsc_semanal.py --dias 7 --saida dados/gsc
Schedule (crontab template: Tuesday at 9 a.m.)
0 9 * * 2 cd ~/projetos/seo-seusite && python3 tools/gsc_semanal.py --dias 7 --saida dados/gsc >> dados/gsc/cron.log 2>&1
Request to the observer agent
Read this week's report (the most recent reports/semana-*.md) and the one from the previous week.
Propose at most 3 actions for this week. For each one:
- the report line that justifies it (copied);
- the type: title/description, new page for a query, indexing, internal link;
- what changes and where;
- how we will know next week whether it worked.
Do not change anything, do not call any API. If the week shows nothing new, say so instead of inventing an action.
Example from the repository
# Relatório semanal de SEO — semana até 2026-10-11

Gerado em 2026-10-13 por `scripts/gsc_relatorio_semanal.py`.

## Totais (cliques / impressões)

| site       | total     | marca    | sem marca | consultas sem marca | vs semana anterior (impr. sem marca) |
| inema.club | 114 / 702 | 87 / 238 | 0 / 157   | 51                  | ▲ +110 |
| inema.pro  | 11 / 761  | 5 / 116  | 2 / 293   | 52                  | ▲ +279 |

## Indexação das URLs-chave (inspeção de 2026-10-13)
| /eventos/ | URL is unknown to Google | - | = |

Indexadas: 13 de 14.

Excerpt from the real report; the query tables were omitted.

04Practice: one week of your site

If you don't have the API credential yet, export the week's queries from the Search Console panel (Performance → Export) and use the CSV.

E1 · The week's report

40 min

Run the non-branded export for the last week (or export from the panel) and ask the agent for a Markdown report with totals, branded, non-branded, and the 15 non-branded queries with the most impressions.

Done when: a file reports/semana-[date].md exists with totals split into branded and non-branded, and the numbers match the Search Console panel.

E2 · Three proposals and your decision

20 min

Give the observer request to the agent. Check each line cited in the report and decide.

Done when: you have up to 3 proposals, each with the line copied from the report and your decision (approved, with the task created, or rejected, with the reason).

05Test what you learned

The explanation appears after your answer.

Question 1 of 4

The cron generates the report every Tuesday. Who makes the commit?skill

06To take with you

One round per weekNon-branded, indexing and target queries, compared with the previous week.
Cron generates, you keepThe schedule produces files; the commit is yours.
Three proposals with evidenceThe agent suggests; each suggestion cites the line; you approve.
2026 yardstickThe number that shows whether SEO is working is non-branded searches.

Going further

gsc_semanal.py in the inemaSEO methodCourse 3: MeasurementinemaSEO systems: Search Console history beyond 16 months
Previous lessonNext lesson