Workflow: Build alerts and response plays
Define alert rules, response playbooks, defense pages, and a weekly report template.
Add your data
Adding details ensures a relevant result
Save time by automatically applying details and getting ready-to-use prompts.
Prompt
Create a competitor monitoring alert ruleset for {your-domain.com} in {country}.
These alerts are designed to detect when monitored competitors make meaningful moves and when {your-domain.com} loses ground. Do NOT generate alerts for {your-domain.com} gains — the purpose is early warning, not reporting success.
Cover two signal categories:
* competitor_gain: a monitored competitor gains organic traffic, rankings, or visibility above threshold in clusters overlapping with {your-domain.com}
* own_loss: {your-domain.com} drops in rankings, traffic share, or keyword visibility in a monitored cluster
Base metric signals on organic traffic trend over time and on position changes in shared keywords (organic search results).
Return ONE table:
Columns:
* alert_name
* signal_type (competitor_gain / own_loss)
* metric
* threshold
* cadence
* action_owner_role
* what_to_investigate
Include at least 8 alert rules — minimum 5 of type competitor_gain, minimum 2 of type own_loss.
Example Output (illustrative)
- A table of 8+ alert rules split into two types — competitor_gain (min 5: competitor traffic surge, keyword expansion, SERP position grabs in shared clusters) and own_loss (min 2: own traffic drop, position losses in shared clusters) — with metric, threshold, cadence, owner role, and what to investigate per alert