القائمة
Configure SEO alerts for ranking drops, traffic changes, technical issues, competitor movements. SEO预警/排名监控
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/rome-os/rome-apps --skill alert-managerيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Use for creative/product/design work before implementation. Guides the guardian from rough idea to approved design spec.
Senior engineer code review workflow — whole-picture understanding, mandatory beyond-the-diff verification, architecture-level review (SSOT, Occam's razor), SOLID, security, performance, and code quality, with P0-P3 severity classification.
Fetch GitHub pull request diffs with gh CLI, including large-PR fallback strategies.
عرض SKILL.md
| name | alert-manager |
| description | Configure SEO alerts for ranking drops, traffic changes, technical issues, competitor movements. SEO预警/排名监控 |
| version | 6.0.0 |
| license | Apache-2.0 |
| compatibility | 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. |
| homepage | https://github.com/aaron-he-zhu/seo-geo-claude-skills |
| metadata | {"author":"aaron-he-zhu","version":"6.0.0","geo-relevance":"low","tags":["seo","geo","seo-alerts","ranking-alerts","traffic-monitoring","competitor-alerts","automated-monitoring","anomaly-detection","SEO预警","SEOアラート","SEO알림","alertas-seo"],"triggers":["set up SEO alerts","monitor rankings","ranking notifications","traffic alerts","competitor alerts","automated monitoring","notify me when rankings drop","alert me if rankings drop","notify me of traffic changes","watch competitor changes","watch my keywords for changes","alert me about changes","how to monitor my rankings","how to set up SEO alerts","SEO预警","排名监控","流量报警","竞品变动提醒","排名掉了提醒我","流量异常","有变化通知我","SEOアラート","ランキング監視","SEO 알림","순위 모니터링","alertas SEO","monitoreo de rankings","alertas de SEO","SEO allerts"]} |
SEO & GEO Skills Library · 20 skills for SEO + GEO · ClawHub · skills.sh System Mode: This monitoring skill follows the shared Skill Contract and State Model.
Sets 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.
System role: Monitoring layer skill. It turns performance changes into deltas, alerts, and next actions.
Use this when the conversation involves any of these situations — even if the user does not use SEO terminology:
Use this whenever the task needs time-aware change detection, escalation, or stakeholder-ready visibility.
Start with one of these prompts. Finish with a short handoff summary using the repository format in Skill Contract.
Set up SEO monitoring alerts for [domain]
Create ranking drop alerts for my top 20 keywords
Alert me when [specific condition]
Set up competitor monitoring for [competitor domains]
Review and optimize my current SEO alerts
Expected output: a delta summary, alert/report output, and a short handoff summary ready for memory/monitoring/.
memory/monitoring/.memory/open-loops.md and memory/decisions.md.Next Best Skill below when a change needs action.Note: All integrations are optional. This skill works without any API keys — users provide data manually when no tools are connected.
See CONNECTORS.md for tool category placeholders.
With ~~SEO tool + ~~search console + ~~web crawler connected: Automatically 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.
With manual data only: Ask the user to provide:
Proceed with the alert configuration using provided parameters. User will need to manually check metrics and report changes for alert triggers.
When a user requests alert setup:
Define Alert Categories
## SEO Alert System Configuration
**Domain**: [domain]
**Configured Date**: [date]
### Alert Categories
| Category | Description | Typical Urgency |
|----------|-------------|-----------------|
| Ranking Alerts | Keyword position changes | Medium-High |
| Traffic Alerts | Organic traffic fluctuations | High |
| Technical Alerts | Site health issues | Critical |
| Backlink Alerts | Link profile changes | Medium |
| Competitor Alerts | Competitor movements | Low-Medium |
| GEO Alerts | AI visibility changes | Medium |
| Brand Alerts | Brand mentions and reputation | Medium |
Configure Alert Rules by Category
For each relevant category (Rankings, Traffic, Technical, Backlinks, Competitors, GEO/AI, Brand), define alert name, trigger condition, threshold, and priority level.
Reference: See references/alert-configuration-templates.md for complete alert tables, threshold examples, and response plan templates for all 7 categories.
Define Alert Response Plans
Map each priority level (Critical, High, Medium, Low) to a response time and immediate action steps.
Set Up Alert Delivery
Configure notification channels (Email, SMS, Slack), recipient routing by role, suppression rules (duplicate cooldown, maintenance windows), and escalation paths.
Create Alert Summary
# SEO Alert System Summary
**Domain**: [domain]
**Configured**: [date]
**Total Active Alerts**: [X]
## Alert Count by Category
| Category | Critical | High | Medium | Low | Total |
|----------|----------|------|--------|-----|-------|
| Rankings | [X] | [X] | [X] | [X] | [X] |
| Traffic | [X] | [X] | [X] | [X] | [X] |
| Technical | [X] | [X] | [X] | [X] | [X] |
| Backlinks | [X] | [X] | [X] | [X] | [X] |
| Competitors | [X] | [X] | [X] | [X] | [X] |
| GEO | [X] | [X] | [X] | [X] | [X] |
| **Total** | **[X]** | **[X]** | **[X]** | **[X]** | **[X]** |
## Quick Reference
### If You Get a Critical Alert
1. Don't panic
2. Check alert details
3. Follow response plan
4. Document actions taken
5. Update stakeholders
### Weekly Alert Review Checklist
- [ ] Review all alerts triggered
- [ ] Identify patterns
- [ ] Adjust thresholds if needed
- [ ] Update response plans
- [ ] Clean up false positives
User: "Set up ranking drop alerts for my top keywords"
Output:
## Ranking Alert Configuration
### Critical Keywords (Immediate Alert)
| Keyword | Current | Alert If | Priority |
|---------|---------|----------|----------|
| best project management software | 2 | Drops to 5+ | 🔴 Critical |
| project management tools | 4 | Drops to 8+ | 🔴 Critical |
| team collaboration software | 1 | Any drop | 🔴 Critical |
### Important Keywords (Same-Day Alert)
| Keyword | Current | Alert If | Priority |
|---------|---------|----------|----------|
| agile project management | 7 | Drops out of top 10 | 🔴 High |
| kanban software | 9 | Drops out of top 10 | 🔴 High |
### Alert Response Plan
**If Critical Keyword Drops**:
1. Check if page is still indexed (site:url)
2. Look for algorithm update announcements
3. Analyze what changed in SERP
4. Review competitor ranking changes
5. Check for technical issues on page
6. Create recovery action plan within 24 hours
**Notification**: Email + Slack to SEO team immediately
| 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 baseline establishment, threshold setting methodology, fatigue prevention, escalation paths, and response playbooks.
After delivering monitoring data or reports to the user, ask:
"Save these results for future sessions?"
If yes, write a dated summary to memory/monitoring/YYYY-MM-DD-<topic>.md containing:
If any findings should influence ongoing strategy, recommend promoting key conclusions to memory/hot-cache.md.