# SEO Monitoring Plan

**Site:** [https://example.com]  
**Monitoring owner:** [Name or role]  
**Baseline reviewer:** [Name or role]  
**Baseline approved:** [Date and time]  
**Normal check cadence:** [Daily / weekly / custom]  
**Incident contact:** [Name or role]  

> Replace every bracketed prompt. Keep performance outcomes, intentional releases, and observed public-page changes in their appropriate evidence systems. A detected page change does not by itself prove a ranking, traffic, lead, or revenue impact.

## 1. Scope and priorities

List only pages whose unexpected movement would trigger a real decision.

| Priority | Page | Why it is monitored | Included public signals | Cadence | Owner |
| --- | --- | --- | --- | --- | --- |
| [Critical / high / normal] | [URL] | [Revenue / traffic / active release / template risk] | [Response / robots / canonical / title / H1 / copy / schema / social / alt / favicon] | [ ] | [ ] |

**Explicitly outside scope:** [Browser-only rendering, authenticated content, performance metrics, rankings, conversions, or other boundaries]

## 2. Approved baseline register

An approved baseline is a reviewed public state, not merely the first captured value.

| Page | Signal | Approved value | Approved UTC | Reviewer | Release or decision evidence |
| --- | --- | --- | --- | --- | --- |
| [URL] | [Field] | [Exact value] | [ ] | [ ] | [Ticket, change log, or note] |

## 3. Recurring check register

| Checked UTC | Page | Signal | Approved value | Current value | Status | Severity | Evidence |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [ ] | [URL] | [Field] | [ ] | [ ] | [Unchanged / changed / unavailable] | [Critical / review / notice] | [Public response or snapshot] |

## 4. Detected-change review

Complete this section before restoring or accepting a changed value.

- **Detected UTC:** [ ]
- **Page and field:** [ ]
- **Approved value:** [ ]
- **Current value:** [ ]
- **Observable risk:** [What the public difference can prove]
- **Impact not yet proven:** [Ranking, traffic, conversion, or business effects requiring separate evidence]
- **Intent:** [Approved / unapproved / unknown]
- **Decision owner:** [ ]
- **Decision:** [Restore / approve new value / investigate / log only]
- **Due UTC:** [ ]

## 5. Resolution evidence

- **Action completed:** [ ]
- **Owner:** [ ]
- **Completed UTC:** [ ]
- **Validated public value:** [ ]
- **Validation UTC:** [ ]
- **Evidence link or reference:** [ ]
- **Baseline decision:** [Keep original / approve current value as the new baseline]

## 6. Periodic monitoring review

Review the plan monthly or after a major launch.

- Remove pages or fields that never lead to a decision.
- Add newly important revenue, traffic, campaign, or template pages.
- Confirm every monitored item still has an owner.
- Review missed or delayed checks.
- Link intentional releases to the change log.
- Link material incidents and outcomes to the client report.
- Confirm the check’s technical boundaries are still accurate.

## 7. Escalation rules

| Severity | Example observable change | Expected response |
| --- | --- | --- |
| Critical | New noindex, site-wide block, harmful redirect, failed response, off-domain canonical | Review promptly, confirm intent, preserve evidence, and restore only when approved |
| Review | Title, H1, meaningful copy, or important social field changed | Review during the agreed operating window and compare with the release record |
| Notice | Lower-risk descriptive or structured-data movement | Log or batch for review unless context raises the risk |

**Final boundary:** This plan supports public-page change control. Use Search Console, analytics, CRM data, release records, rendering tests, logs, and human review for the questions they are designed to answer.