- name
- alert-manager
- description
- Configure SEO alerts for ranking drops, traffic changes, technical issues, competitor movements. SEO预警/排名监控
- version
- 9.9.5
- license
- Apache-2.0
- compatibility
- Claude Code, skills.sh, ClawHub, Vercel Labs, Cursor, Windsurf, Codex CLI, Amp, Gemini CLI, Kimi Code, Qwen Code, CodeBuddy
- homepage
- https://github.com/aaron-he-zhu/seo-geo-claude-skills
- when_to_use
- Use when setting up monitoring alerts for rankings, traffic, backlinks, technical issues, or AI visibility changes.
- argument-hint
- <domain> [metric]
- metadata
- author
- aaron-he-zhu
- version
- 9.9.5
- geo-relevance
- low
- tags
- triggers
Alert Manager
Sets up proactive monitoring alerts for ranking, traffic, technical, backlink, competitor, and GEO changes.
Quick Start
Set up SEO monitoring alerts for [domain]Create ranking drop alerts for my top 20 keywordsSkill Contract
Expected output: an alert configuration summary plus the standard handoff summary for memory/monitoring/.
- Reads: current metrics, baselines, alert thresholds, and reporting context from CLAUDE.md and the shared State Model when available.
- Writes: a user-facing monitoring deliverable and reusable summary.
- Promotes: significant anomalies, durable thresholds, and follow-up actions to
memory/open-loops.mdandmemory/decisions.md. - Primary next skill: performance-reporter when alert output needs a reporting cadence.
Handoff Summary
Emit the standard shape from skill-contract.md §Handoff Summary Format.
Data Sources
All integrations optional (see CONNECTORS.md). With tools, monitor real-time feeds from ~~SEO tool, ~~search console, and ~~web crawler. Without tools, ask for baselines, critical keywords, preferences, and historical data.
Instructions
When a user requests alert setup:
- Define Alert Categories — choose from rankings, traffic, technical, backlinks, competitors, GEO / AI, and brand alerts.
- Configure Alert Rules by Category — define trigger condition, threshold, alert name, and priority for each relevant rule.
- Define Alert Response Plans — map Critical / High / Medium / Low to response time and next actions.
- Set Up Alert Delivery — configure channels, routing, cooldowns, maintenance windows, and escalation paths.
- Create Alert Summary — deliver category counts, critical playbook, and weekly review checklist.
Reference: See references/alert-configuration-templates.md for the full category tables, thresholds, and response-plan templates.
Example
Sample outcome: a keyword alert matrix with Critical vs High thresholds, a response plan for drops, and notification routing to email + Slack.
Tips for Success
Start simple, tune thresholds to normal volatility, avoid alert fatigue, and review the system regularly.
Alert Threshold Quick Reference
| Metric | Warning | Critical | Frequency |
|---|---|---|---|
| Organic traffic | -15% WoW | -30% WoW | Daily |
| Keyword positions | >3 position drop | >5 position drop | Daily |
| Pages indexed | -5% change | -20% change | Weekly |
| Crawl errors | >10 new/day | >50 new/day | Daily |
| Core Web Vitals | "Needs Improvement" | "Poor" | Weekly |
| Backlinks lost | >5% in 1 week | >15% in 1 week | Weekly |
| AI citation loss | Any key query | >20% queries | Weekly |
| Security issues | Any detected | Any detected | Daily |
Reference: See references/alert-threshold-guide.md for threshold setting, fatigue prevention, escalation paths, and response playbooks.
Save Results
Ask "Save these results?" If yes, write memory/monitoring/YYYY-MM-DD-<topic>.md with headline finding, actions, and open loops.
Reference Materials
- Alert Threshold Guide — Thresholds, fatigue prevention, and escalation templates
Next Best Skill
Reporting cadence requested → performance-reporter. Standalone setup → Terminal. Visited-set rule applies per skill-contract.md.