Automation · Operations and reporting
A weekly Search Console report, with the history kept
How an AI agent builds the search report every Monday: queries, pages, indexing and real field speed, all accumulated in a spreadsheet.
How do I get the Search Console report every Monday without building it by hand?
A scheduled task runs early on Mondays: it pulls the queries that drove the most traffic last week with their clicks, impressions and position, the pages receiving them, checks whether what you published got indexed, and measures the real speed of the key pages with field data rather than lab data. Everything accumulates in a spreadsheet, because Search Console only keeps 16 months and a report that does not accumulate lets you compare nothing, and the summary reaches the team by email. The point is not the report. The point is having the series.
What starts it
At a set time
A task on a weekly recurring trigger. It is scheduled early on Monday because Search Console data lags by two or three days: asking on Sunday returns an incomplete week.
A task on a recurring (cron) or date and time trigger. It runs on its own, with nobody logged in.
Who runs it
Met for content analytics
It has no seeded name in the product: it is an internal marketing Met. The task is tedious, repetitive and gets done badly when a rushed person does it on a Monday.
What you need connected
- Google Workspace Productivity
6 steps · 12 tools
The procedure, step by step
Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.
- 1
Pick the right verified property
The site listing returns the verified properties on the account with their permission level. With several properties (the domain, the subdomain, the www and non-www versions), asking the wrong one produces a report that looks perfectly normal and describes a different site.
- 2
Pull the queries and the pages receiving them
Top queries return clicks, impressions, click-through rate and position for the date range. Pages with their queries answer the question that actually helps: which page receives which search. With that you decide whether to write something new or improve what is already ranking on the edge of the first page.
- 3
Check whether the new content got indexed
URL inspection says whether it is indexed, which canonical Google picked and whether there are coverage errors. It is the diagnosis that avoids the circular conversation about publishing and nothing happening: quite often nothing happens because the page is not indexed. The sitemap listing shows when each one was fetched and with what errors, and resubmitting helps after publishing in volume.
- 4
Measure speed with real user data
The PageSpeed audit gives the lab metrics on mobile and desktop, and the user experience history gives up to 25 weeks of real users. Both matter and they are not the same thing: the lab says what can be improved, the field series says whether the improvement was noticed.
- 5
Accumulate the series in a spreadsheet
The tab is created once, and if it already exists it is not duplicated. Each run appends rows at the end without overwriting what came before. That file becomes the memory of the project: reading the range lets you compare against earlier weeks inside the summary itself.
- 6
Send the summary to whoever will read it
The email carries three or four lines about what changed and the link to the sheet, not a table with two hundred rows. A report you have to open and read in full gets read by nobody; one that says what went up, what went down and what needs a look does get read.
Before you start
What you need ready
The Met solves none of these for you. If one is missing, the automation stops there.
-
A Google account with access to Search Console
You authorize it from Meteor with the account that administers the property. It has to hold permission on the site: the property listing shows which one, and at what level.
-
The property verified in Search Console
You verify it in Search Console with any of its methods. Without verification there is no data, and it is prior work the Met cannot do for you.
-
A spreadsheet to accumulate in
A Google Sheets file shared with the connected account. It can be empty: the tab is created by the first run.
The limits
What this automation does NOT solve
Better said here than discovered halfway through the rollout.
-
It does not improve your rankings. It measures and orders; writing better, fixing speed and earning links is still work with judgment behind it.
-
It does not bring Analytics data. Search Console measures search; sessions, conversions and traffic sources are a different tool.
-
It does not force indexing of any page you like. Google's direct indexing interface is limited to specific content types; for the rest you request a crawl and wait.
-
It does not recover data older than 16 months. That is why the series accumulates in a sheet: whatever was not saved in time, Search Console no longer has.
FAQ
Questions about this automation
Because it stores it for 16 months and in its own format. The sheet lets you compare years, cross it with what the team published each week and keep the series past that limit. It is a cheap decision you thank yourself for two years later.
Because Search Console data arrives two or three days late. Asking for the week just closed on a Sunday returns an incomplete week, and comparing an incomplete week against a complete one produces drops that never happened.
Yes. The property listing returns every verified one on the account and the task can walk them, with one tab per site in the same sheet.
Want this automation running on your own data?
We will show it to you with your accounts connected, not with a canned demo.