# web-monitor

Web Monitor

## Overview
Web Monitor is the skill of tracking important web pages so you can react before changes hurt your pipeline, positioning, pricing, or delivery quality. A one-person company cannot manually re-check competitor pages, vendor pricing pages, partner directories, and platform policy pages every day. This skill gives you a repeatable monitoring workflow with clear alerts and clear next actions.

## When to Use This Skill
Use this when you depend on external pages for revenue or operations, including competitor offer pages, referral directories, ad platform policy pages, API pricing pages, and marketplace listings. Use it when sudden changes can create churn risk, margin compression, or broken promises in your sales copy.

## What This Skill Does
This skill sets up focused page watchers, records snapshots, computes diffs, and helps you prioritize the business impact of each detected change. It is not just about collecting updates. The goal is to convert page changes into actionable decisions: update your offer, adjust pricing, revise your sales page, or trigger a customer communication.

## How to Use
Step 1: Define your monitored page set by business risk. Start with pages tied to pricing, acquisition channels, policy constraints, and delivery dependencies.

Step 2: Attach a business tag to each monitored page: `revenue`, `conversion`, `delivery`, `compliance`, or `strategic-watch`.

Step 3: Monitor only the stable section that matters (for example pricing table or policy body) to reduce false alerts from navigation, ads, or timestamps.

Step 4: Run checks on a fixed cadence. Daily for pricing and policy pages, weekly for lower-risk strategic pages.

Step 5: Triage each detected change with a simple severity rubric:
- `P0`: immediate revenue risk or compliance risk
- `P1`: conversion or margin impact
- `P2`: informational change with no immediate action

Step 6: Log the action taken for each meaningful change: update positioning, update offer copy, update onboarding docs, or update internal SOPs.

Step 7: Review weekly what changed, what actions were shipped, and what impact was observed in leads, conversion, churn, or support load.

## Output
The output should include:
- Monitored URL inventory with risk tags and owners
- A dated change log with before/after snippets
- Severity labels (`P0/P1/P2`) for each alert
- Action decisions and shipped updates
- A short weekly summary for decision review

## Common Mistakes
Do not monitor too many pages without priority labels.  
Do not treat every diff as urgent without impact scoring.  
Do not monitor entire pages when a specific selector is enough.  
Do not collect alerts without documenting what decision was made.  
Do not keep monitoring pages that have shown zero strategic value for multiple cycles.

## Example Monitoring Set for a Solo Operator
- Competitor pricing page and offer page
- Your top acquisition channel policy page
- Your payment processor fee and policy updates
- Your primary AI vendor pricing or usage policy page
- Your own sales page and checkout page for unexpected content drift

## What Good Looks Like
A healthy monitoring workflow catches material external changes within one cycle, routes them through a clear triage process, and leads to concrete updates in your pricing, messaging, delivery, or risk controls. The system should reduce surprises and improve decision speed, not create alert fatigue.