---
title: "Regression protection"
description: "IndexPlane checks what your site serves every week and after every plugin, theme or core update, and tells you the moment an SEO surface moves."
url: "https://tryindexplane.com/features/protect/"
markdown: "https://tryindexplane.com/features/protect.md"
---

# Regression protection

Regression protection & alerts

IndexPlane checks what your site serves every week and after every plugin, theme or core update, and tells you the moment an SEO surface moves.

- [Download free](https://wordpress.org/plugins/indexplane/)
- [Set up weekly checks](https://tryindexplane.com/docs/monitoring/)

Plan: Free core; full event-driven monitoring and attribution in Pro.

## You find out from the traffic graph, three weeks later.

> “A routine plugin update added noindex to every product page. Nobody noticed until sales dropped.”

> “Canonicals pointed at staging for a month after a deploy.”

> “We knew something broke. We had no idea what changed around then.”

## Regression protection

### Weekly checks, plus a check after every update

Checks run on a schedule and again right after plugin, theme and core updates. Run them from system cron for reliability.

[Read how it works](https://tryindexplane.com/docs/monitoring.md)

### Incidents grouped by template, with blast radius

One incident per regression, not 800 rows. See which template broke and how far it spread: “Product · 120/120 URLs”.

[Read how it works](https://tryindexplane.com/docs/monitoring.md)

### “What changed around then”

Every regression sits next to the WordPress events that happened around it: updates, settings changes, deploys. Correlated, not claimed as proven cause.

[Read how it works](https://tryindexplane.com/docs/monitoring.md)

### Alerts where you work

One email per incident, never a flood. Slack and signed webhooks in Pro.

[Read how it works](https://tryindexplane.com/docs/monitoring.md)

## What you can check for yourself.

- Checks your site’s own served HTML from inside WordPress: no external crawler.
- Template cohorts mean one incident per broken template.
- Fail-open: if a check can’t run, your site keeps serving normally.