SEO drift (baseline and regressions)
A “Git for SEO”: detect what a deployment broke
Open the page in the appThe problem it solves
The most common cause of a sudden traffic drop is not a Google algorithm: it is a deployment that silently removed a canonical, added a noindex, or made the Schema disappear. Nobody notices until rankings drop, days later. SEO Drift works like a version control system: it photographs the SEO state of your key pages (the “baseline”), then compares the current state against that photo on every check.
What the baseline captures
For each monitored URL (up to 25 per project), PivotSEO records: title, meta description, canonical, meta robots, the list of H1/H2/H3s, the JSON-LD structured data types with a fingerprint (hash) of their content, Open Graph tags, HTTP status code, word count and a fingerprint of the visible content. Fingerprints detect even minimal changes without storing the whole page.
The 15 comparison rules
- Critical (immediate action) — page in 4xx/5xx error, Schema entirely removed, canonical changed or removed, noindex added, H1 removed, H1 changed by more than 50% (measured similarity), title removed. These changes cause measurable traffic loss within days.
- Warnings (investigate within a week) — title changed, meta description changed or removed, Open Graph tags gone, Schema content modified, more than 40% of visible content lost (often a sign rendering now depends on JavaScript).
- Info (tracking only) — new Schema added (positive change), H2 structure changed, content changed with no SEO regression detected.
Recommended workflow
- 1. Add your strategic pages (homepage, service pages, pillar articles) and capture the baseline.
- 2. After every deployment of your site, click “Check for drift now”.
- 3. Each deviation shows the before/after: fix critical ones immediately.
- 4. If a change is intentional (new optimized title, redesign), click the camera icon to recapture the baseline and accept the new state.
