Traffic dropped. Here's the edit that probably caused it.
One alert watches clicks on the pages you care about. When they fall, it shows you the page edits detected in the same window — so you start the investigation with a suspect instead of a blank page.
A quiet inbox is not the same as "nothing happened"
Most traffic losses are found late — someone opens Search Console for an unrelated reason and notices a line that has been sliding for three weeks. By then the trail is cold: you are reconstructing what changed from memory, deploy notes, and whoever happens to be online.
The usual fix makes it worse. A threshold alert that re-sends every time it runs is still true tomorrow, and the day after, so it becomes noise you filter to a folder — and the one that actually mattered gets filtered with it.
This workflow does two things differently. It pairs the drop with the page edits Page Pulse detected in the same window, so the likely cause arrives with the symptom. And it notifies once when the drop starts, stays quiet while it continues, then tells you when it recovers — so the alert keeps meaning something.
Set it up
Five fields in the alert builder. The condition defaults are already the ones you want.
Open the alert builder
In Page Pulse, open the project you want to watch, go to Alerts, and choose New alert.
Trigger: Metric drop
Pick "Metric drop" — Clicks, impressions, users, or events fall below a threshold. This one reads Search Console data, so it is unavailable on crawl-only projects; connect Google first if it is greyed out.
Condition: leave the defaults
The form opens on Clicks · drops by more than · 20% · over the last 30 days — which is exactly this workflow. Raise the percentage if the pages are spiky, or shorten the window to 7 or 14 days to react faster.
Scope: the pages worth waking up for
Set Scope to Specific URL(s) and paste your money pages, or Tagged pages if you have already tagged a section. Leaving it on All pages is the fastest way to make this alert noisy.
Page changes: Include in alert
This is the step that makes it a Page Pulse alert instead of a generic threshold email. Set page changes to "Include in alert" — it shows the recent page edits alongside the metric data, so the drop and its likely cause arrive together.
Delivery, then save
Add email recipients (up to 20) and/or a Slack channel — at least one is required. Turn on the recovery notice so you also hear when it clears, then save.
What you need
- Search Console connected (this trigger reads clicks)
- Google Analytics 4 for users and key events
- At least one delivery channel — email or Slack
- Crawl-only projects cannot use this trigger
When it actually fires
- Once, when the drop begins — not every run
- Silent while the drop continues
- A recovery notice when it clears, if enabled
- Evaluated at most once a day
Be realistic about timing
- Search Console data lags 2–3 days
- So a drop surfaces a few days after it starts
- Change detection runs at crawl speed — daily on paid plans
- This is early warning, not real time
Stop finding traffic drops three weeks late
Page Pulse watches your pages, logs every change, and puts the edit next to the outcome. Free for up to 50 pages.
No credit card required · Free plan available
Related workflows
Compare GSC & GA4 performance before and after any page change
Stop guessing whether that rewrite worked. Record automatic, daily, page-level changes, then pull a clean before/after comparison of…
View workflow
Find which landing pages bring in the most key events from GA4
GA4 shows you key events, but not which landing page caused them. This workflow surfaces the exact pages…
View workflow
Find which landing pages drive your most valuable conversions
Not all landing pages are equal. Some drive clicks that convert while others drive clicks that bounce. This…
View workflow