Alert Manager

1---2name: alert-manager3description: 'Configure SEO alerts for ranking drops, traffic changes, technical issues, competitor movements. SEO预警/排名监控'4version: "9.0.0"5license: Apache-2.06compatibility: "Claude Code ≥1.0, skills.sh marketplace, ClawHub marketplace, Vercel Labs skills ecosystem. No system packages required. Optional: MCP network access for SEO tool integrations."7homepage: "https://github.com/aaron-he-zhu/seo-geo-claude-skills"8when_to_use: "Use when setting up monitoring alerts for rankings, traffic, backlinks, technical issues, or AI visibility changes."9argument-hint: "<domain> [metric]"10metadata:11  author: aaron-he-zhu12  version: "9.0.0"13  geo-relevance: "low"14  tags:15    - seo16    - geo17    - seo-alerts18    - ranking-alerts19    - traffic-monitoring20    - competitor-alerts21    - automated-monitoring22    - anomaly-detection23    - SEO预警24    - SEOアラート25    - SEO알림26    - alertas-seo27  triggers:28    # EN-formal29    - "set up SEO alerts"30    - "monitor rankings"31    - "ranking notifications"32    - "traffic alerts"33    - "competitor alerts"34    - "automated monitoring"35    # EN-casual36    - "notify me when rankings drop"37    - "alert me if rankings drop"38    - "notify me of traffic changes"39    - "watch competitor changes"40    - "watch my keywords for changes"41    - "alert me about changes"42    # EN-question43    - "how to monitor my rankings"44    - "how to set up SEO alerts"45    # ZH-pro46    - "SEO预警"47    - "排名监控"48    - "流量报警"49    - "竞品变动提醒"50    # ZH-casual51    - "排名掉了提醒我"52    - "流量异常"53    - "有变化通知我"54    # JA55    - "SEOアラート"56    - "ランキング監視"57    # KO58    - "SEO 알림"59    - "순위 모니터링"60    # ES61    - "alertas SEO"62    - "monitoreo de rankings"63    # PT64    - "alertas de SEO"65    # Misspellings66    - "SEO allerts"67---68 69# Alert Manager70 71 72> **[SEO & GEO Skills Library](https://github.com/aaron-he-zhu/seo-geo-claude-skills)** · 20 skills for SEO + GEO · [ClawHub](https://clawhub.ai/u/aaron-he-zhu) · [skills.sh](https://skills.sh/aaron-he-zhu/seo-geo-claude-skills)73> **System Mode**: This monitoring skill follows the shared [Skill Contract](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/references/skill-contract.md) and [State Model](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/references/state-model.md).74 75 76Sets up proactive monitoring alerts for critical SEO and GEO metrics. Triggers notifications when rankings drop, traffic changes significantly, technical issues occur, or competitors make moves.77 78**System role**: Monitoring layer skill. It turns performance changes into deltas, alerts, and next actions.79 80## When This Must Trigger81 82Use this when the conversation involves time-aware change detection, escalation, or stakeholder-ready visibility — even if the user doesn't use SEO terminology:83 84- Setting up SEO monitoring systems85- Creating ranking drop alerts86- Monitoring technical SEO health87- Tracking competitor movements88- Alerting on content performance changes89- Monitoring GEO/AI visibility changes90- Setting up brand mention alerts91 92## What This Skill Does93 941. **Alert Configuration**: Sets up custom alert thresholds952. **Multi-Metric Monitoring**: Tracks rankings, traffic, technical issues963. **Threshold Management**: Defines when alerts trigger974. **Priority Classification**: Categorizes alerts by severity985. **Notification Setup**: Configures how alerts are delivered996. **Alert Response Plans**: Creates action plans for each alert type1007. **Alert History**: Tracks alert patterns over time101 102## Quick Start103 104Start with one of these prompts. Finish with a short handoff summary using the repository format in [Skill Contract](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/references/skill-contract.md).105 106### Set Up Alerts107 108```109Set up SEO monitoring alerts for [domain]110```111 112```113Create ranking drop alerts for my top 20 keywords114```115 116### Configure Specific Alerts117 118```119Alert me when [specific condition]120```121 122```123Set up competitor monitoring for [competitor domains]124```125 126### Review Alert System127 128```129Review and optimize my current SEO alerts130```131 132## Skill Contract133 134**Expected output**: a delta summary, alert/report output, and a short handoff summary ready for `memory/monitoring/`.135 136- **Reads**: current metrics, previous baselines, alert thresholds, and reporting context from [CLAUDE.md](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/CLAUDE.md) and the shared [State Model](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/references/state-model.md) when available.137- **Writes**: a user-facing monitoring deliverable plus a reusable summary that can be stored under `memory/monitoring/`.138- **Promotes**: significant changes, confirmed anomalies, and follow-up actions to `memory/open-loops.md` and `memory/decisions.md`.139- **Next handoff**: use the `Next Best Skill` below when a change needs action.140 141### Handoff Summary142 143Emit this shape when finishing the skill (see [skill-contract.md §Handoff Summary Format](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/references/skill-contract.md) for the authoritative format):144 145- **Status**: DONE / DONE_WITH_CONCERNS / BLOCKED / NEEDS_INPUT146- **Objective**: what was analyzed, created, or fixed147- **Key Findings / Output**: the highest-signal result148- **Evidence**: URLs, data points, or sections reviewed149- **Open Loops**: blockers, missing inputs, or unresolved risks150- **Recommended Next Skill**: one primary next move151 152## Data Sources153 154> **Note:** All integrations are optional. This skill works without any API keys — users provide data manually when no tools are connected.155 156> See [CONNECTORS.md](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/CONNECTORS.md) for tool category placeholders.157 158**With ~~SEO tool + ~~search console + ~~web crawler connected:**159Automatically monitor real-time metric feeds for ranking changes via ~~SEO tool API, indexing and coverage alerts from ~~search console, and technical health alerts from ~~web crawler. Set up automated threshold-based alerts with notification delivery.160 161**With manual data only:**162Ask the user to provide:1631. Current baseline metrics for alert thresholds (rankings, traffic, backlinks)1642. Critical keywords or pages to monitor1653. Alert priority levels and notification preferences1664. Historical data to understand normal fluctuation ranges1675. Manual reporting on metric changes when they check their tools168 169Proceed with the alert configuration using provided parameters. User will need to manually check metrics and report changes for alert triggers.170 171## Instructions172 173When a user requests alert setup:174 1751. **Define Alert Categories**176 177   ```markdown178   ## SEO Alert System Configuration179   180   **Domain**: [domain]181   **Configured Date**: [date]182   183   ### Alert Categories184   185   | Category | Description | Typical Urgency |186   |----------|-------------|-----------------|187   | Ranking Alerts | Keyword position changes | Medium-High |188   | Traffic Alerts | Organic traffic fluctuations | High |189   | Technical Alerts | Site health issues | Critical |190   | Backlink Alerts | Link profile changes | Medium |191   | Competitor Alerts | Competitor movements | Low-Medium |192   | GEO Alerts | AI visibility changes | Medium |193   | Brand Alerts | Brand mentions and reputation | Medium |194   ```195 1962. **Configure Alert Rules by Category**197 198   For each relevant category (Rankings, Traffic, Technical, Backlinks, Competitors, GEO/AI, Brand), define alert name, trigger condition, threshold, and priority level.199 200   > **Reference**: See [references/alert-configuration-templates.md](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/monitor/alert-manager/references/alert-configuration-templates.md) for complete alert tables, threshold examples, and response plan templates for all 7 categories.201 2023. **Define Alert Response Plans**203 204   Map each priority level (Critical, High, Medium, Low) to a response time and immediate action steps.205 2064. **Set Up Alert Delivery**207 208   Configure notification channels (Email, SMS, Slack), recipient routing by role, suppression rules (duplicate cooldown, maintenance windows), and escalation paths.209 2105. **Create Alert Summary**211 212    ```markdown213    # SEO Alert System Summary214    215    **Domain**: [domain]216    **Configured**: [date]217    **Total Active Alerts**: [X]218    219    ## Alert Count by Category220    221    | Category | Critical | High | Medium | Low | Total |222    |----------|----------|------|--------|-----|-------|223    | Rankings | [X] | [X] | [X] | [X] | [X] |224    | Traffic | [X] | [X] | [X] | [X] | [X] |225    | Technical | [X] | [X] | [X] | [X] | [X] |226    | Backlinks | [X] | [X] | [X] | [X] | [X] |227    | Competitors | [X] | [X] | [X] | [X] | [X] |228    | GEO | [X] | [X] | [X] | [X] | [X] |229    | **Total** | **[X]** | **[X]** | **[X]** | **[X]** | **[X]** |230    231    ## Quick Reference232    233    ### If You Get a Critical Alert234    235    1. Don't panic236    2. Check alert details237    3. Follow response plan238    4. Document actions taken239    5. Update stakeholders240    241    ### Weekly Alert Review Checklist242    243    - [ ] Review all alerts triggered244    - [ ] Identify patterns245    - [ ] Adjust thresholds if needed246    - [ ] Update response plans247    - [ ] Clean up false positives248    ```249 250## Validation Checkpoints251 252### Input Validation253- [ ] Alert thresholds are based on realistic baseline data254- [ ] Critical keywords and pages clearly identified255- [ ] Response plans defined for each alert priority level256- [ ] Notification channels configured with appropriate recipients257 258### Output Validation259- [ ] Every metric cites its data source and collection date260- [ ] Alert thresholds account for normal metric fluctuations261- [ ] Response plans are specific and time-bound262- [ ] Source of each alert trigger clearly stated (~~SEO tool API alert, ~~search console notification, ~~web crawler alert, or manual user check)263 264## Example265 266**User**: "Set up ranking drop alerts for my top keywords"267 268**Output**:269 270```markdown271## Ranking Alert Configuration272 273### Critical Keywords (Immediate Alert)274 275| Keyword | Current | Alert If | Priority |276|---------|---------|----------|----------|277| best project management software | 2 | Drops to 5+ | 🔴 Critical |278| project management tools | 4 | Drops to 8+ | 🔴 Critical |279| team collaboration software | 1 | Any drop | 🔴 Critical |280 281### Important Keywords (Same-Day Alert)282 283| Keyword | Current | Alert If | Priority |284|---------|---------|----------|----------|285| agile project management | 7 | Drops out of top 10 | 🔴 High |286| kanban software | 9 | Drops out of top 10 | 🔴 High |287 288### Alert Response Plan289 290**If Critical Keyword Drops**:2911. Check if page is still indexed (site:url)2922. Look for algorithm update announcements2933. Analyze what changed in SERP2944. Review competitor ranking changes2955. Check for technical issues on page2966. Create recovery action plan within 24 hours297 298**Notification**: Email + Slack to SEO team immediately299```300 301## Tips for Success302 3031. **Start simple** - Don't create too many alerts initially3042. **Tune thresholds** - Adjust based on normal fluctuations3053. **Avoid alert fatigue** - Too many alerts = ignored alerts3064. **Document response plans** - Know what to do when alerts fire3075. **Review regularly** - Alerts need maintenance as your SEO matures3086. **Include positive alerts** - Track wins, not just problems309 310## Alert Threshold Quick Reference311 312| Metric | Warning | Critical | Frequency |313|--------|---------|----------|-----------|314| Organic traffic | -15% WoW | -30% WoW | Daily |315| Keyword positions | >3 position drop | >5 position drop | Daily |316| Pages indexed | -5% change | -20% change | Weekly |317| Crawl errors | >10 new/day | >50 new/day | Daily |318| Core Web Vitals | "Needs Improvement" | "Poor" | Weekly |319| Backlinks lost | >5% in 1 week | >15% in 1 week | Weekly |320| AI citation loss | Any key query | >20% queries | Weekly |321| Security issues | Any detected | Any detected | Daily |322 323> **Reference**: See [references/alert-threshold-guide.md](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/monitor/alert-manager/references/alert-threshold-guide.md) for baseline establishment, threshold setting methodology, fatigue prevention, escalation paths, and response playbooks.324 325 326### Save Results327 328After delivering monitoring data or reports to the user, ask:329 330> "Save these results for future sessions?"331 332If yes, write a dated summary to `memory/monitoring/YYYY-MM-DD-<topic>.md` containing:333- One-line headline finding or status change334- Top 3-5 actionable items335- Open loops or anomalies requiring follow-up336- Source data references337 338If any findings should influence ongoing strategy, recommend promoting key conclusions to `memory/hot-cache.md`.339 340## Reference Materials341 342- [Alert Threshold Guide](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/monitor/alert-manager/references/alert-threshold-guide.md) — Recommended thresholds by metric, fatigue prevention strategies, and escalation path templates343 344## Next Best Skill345 346Follows the verdict-conditional branching pattern in [skill-contract.md §Termination rules for Next Best Skill chains](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/references/skill-contract.md). Visited-set rule applies.347 348- **Alert configuration just completed and reporting cadence is requested** → Primary: [performance-reporter](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/monitor/performance-reporter/SKILL.md) — fold the configured alerts into a recurring stakeholder report.349- **Alert configuration is a standalone setup (no reporting loop)** → Terminal (chain ends).350- **Visited-set exception**: if `rank-tracker` invoked this skill for threshold setup, do NOT hand back to `rank-tracker` — STOP chain and report chain-complete.