Every Monday, someone checks the dashboard, copies numbers, and writes a summary. It’s ideal boring work: read-only, every week, and checked in two minutes. Have a website? The dashboard is Search Console, Google’s free tool that shows how people find your website. Don’t have one? Use the sheet for this week’s numbers. You export the data, and the agent reads and writes.
Goal: turn the Search Console export (or your weekly numbers) into a report of up to 250 words with checked numbers.
01 · From dashboard to report
Click each step. You do the first and last.
A number that doesn't match becomes a new rule in the sheet
Click each block in the diagram to see what it does.
The same process works for any dashboard that exports a spreadsheet: sales, scheduling, customer service.
02 · The export, step by step
In Search Console, using your login. Click each step.
1. Performance
Sign in to Search Console with your account, choose the site, and open the Performance report (search results).
It shows clicks, impressions, CTR (clicks divided by impressions), and average position.
2. Period
In the date filter, choose to compare the last 7 days with the previous period.
That way, the table shows both weeks side by side, and the agent doesn’t have to guess the dates.
3. Export
Click Export and choose Google Sheets, Excel, or CSV (a spreadsheet in plain text).
The file has one tab for each dimension (queries, pages, countries…). For the report, you only need queries and pages. Tab names change with your account language.
Watch outWhen the dashboard doesn’t have a value, it shows ~ or -; in the exported spreadsheet, those cases become zero.
4. Hand it
In chat, attach the file to the Project and say "report". If the file is large, paste only the first 50 rows from each tab.
In the terminal, save the file in the agent’s folder and run the command in the block below.
03 · Sample data and prompts
No Search Console? Use the sample data: it’s made up, but formatted like a real export.
Sample data (paste into the Project after the sheet)
report
Use the sheet in this Project. The data is above (or in the attached file).
Before writing the report, show me the total clicks for this week and last week so I can check them.
Variation · weekly numbers sheet (in a new Project, "Weekly numbers")
Role: You are my weekly numbers agent.
About me: [what the business does]; I paste the numbers from each tool every Friday.
When: when I paste the numbers and say "numbers".
Steps: 1) make a table: metric, this week, previous week, change in %; 2) write 3 short bullets: the best news, the biggest concern, a question for the team.
Rules: read only, never change or delete anything; save everything as a draft, I send it; never ask for a password, login screen = stop and call me; never pay, approve, or schedule a payment; copy the numbers exactly; if a number is missing, write "couldn't find", never estimate; if you get stuck, stop and ask.
Delivery: the table and the 3 bullets, nothing else.
First task: run it now with the numbers I’m going to paste.
Terminal (optional) · Codex with the light model
cd my-agents/site-report
# the sheet is in AGENTS.md; the exported spreadsheet is in this folder
codex exec --skip-git-repo-check -m gpt-6-luna -s read-only -o report.md "report: follow AGENTS.md with the spreadsheet in this folder"
Terminal (optional) · Claude Code with the light model
cd my-agents/site-report
# the sheet is in CLAUDE.md; the exported spreadsheet is in this folder
claude -p --model sonnet "report: follow CLAUDE.md with the spreadsheet in this folder" > report.md
Simulation: illustrative example
Total clicks: 199 this week versus 193 last week (up by 6).
Biggest increase: "custom cabinets denver", from 30 to 48.
Biggest drop: "custom kitchen price", from 41 to 22.
Three simple actions, one per line.
These are the totals calculated by hand from the sample data. The agent’s wording may vary; the numbers must not.
The agent doesn’t need to access Search Console: it gets the spreadsheet. That means no password in the conversation, nothing changes in the dashboard, and the only possible mistake is incorrect wording, which you’ll catch when you check it.
Attach the entire 1,000-row spreadsheet in chat: the model may read only part of it. Send the tabs and rows that matter.
Ask for a "complete website analysis to rank better on Google" (known as SEO): that’s work for the top model and for you (lesson 7). The weekly report is routine.
Skip checking in the first few weeks: that’s when you find out the sheet needs another rule.
04 · Check the agent’s report
Run the agent with the sample data and paste its report here. The page looks for the right numbers: the total for both weeks and the biggest drop. If any are missing, the agent got the math wrong or skipped what matters.
report.txt
05 · Practice: your first report
Start with the sample data, then use your own.
E1 · Practice with the sample
10 min
Create a Project called "Website report" using the example sheet from lesson 2 (the website report one), paste in the example data and Monday’s request. Paste the report into the checker.
Done when: the checker responds OK: the report includes 199, 193, and the drop from 41 to 22.
E2 · With your own data
15 min
Export your week from Search Console (or gather your week's numbers) and run the same prompt. No website? Use the weekly numbers sheet.
Done when: you found two numbers from the report in the spreadsheet, and both matched.
E3 · One more rule
5 min
Read the report and note one thing you’d like to change (order, length, one more number). Add a line to the sheet.
Done when: the sheet has a new rule, and the next report already reflects the change.
06 · Test what you learned
The explanation appears after your answer.
Question 1 of 4
On the chat path, who logs in to Search Console?
Correct
In chat, the agent can’t open your dashboard. You log in, export the spreadsheet, and give it to the agent; it reads and writes. Never put a password in the sheet or the conversation.
That's not it
In chat, the agent can’t open your dashboard. You log in, export the spreadsheet, and give it to the agent; it reads and writes. Never put a password in the sheet or the conversation.Review: From dashboard to report
Question 2 of 4
Using the sample data, what’s the total number of clicks this week?
Correct
48 + 22 + 64 + 17 + 12 + 9 + 6 + 21 = 199. The previous week adds up to 193. 64 is just the largest row, not the total.
That's not it
48 + 22 + 64 + 17 + 12 + 9 + 6 + 21 = 199. The previous week adds up to 193. 64 is just the largest row, not the total.Review: Sample data and prompts
Question 3 of 4
The report is well written, but you don’t have time to check it. In the first few weeks, the minimum is:
Correct
A spot check takes two minutes and shows whether the sheet works. Clear writing doesn’t prove the math is right, and having the agent check its own work repeats the same mistake.
That's not it
A spot check takes two minutes and shows whether the sheet works. Clear writing doesn’t prove the math is right, and having the agent check its own work repeats the same mistake.Review: From dashboard to report
Question 4 of 4
One of your weekly numbers doesn’t appear in the spreadsheet you pasted. What does the sheet tell the agent to write?
Correct
An estimate that looks like a real number is the most costly mistake: you make decisions based on it. “Couldn't find” shows the gap, and you fill it in.
That's not it
An estimate that looks like a real number is the most costly mistake: you make decisions based on it. “Couldn't find” shows the gap, and you fill it in.Review: Sample data and prompts
Test complete
You got {a} out of {n} right. Get them all right to mark the lesson as complete.
Choose an option. The explanation appears after you try.
07 · The lesson in three sentences
You exportThe login and dashboard clicks are yours. The agent receives the spreadsheet and only reads it.
Fixed formatTotal, biggest increases and drops with the numbers side by side, three actions. The same every Monday.
Two numbersCheck two numbers in the spreadsheet. If they match, trust it; if they don’t, add a rule to the sheet.