Weekly
Get alerted when a page loses clicks
You hear about pages whose search clicks fell sharply, so you can look into them early.
- Runs
- Weekly
- Apps
- Google Search Console
- AI
- Not needed
- Access
- read
Send this to your assistant
Create a ClickRuntime automation: every Tuesday, compare each page's Search Console clicks on example.com with the previous week and email me any page with at least 50 clicks before that dropped more than 40%.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
An e-commerce owner has a category page that brings in 40 percent of her organic traffic. After a template change a developer accidentally added a noindex tag to it. Rankings slide for a week, clicks halve, and nobody notices until the monthly report shows the damage. By then the lost sales cannot be recovered, and finding the cause means digging through weeks of changes.
Every week, ClickRuntime pulls clicks per page from Google Search Console for two ranges, the latest week and the one before it, and compares them. Pages that lost a large share of their clicks, and had enough traffic for the drop to be meaningful, are listed in an email with the old figure, the new figure and the change.
It is a safety net for site owners, SEO consultants and content teams.
What you get out of it
Traffic loss caught in days, not months
A weekly comparison highlights a falling page while the cause, like a recent deploy or a changed title, is still easy to trace. The sooner you look, the less revenue disappears while the problem sits.
Technical mistakes found quickly
A stray noindex tag, a broken redirect or a canonical pointing the wrong way all show up as a sudden drop in clicks. The alert tells you where to look even if you do not yet know the reason.
Focus on pages that matter
Setting a minimum click count avoids noise from pages that went from three clicks to two. The list contains only losses that move the numbers, which saves time spent chasing statistical wobble.
Evidence for client conversations
Agencies can show a client exactly which page fell, by how much and when. A dated email is more convincing than a general statement that traffic seems lower this month.
Time to react to algorithm updates
When many pages drop at once, the pattern points to a search update. Seeing it within a week lets you review content and respond quickly, instead of learning about it from a competitor.
How it works
What happens, step by step
Once a week, ClickRuntime pulls search clicks for each page from Google Search Console, for this week and the week before.
It keeps the pages whose clicks fell sharply.
You get an email listing each page with its old and new clicks, like "312 → 141 clicks (-55%)", so you can look into them early.
Before it runs live
- Connect Google Search Console
What you get
Build your own
Need it to work differently?
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
from datetime import date, timedelta
from urllib.parse import quote
from clickruntime import on_trigger, credentials, http, notify
SITE = "sc-domain:example.com"
def clicks_by_page(headers, start, end):
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": ["page"], "rowLimit": 5000})
resp.raise_for_status()
return {r["keys"][0]: r["clicks"] for r in resp.json().get("rows", [])}
@on_trigger
def run(event):
headers = {"Authorization": f"Bearer {credentials.connection('google', 'work')}"}
end = date.today() - timedelta(days=3) # Search Console data lags a couple of days
now = clicks_by_page(headers, end - timedelta(days=6), end)
before = clicks_by_page(headers, end - timedelta(days=13), end - timedelta(days=7))
drops = [(p, c, now.get(p, 0)) for p, c in before.items() if c >= 50 and now.get(p, 0) < c * 0.6]
if drops:
lines = [f"{p}: {c:.0f} → {n:.0f} clicks ({(n - c) / c:.0%})" for p, c, n in sorted(drops, key=lambda d: d[2] / d[1])]
notify.email_me(f"{len(drops)} pages lost over 40% of clicks", "\n".join(lines))
return {"dropped": len(drops)}FAQ
Common questions
How big does a drop have to be to appear?
Why compare weeks instead of days?
Does the connected account need a specific permission?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
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.
See how it worksGet told about sitemap errors
If Search Console reports errors or warnings on your sitemaps, you get an email that day.
See how it worksKnow the moment your website goes down
Your team hears in Slack when the site stops responding or slows down, and again when it's back.
See how it worksKeep exploring
Set up “Get alerted when a page loses clicks” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.