The playbook
Website Migration SEO: Metrics and Measurement
Measure website migration SEO by defining priority migrated URLs passing checks precisely enough that two people can reproduce the result from the same records. Keep the reporting unit, date basis, and scope visible. Without those definitions, a change in the report may reflect a changed calculation rather than a changed customer outcome.
Put the task in context
Create the old-to-new URL map before release, including high-value pages, downloads, and linked resources. Test a representative set in staging and production. After launch, investigate missing destinations and redirect errors separately from expected short-term measurement variability.
Create a metric definition
| Definition field | What it must explain |
|---|---|
| Measure | priority migrated URLs passing checks |
| Unit | What one page or query record or completed outcome represents |
| Included records | The scope identified by old URL and new URL |
| Date basis | The event date or period used to include a record |
| Exclusions | Tests, duplicates, or other records outside the agreed definition |
| Source owner | analytics owner |
Separate delivery checks from outcome measures
A delivery check asks whether the team completed a specific task, such as inventory current URLs and their search value. An outcome measure asks what happened for the user or business afterward. Keep both visible. Completing the task is useful evidence of execution, but it does not by itself prove that the broader outcome improved.
Worked arithmetic example
Suppose an illustrative review includes 80 eligible records, and 60 satisfy the explicitly defined completion condition. The completion share is 60 ÷ 80 × 100 = 75%. This is hypothetical arithmetic, not an industry benchmark or a predicted improvement. It describes only the population and condition you defined.
For website migration SEO, explain the condition before applying that calculation. If the question is whether the team can compare indexing traffic and errors after release, a record counts only when the evidence demonstrates that condition. Do not replace missing outcomes with successful ones just to complete a report.
Compare like with like
Keep the scope, date basis, and exclusions consistent between observations. If new URL changes meaning between periods, note the change and rebuild a comparable view where possible. A rate can also move because the composition of the underlying group changed, even when individual performance did not.
Investigate an unexpected result
- Check whether the underlying old URL records are complete.
- Look for this known failure: launching without a complete mapping of important old pages.
- Verify that the process still includes: map destinations and test redirects before launch.
- Reconcile a sample with the original record before changing the operating plan.
Use the report to choose an action
If the evidence supports a correction, restore missing destinations and repair mappings using the inventory. Record when the change occurred and what should be checked next. Keep uncertainty visible when the sample is small or the observation period is incomplete. The purpose of measurement is a better decision about priority migrated URLs passing checks, not a favorable-looking number.
Keep a dated record of the page or query being examined. Search interfaces and external references can change. A saved observation should include enough context to distinguish an old issue from the current state.
Skip the manual steps. Let AgentixSEO run this for every client.
Start now