Monitoring & Alerting
Monitoring and alerting systems detect SEO issues before they become critical. A good alerting setup notifies you when something changes significantly, distinguishing signal from noise so you can investigate proactively.
Learning Focus
After this lesson you can set up automated alerts for indexing changes, ranking movements, traffic anomalies, conversion drops, CWV degradation, server errors, and competitor movements.
This lesson covers the seven alert types (leaves 2.8.1–2.8.7): indexing alerts, ranking alerts, traffic anomaly alerts, conversion anomaly alerts, Core Web Vitals alerts, server error alerts, and competitor movement alerts.
Why This Matters
Core Concept
- Proactive alerting prevents minor issues from becoming major problems. A noindex tag added during deployment can take weeks to discover without alerting.
- Manual monitoring does not scale. Automated alerts let you focus on fixes, not data checking.
- Alerting builds trust with stakeholders by demonstrating that the SEO team knows what is happening in real time.
Indexing Alerts
Indexing alerts notify you when the number of indexed pages changes significantly.
What to monitor:
| Alert | Threshold | Response Time |
|---|---|---|
| Indexed page count drops significantly | >10% drop in 24 hours | Immediate investigation |
| Indexed page count does not increase after new content publication | No new pages indexed within 7 days | Weekly check |
| "Crawled - not indexed" count spikes | >20% increase week-over-week | Weekly investigation |
| "Blocked by robots.txt" appears for important pages | Any occurrence on verified pages | Immediate |
| Noindex tag detected on pages that should be indexed | Any occurrence | Immediate |
| Sitemap errors increase | Any new errors | Immediate |
| Index coverage report shows new error types | New error category appears | Investigate within 24 hours |
How to set up indexing alerts:
| Method | Setup | Best For |
|---|---|---|
| GSC email notifications | Enable in GSC settings > Preferences | Basic monitoring |
| GSC API + custom script | Pull indexing data via API and compare to thresholds | Custom alerting |
| Crawl tool scheduled crawl + diff | Run weekly crawl, compare to previous crawl | Detailed index tracking |
| Google Alert for site:domain.com | Monitor for site disappearing from index | Emergency detection |
Indexing alert workflow:
- Alert triggers (e.g., indexed pages drop 15%).
- Check GSC Indexing report for the reason.
- Identify when the change started (compare date range).
- Correlate with deployment or configuration change.
- Fix the root cause.
- Monitor to confirm index recovery.
Ranking Alerts
Ranking alerts notify you when tracked keywords change position significantly.
What to monitor:
| Alert | Threshold | Response Time |
|---|---|---|
| Priority keyword drops out of top 5 or top 10 | Any drop below target position for priority keywords | Investigate within 24 hours |
| Cluster ranking declines | Average position for a keyword cluster drops >2 positions | Weekly review |
| Featured snippet loss | Page loses snippet for a tracked keyword | Investigate within 48 hours |
| New competitor enters top 10 for priority keyword | Any new domain in top 10 | Monthly competitive review |
| Significant rank volatility index increase | >50% increase in volatility score | Check algorithm update status |
How to set up ranking alerts:
- Most rank tracking tools (Ahrefs, Semrush, STAT, AccuRanker) have built-in alerting for position changes.
- Configure alerts for drop-out-of-top-10 and drop-out-of-top-3 separately.
- Use cluster-level alerts (average position for a keyword group) to reduce noise from individual keyword fluctuations.
warning
Ranking alert pitfall: Individual keyword positions fluctuate daily. Do not alert on every position change. Alert on significant drops (5+ positions) or drops across multiple keywords simultaneously.
Traffic Anomaly Alerts
Traffic anomaly alerts detect unusual changes in organic traffic volume or pattern.
What to monitor:
| Alert | Threshold | Response Time |
|---|---|---|
| Organic sessions drop significantly | >20% drop day-over-day or >15% drop week-over-week | Immediate investigation |
| Organic impressions drop significantly | >20% drop vs same period | Immediate |
| Non-brand organic traffic drops while brand is stable | >15% non-brand drop | Investigate content and ranking |
| Specific segment traffic drops (country, device, page type) | >30% drop for the segment | 24-hour investigation |
| Sudden traffic spike (potential bot attack or scrapers) | >100% increase with low engagement | Investigate source |
How to set up traffic anomaly alerts:
| Method | Setup |
|---|---|
| GA4 custom alerts | GA4 Administration > Custom alerts > Create alert (metric: organic sessions, condition: decreases by more than 20% compared to previous period) |
| GSC API + custom dashboard | Pull daily impression/click data, compare to 7-day rolling average |
| Google Analytics anomaly detection | Google Analytics 4 has built-in anomaly detection for some reports |
| Third-party monitoring tools | Tools like ContentKing, Rank Ranger, Wincher offer traffic anomaly alerting |
Traffic alert workflow:
- Alert triggers (e.g., organic sessions drop 25%).
- Check the GSC Performance report to see if impressions also dropped (a ranking issue) or only clicks dropped (a CTR or snippet issue).
- Segment by brand/non-brand to narrow the scope.
- Check for technical issues (server errors, robots.txt, noindex).
- Check for algorithm updates (Search Status Dashboard, tracker tools).
- Document findings and response.
Conversion Anomaly Alerts
Conversion anomaly alerts detect when organic traffic stops converting at expected rates.
What to monitor:
| Alert | Threshold | Response Time |
|---|---|---|
| Organic conversion rate drops | >20% drop week-over-week | 24-hour investigation |
| Organic revenue drops | >15% drop week-over-week | Immediate |
| Organic-assisted conversion rate drops | >20% drop | Weekly review |
| Specific page conversion rate drops | >30% drop for top 20 landing pages | 48-hour investigation |
| Cart abandonment rate (organic) increases | >15% increase | 24-hour investigation |
| Form submission error rate increases | Any error increase | Immediate |
How to set up conversion alerts:
- GA4 custom alerts for conversion events.
- Set up alerts for: conversion rate drops, revenue drops, specific goal completion drops.
- Use a rolling 7-day average as the baseline for comparison.
Conversion alert workflow:
- Alert triggers (e.g., organic conversion rate drops 25%).
- Segment by landing page: which specific pages lost conversion rate?
- Check for technical issues: page speed, form failures, checkout errors.
- Check for content changes: did the page content change without updating conversion paths?
- Check for intent mismatch: did the ranking keywords change, attracting less qualified traffic?
- Fix and monitor.
Core Web Vitals Alerts
Core Web Vitals alerts notify you when page experience metrics degrade.
What to monitor:
| Alert | Threshold | Response Time |
|---|---|---|
| CWV pass rate drops | >5% drop in "good" URLs for any metric | Weekly investigation |
| Specific URL group CWV degradation | >10% of URL group moves from "good" to "needs improvement" or "poor" | 48-hour investigation |
| LCP increases significantly | >0.5s increase for mobile or desktop average | Weekly investigation |
| CLS increases | >0.05 increase in average CLS | Weekly investigation |
| INP increases | >50ms increase | Weekly investigation |
| PageSpeed Insights score drops | >10 point drop | 48-hour investigation |
How to set up CWV alerts:
- GSC Core Web Vitals report has email notifications (enable in GSC settings).
- CrUX API can be polled for URL group-level data.
- Third-party monitoring tools (SpeedCurve, Treo, Calibre) offer real-user monitoring with alerting.
- Lighthouse CI can alert on lab data regression after each deployment.
CWV alert workflow:
- Alert triggers (e.g., mobile LCP increases from 2.2s to 3.1s).
- Identify the affected URL group (GSC CWV report groups by issue type).
- Check for recent deployments that may have affected page speed.
- Use Lighthouse or PageSpeed Insights to diagnose the specific cause.
- Fix and verify.
Server Error Alerts
Server error alerts notify you when Googlebot or users cannot access your site.
What to monitor:
| Alert | Threshold | Response Time |
|---|---|---|
| 5xx errors increase significantly | Any increase to >0.5% of crawl requests | Immediate |
| 4xx errors increase | >10% increase week-over-week | Daily check |
| DNS resolution failures | Any occurrence | Immediate |
| Robot.txt returns non-200 status | Any occurrence | Immediate |
| SSL certificate expiration | <30 days to expiry | Immediate renewal |
| Host status shows errors in GSC | Any host error | Immediate |
How to set up server error alerts:
- GSC Crawl stats email notifications.
- Server monitoring tools (Pingdom, DataDog, New Relic) with uptime and error rate thresholds.
- Custom GSC API polling for crawl error increases.
- SSL monitoring tools (many hosting providers include this).
Competitor Movement Alerts
Competitor movement alerts track significant changes in competitor SEO activity.
What to monitor:
| Alert | Threshold | Response Time |
|---|---|---|
| Competitor new content volume spikes | >50% increase in competitor content publication | Monthly review |
| Competitor gains featured snippets in your target keywords | Any new snippet gain for priority keywords | Monthly review |
| Competitor backlink velocity increases | >50% increase in competitor new referring domains | Monthly review |
| Competitor domain or subdomain structure changes | Major URL or structure change detected | Investigate for migration impact |
| Competitor enters your brand terms in SERP | Any new competitor appearing for branded queries | Immediate review |
| Competitor launches new comparison page for your category | Any new page targeting your primary keywords | Monthly review |
How to set up competitor movement alerts:
- Brand mention monitoring (Google Alerts, Mention, Brand24).
- Rank tracker competitive position change alerts.
- Backlink tool alerts for competitor new links.
- Content monitoring tools for competitor publication tracking.
Competitor alert workflow:
- Alert triggers (e.g., competitor publishes a new comparison page).
- Review the new content: format, depth, keywords, unique value proposition.
- Assess competitive threat: is this a direct response to your content?
- Plan response if needed: update your content, create a stronger asset, or monitor.
Workflow
- Define alert priorities: Critical (immediate response), Important (24-48 hour response), Informational (weekly review).
- Set up alerts: Configure in GSC, GA4, rank tracker, server monitoring, and any third-party tools.
- Document response plans: For each alert type, document the investigation steps and expected response team.
- Triage daily: Check alerts (automated or manually) for critical and important triggers.
- Investigate: Follow the documented workflow for the triggered alert.
- Respond: Fix the root cause.
- Document: Record the alert, root cause, response, and outcome.
Common Mistakes
- Too many alerts: Alert fatigue causes teams to ignore alerts. Only alert on changes that require action.
- No documented response plan: An alert without a response workflow leads to confusion. Document what to do when each alert triggers.
- Alerting without baselines: Without a baseline, you cannot determine if a change is significant. Set baselines before configuring alerts.
- Not testing alerts: Configure alerts and then test them (simulate the condition) to verify they trigger correctly.
- Reacting to every ranking fluctuation: Set appropriate thresholds to avoid alerting on normal daily movement.
Checklist
- Indexing alerts are configured for page count drops and new error types.
- Ranking alerts are configured for priority keywords with meaningful thresholds.
- Traffic anomaly alerts compare to rolling 7-day average.
- Conversion anomaly alerts track rate and revenue changes.
- Core Web Vitals alerts monitor pass rate and metric averages.
- Server error alerts cover 5xx, 4xx, DNS, and SSL.
- Competitor movement alerts track new content, backlink changes, and SERP entries.
- Alert thresholds are documented and reviewed quarterly.
- Response plans exist for each alert type.
- Alerts are tested after configuration.