Automate a weekly SEO report with AI

1. Reads your notes. list_notes returns anything you or a previous run saved for this property: a launch date, a redirect change, the queries that count as brand. A drop the week after a known migration reads very differently from a drop out of nowhere. Notes do not count as data pulls.
2. Pulls the headline. search_analytics with no dimension and the compare option returns the property totals for the last 7 days next to the 7 days before. One data pull.
3. Pulls pages. The same call by page shows which URLs gained or lost clicks and impressions, and where average position moved. A page whose impressions fall off a cliff is the clearest technical warning sign the performance data gives you. One data pull.
4. Pulls queries. The same call by query lists the searches behind the change, including queries that are new this week. One data pull.
5. Draws the chart. search_chart returns the daily series for 28 days. In Claude it renders as an interactive chart in the conversation; elsewhere it comes back as a compact daily table. It answers the question a week-on-week number cannot: is this a trend or one odd day? One data pull.
6. Writes and remembers. The agent writes the five bullets and calls add_note with the week's numbers, so next week it can compare against what it said, not only against Google's previous period.

Four data pulls a week is about 17 a month, which fits inside the free plan's 40 with room left for questions during the week.

Putting it on a schedule

The prompt is written to run unattended: it needs no follow-up questions and ends with a clear verdict. If your AI client can run prompts on a schedule, paste it there. If not, an always-on agent or a workflow tool can run it for you, and we have step-by-step guides for three setups:

• Scheduled tasks in Claude Code and ChatGPT, including what each can and cannot do unattended.
• An autonomous SEO agent built in n8n, which wakes on a timer, runs the analysis and logs the result.
• OpenClaw and Hermes agents, which run on your own machine and message you the report in your chat app.
• Grok Bot routines, which run in xAI's cloud after you close your laptop.

Whatever runs it, the account behind the connection stays read-only by default, so a scheduled agent can read your data but cannot change your Search Console settings.

A real run on mcpsearchconsole.com on 2 October 2026. Search Console reported the window as 23 to 30 September 2026, compared with 15 to 22 September 2026. This is a young site with small numbers, which makes it a good test of whether the agent can tell noise from news.

The agent's verdict: No action. Clicks halved, but from 15 to 8, which is within normal weekly swing at this volume, and average position improved. One item to check: /blog fell from position 6.2 to 72.8, so inspect it next week if it does not recover. No notes existed for the property, so the agent saved the week's numbers as the first one.

A weekly report is only useful if it ends in a decision. These are the rules the prompt applies, and you can tune the thresholds to your traffic:

• Clicks down, impressions steady, position steady. A CTR problem, often a new SERP feature or a rival's better title. Look at the losing queries and rewrite the title and description of the page behind them. See the low-CTR use case for the method.
• Clicks and impressions down together, position steady. Demand fell: seasonality, a news cycle ending. Check the 28-day chart and last year if you have it. Usually no action.
• Position worse by 10 or more on one page. Treat it as a possible technical problem. Inspect the URL (index state, canonical, robots) before touching the content.
• A page drops to near zero impressions. Act the same day. Something removed it: a noindex, a redirect, a broken deploy. Inspect it and check its redirects.
• A whole site drop across many pages. Read your notes first (deploy, migration). Then check robots.txt and the sitemap. If nothing changed on your side, wait a week and compare with known Google updates.
• New queries ranking in the top 10. Opportunity. If the page only mentions the topic in passing, give it a section, or plan a dedicated page.
• Small sites, small numbers. Below about 50 clicks a week, ignore swings under half. Look at the four-week trend instead.

Whatever you decide, have the agent save it with add_note. In four weeks, the question "did that title change work?" has an answer.

• Data trails by about two days. A report on Monday covers the week up to Friday or Saturday. Do not read the last day of the chart as a drop; it is often still filling in.
• Search Console sees search, not your business. It cannot tell you about conversions, revenue or traffic from other channels. Pair the report with your analytics tool if those matter.
• Small numbers are noisy. At a few dozen clicks a week, a single visitor moves CTR by points. The report's verdict should lean on trends, not one week.
• Rare queries are hidden. Google leaves out anonymised queries, so query rows will not add up to the total.
• It does not see rivals. A loss can be a competitor's new page. Search Console only shows your side.
• Average position is an average. A page that starts showing for many deep queries can look worse while gaining clicks. Read position next to impressions.