Change Log
The structured change log. Every SEO, content or technical change you ship is recorded as a Change Log entry with a type, a date, the page groups / URLs it affects, and (optionally) a Jira / Git link and a before/after note. Metricstab shows it on every traffic chart next to what your traffic did, and can turn it into an SEO test.
Why bother logging changes?
Most SEO teams ship 20–50 changes a month and can't tell you which ones moved the needle. A structured change log fixes that. Once a change is logged, Metricstab can:
- Overlay it on every traffic chart so you can see the impact in context.
- Use it as the deployment date of an SEO test (Test this change).
- Draw it on the chart of every SEO test whose dates it falls inside, so a result is read next to whatever else changed at the time.
Where to log a change
Open the Change Log page from the left-hand site nav and click Add Change Log entry. Title, type and start date are the only required fields. Everything else is optional.
You can also log events from Manage site → Change Log entries if you prefer.
Field reference
| Field | Required? | What it does |
|---|---|---|
| Title | Yes | Short label that appears on chart markers and in dashboards. |
| Change type | Yes | Controlled vocabulary (title, meta, content refresh, schema, internal links, canonical, robots, redirect, template, performance, algorithm, other). Shown on the marker and used to filter the Change Log. |
| Start date | Yes | The day the change went live. It becomes the deployment date when you start an SEO test from this event. |
| End date | No | For multi-day rollouts (e.g. a phased migration). Leave blank for a single-day change. |
| Expected impact window | No | How many days you expect Google to take to react. Recorded with the event for your own reference. |
| Hypothesis / context | No | One-line statement of what you expect to happen. The single biggest safeguard against post-hoc rationalisation. |
| Page groups | No | Which configured page groups are affected. Reuses your existing Page Groups rules; recorded on the event. |
| Specific URLs | No | Newline-separated URLs for changes that don't fit a group or type (e.g. a single hub page). |
| Before / After | No | Snapshot of the field that changed (e.g. old title text vs new title text), kept with the event so you can see later exactly what was changed. |
| Jira / Linear URL | No | Link back to the ticket where the work was tracked. |
| GitHub / GitLab URL | No | Link back to the PR or commit that shipped the change. |
Change-type vocabulary
Pick the closest match. The vocabulary is intentionally controlled so the Change Log filter stays meaningful.
| Type | When to use it | Suggested expected-impact window |
|---|---|---|
| Title change | Rewriting <title> tags on one or many pages. |
~14 days |
| Meta description change | Rewriting <meta name="description">. |
~14 days |
| H1 change | Editing the visible H1 heading. | ~21 days |
| Content refresh | Material rewrite or expansion of body copy. | ~42 days |
| Structured data / schema | Adding or removing JSON-LD, microdata, etc. | ~14 days |
| Internal linking | Adding hub links, breadcrumbs, related-content modules. | ~30 days |
| Canonical change | Adding/removing/changing rel=canonical.
High-risk. |
~21 days |
| Robots / noindex change | robots.txt or page-level noindex changes.
High-risk. |
~21 days |
| Redirect change | 301/302 changes, redirect chain edits. | ~21 days |
| Template change | Markup changes that affect a whole category of pages at once. | ~30 days |
| Performance / speed change | Image optimisation, JS removal, CDN changes affecting Core Web Vitals. | ~30 days |
| Google algorithm update | Confirmed Google update (Core, Spam, Helpful Content…) — log it so other experiments running in this window get a confounding warning. | ~14 days |
| Other SEO change | Anything that doesn't fit above. | — |
| Note / Release / Migration / Incident | Free-form Phase 1 Change Log entries, kept for backward compatibility. | — |
What happens after you log a change
- It immediately appears as a Change Log marker on every traffic chart for the targeted period.
- It appears on the site's Change Log page (accessible from the left-hand nav under Change Log), where it can be filtered by type or searched by title.
- It is visible to the “What changed this period?” Overview card, so executive recaps reference real shipped work.
- You can test it: Test this change on the Change Log opens a new SEO test with the change's title, date, type and specific URLs already filled in, so you can measure a change you made weeks or months ago. The test then appears under the change, with its verdict once it finishes.
- It is drawn on the chart of every SEO test whose dates it falls inside, so a test's result can be read next to whatever else changed at the time.
You don't need to log Google's own updates: core, spam and other ranking updates are added to the same charts automatically (in blue, labelled Google:) from Google's public Search Status Dashboard, which covers roughly the last year. A marker shows that an update happened at the same time — not that it caused a change in your traffic.
Related features
- Traffic Trend — Change Log entry markers appear as vertical lines on this chart.
- SEO Tests — Start a test from any change with Test this change; the change's date becomes the test's deployment date.
- Insights Reference — Logged changes surface in the “What Changed” narrative on the Overview Dashboard.
Integrity notes
- Log before you ship when you can. Logging in arrears is fine but the hypothesis field gets weaker the further you are from the change.
- One Change Log entry per discrete change. If you ship a title rewrite and a schema addition together, log them as two events on the same date, so a test started from either one is read next to the other.
- Don't backfill the “After” field with the result. The before/after fields describe the page state, not the metric outcome. The outcome lives in the SEO test you start from the event.