Skip to content

Weekly

Get a weekly search performance report

Every Monday you see clicks, impressions, CTR and position against the week before, with the queries that moved most.

Runs
Weekly
Apps
Google Search Console
AI
Not needed
Access
read (webmasters.readonly)

Send this to your assistant

Create a ClickRuntime automation: every Monday at 8am, email me last week's Search Console clicks, impressions, CTR and average position for example.com compared with the week before, plus the 10 queries that gained or lost the most clicks.

Paste it into your assistant. It tells you what it will send or change before it runs live.

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

The owner of a small consultancy knows her blog should bring in clients, but opening Search Console means picking a date range, clicking through Performance, switching between queries and pages, and exporting to compare with last period. It takes forty minutes, and it is the first thing dropped when a client project gets busy. So months pass with no idea which articles are growing and which have quietly lost their rankings.

Every week, ClickRuntime queries Search Console's search analytics for the last 7 days and the 7 before them, by query and by page. It works out the change in clicks, impressions, CTR and average position, and emails a report with totals plus the biggest gainers and losers.

It is useful for solo operators, small marketing teams and agencies that want a regular snapshot without a reporting tool.

What you get out of it

  • A regular view of what is working

    Seeing which queries and pages gained clicks tells you what to write more about. Repeating what already attracts readers is cheaper than guessing at topics that might. Topic planning gets a factual basis each week.

  • Losing pages are spotted

    Pages that slip in position or clicks are listed with the size of the change. You can refresh an outdated article before the drop becomes a trend that takes months to reverse.

  • CTR shows title problems

    A page with many impressions but a low click-through rate may have a weak title or description. The report puts those pages in front of you, and a rewritten title is an easy win.

  • No exporting or spreadsheets

    The comparison arrives as an email ready to read. The forty minutes of clicking and copying disappear, so the report is actually looked at every week instead of whenever there is time.

  • Numbers to share with clients and bosses

    A consistent weekly format builds a simple record of progress. When someone asks if the SEO work is paying off, you have dated figures instead of an impression. Reports like that also help justify budget for content.

How it works

What happens, step by step

  1. Every Monday, ClickRuntime pulls last week's Google Search Console figures and the same figures for the week before.

  2. It compares clicks, impressions, click-through rate and average position, and works out which search queries moved the most.

  3. You get one email with each figure next to last week's and a list of the biggest gains and losses by query.

Before it runs live

  • Connect Google Search Console

What you get

RunsWeekly
Get a weekly search performance reporttoday, 9:00Succeeded
Email · Search Console weeklyclicks: 4,812.00 (was 4,390.00) ctr: 0.03 (was 0.03) Biggest query changes: +182 northwind hiking boots

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.
  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

  • Run it at a different time, more or less often, or only on weekdays
  • Add an AI step, for example to summarize, sort or draft a reply
  • Add another app, for example also send it to Slack
  • Combine it with other Google Search Console steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.
weekly_seo_report.pyexample
from datetime import date, timedelta
from urllib.parse import quote
from clickruntime import on_trigger, credentials, http, notify

SITE = "sc-domain:example.com"

def query(headers, start, end, dims):
    resp = http.post(f"https://www.googleapis.com/webmasters/v3/sites/{quote(SITE, safe='')}/searchAnalytics/query",
                     headers=headers, json={"startDate": str(start), "endDate": str(end), "dimensions": dims, "rowLimit": 1000})
    resp.raise_for_status()
    return resp.json().get("rows", [])

@on_trigger
def run(event):
    headers = {"Authorization": f"Bearer {credentials.connection('google', 'work')}"}
    end = date.today() - timedelta(days=date.today().weekday() + 1)  # last Sunday
    weeks = [(end - timedelta(days=6), end), (end - timedelta(days=13), end - timedelta(days=7))]
    cur, prev = ((query(headers, s, e, []) or [{}])[0] for s, e in weeks)
    text = "\n".join(f"{k}: {cur.get(k, 0):,.2f} (was {prev.get(k, 0):,.2f})"
                     for k in ("clicks", "impressions", "ctr", "position"))
    q_now = {r["keys"][0]: r["clicks"] for r in query(headers, *weeks[0], ["query"])}
    q_before = {r["keys"][0]: r["clicks"] for r in query(headers, *weeks[1], ["query"])}
    deltas = sorted(((q_now.get(q, 0) - q_before.get(q, 0), q) for q in q_now.keys() | q_before.keys()),
                    key=lambda d: -abs(d[0]))[:10]
    text += "\n\nBiggest query changes:\n" + "\n".join(f"  {d:+.0f}  {q}" for d, q in deltas)
    notify.email_me("Search Console: last week", text)
    return {"clicks": cur.get("clicks", 0)}

FAQ

Common questions

Why does the report cover the previous 7 days and not today?
Search Console data is delayed by a couple of days, so the most recent days are incomplete. The report uses the latest full week it can trust, and compares it with the week before for a fair change calculation.
What is average position and how reliable is it?
Average position is the mean ranking of your page across all searches in which it appeared, so it blends different queries and locations. Use it as a direction indicator, and look at the top queries for a page to understand why it moved. A change of one position matters little.
Can the report cover more than one site?
Yes. Each Search Console property can have its own report, or several can be combined into one email with a section for each. The Google account connected needs access to every property included, and each site is listed separately.
What permissions does it need?
read (webmasters.readonly). Nothing else in your accounts is used.
Does it need AI?
No. It runs without AI, so it doesn't use your plan's AI allowance.
How many runs does it use?
One run each time it runs (weekly). Checks that find nothing to do and stop right away aren't counted.
Can I change how it works?
Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

Set up “Get a weekly search performance report” from your assistant

Copy the prompt above, or connect your assistant first. Free plan, no credit card.