Alert Manager

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.

When This Must Trigger

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.

• Setting up SEO monitoring systems
• Creating ranking drop alerts
• Monitoring technical SEO health
• Tracking competitor movements
• Alerting on content performance changes
• Monitoring GEO/AI visibility changes
• Setting up brand mention alerts

What This Skill Does

1. Alert Configuration: Sets up custom alert thresholds
2. Multi-Metric Monitoring: Tracks rankings, traffic, technical issues
3. Threshold Management: Defines when alerts trigger
4. Priority Classification: Categorizes alerts by severity
5. Notification Setup: Configures how alerts are delivered
6. Alert Response Plans: Creates action plans for each alert type
7. Alert History: Tracks alert patterns over time

Quick Start

Start with one of these prompts. Finish with a short handoff summary using the repository format in Skill Contract.

Set Up Alerts

Set up SEO monitoring alerts for [domain]

Create ranking drop alerts for my top 20 keywords

Configure Specific Alerts

Alert me when [specific condition]

Set up competitor monitoring for [competitor domains]

Review Alert System

Review and optimize my current SEO alerts

Skill Contract

Expected output: a delta summary, alert/report output, and a short handoff summary ready for memory/monitoring/.

• Reads: current metrics, previous baselines, alert thresholds, and reporting context from CLAUDE.md and the shared State Model when available.
• Writes: a user-facing monitoring deliverable plus a reusable summary that can be stored under memory/monitoring/.
• Promotes: significant changes, confirmed anomalies, and follow-up actions to memory/open-loops.md and memory/decisions.md.
• Next handoff: use the Next Best Skill below when a change needs action.

Data Sources

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:

1. Current baseline metrics for alert thresholds (rankings, traffic, backlinks)
2. Critical keywords or pages to monitor
3. Alert priority levels and notification preferences
4. Historical data to understand normal fluctuation ranges
5. Manual reporting on metric changes when they check their tools

Proceed with the alert configuration using provided parameters. User will need to manually check metrics and report changes for alert triggers.

Instructions

When a user requests alert setup:

1. 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 |
   

2. 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.

3. Define Alert Response Plans

   Map each priority level (Critical, High, Medium, Low) to a response time and immediate action steps.

4. Set Up Alert Delivery

   Configure notification channels (Email, SMS, Slack), recipient routing by role, suppression rules (duplicate cooldown, maintenance windows), and escalation paths.

5. 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
   

Validation Checkpoints

Input Validation

• Alert thresholds are based on realistic baseline data
• Critical keywords and pages clearly identified
• Response plans defined for each alert priority level
• Notification channels configured with appropriate recipients

Output Validation

• Every metric cites its data source and collection date
• Alert thresholds account for normal metric fluctuations
• Response plans are specific and time-bound
• Source of each alert trigger clearly stated (~~SEO tool API alert, ~~search console notification, ~~web crawler alert, or manual user check)

Example

User: "Set up ranking drop alerts for my top keywords"

Output:

## Ranking Alert Configuration

### Critical Keywords (Immediate Alert)

| Keyword | Current | Alert If | Priority |