Public spec
Migration Risk OS
This is the operating-system spec behind SEOParity migration work. It defines the modules, data fields, outputs, and launch checks needed to keep a rebuild from becoming a search-visibility regression.
1. Baseline
Old-site URL and signal inventory
GSC pages, GA4 landing pages, old sitemap, crawl export, backlinks, priority templates.
2. Parity Map
Old-to-new issue map
Redirect, canonical, metadata, schema, sitemap, internal-link, and tracking parity fields.
3. Launch QA
Fix queue before recrawl
HTTP status, final target, live canonical, noindex/robots, schema, speed, analytics event proof.
4. Recovery Monitor
30-day evidence log
GSC deltas, URL Inspection samples, sitemap reads, crawl stats, GA4 leads, and escalation thresholds.
Modules
The OS is not another generic audit checklist. Each module has a concrete input, a failure mode, and a public SEOParity asset that demonstrates the workflow.
| Module | Input and decision | Public asset |
|---|---|---|
| URL inventory | Old URLs, new URLs, GSC clicks, backlinks, status, template, and priority. | Redirect map template |
| Redirect QA | Expected status, first hop, chain count, final target, homepage fallback, and target status. | Redirect map checker |
| Canonical parity | Declared canonical, Google-selected canonical, sitemap URL, internal-link target, and redirect target. | Canonical checker and worksheet |
| Sitemap parity | Indexable 200 URLs only, current lastmod policy, submitted sitemap state, and discovered URL gaps. | Migration checklist |
| Schema parity | Visible page facts, JSON-LD type, author/entity IDs, rich-result eligibility, and unsupported markup. | Schema parity guide |
| Performance regression | LCP, INP, CLS, TTFB, render path, third-party scripts, and field-data caveats. | Speed test and RUM |
| Post-launch monitoring | GSC pages, queries, countries/devices, crawl stats, manual actions, GA4 events, and lead flow. | 30-day GSC runbook |
| Catalog risk | Products, categories, filters, stock states, CMS collections, duplicate routes, and sitemap splitting. | Catalog audit scope |
Minimum data model
A migration risk system fails if it only stores page titles and status codes. The useful unit is a URL-level record that ties search value, launch behavior, and recrawl action together.
| Field | Meaning | Example |
|---|---|---|
| url | Canonical production URL | https://example.com/services/a |
| old_url | Old source URL when the page moved | https://old.example.com/service-a |
| template | Page family or route pattern | service detail |
| gsc_clicks_90d | Clicks before launch | 184 |
| redirect_status | Expected and observed redirect result | 301 to final URL |
| declared_canonical | Canonical in rendered HTML | self |
| sitemap_state | Included, omitted, stale, redirected, or noindexed | included |
| issue_severity | P0, P1, P2, or monitor | P0 |