Site Migration QA: Redirects, Parity + Traffic Alerts

Unlike free "check my redirects" prompts, which guess, this pack scores the statuses and hop counts your crawler actually recorded with a bundled script (migration_qa.py, stdlib Python, offline), so every PASS, FAIL and LONG CHAIN comes from real data.

Sample run (real data, 22 Oct 2026): 9 well-known retired URLs, live statuses and hops fetched with curl, then scored by the bundled migration_qa.py:

1. 5 of 9 redirects PASS: one 301 hop to the right page (e.g. google.com/analytics/ to marketingplatform.google.com/about/analytics/, hubspot "what-is-seo" to /marketing/seo)
2. 4 of 9 FAIL with "Bad match type": the final URL is not the expected page
3. google.com/webmasters/tools/ answers 302 (temporary), then takes 3 hops to search-console/about?hl=en: FAIL + LONG CHAIN
4. twitter.com/home takes 2 hops and lands on a login wall, not x.com/home: SHORTEN
5. support.google.com/webmasters/answer/93633 takes 2 hops and adds a tracking query string: SHORTEN
6. atlassian.com/software/bitbucket returns 200 with no redirect at all (old page still live)
7. searchenginejournal.com/seo-guide/ redirects correctly but the target returned 403 to our test client: FIX STATUS (re-check with your crawler's user agent) Summary line from the script: 18 rows, PASS=5, OK=5, FAIL=4, SHORTEN=2, FIX STATUS=1, LONG CHAIN=1. Expected targets were set by us for the test.

What it does

• Scores old-to-new redirect rows: match OK, status OK, PASS or FAIL plus the top issue
• Flags chains and loops as LOOP, LONG CHAIN, SHORTEN, FIX STATUS or OK
• Scores content parity 0-100 (title, H1, canonical, hreflang, schema) as STRONG, FIX or REWORK
• Ranks launch fixes, and includes a QA checklist, report template and an empty Sheets workbook for launch QA and traffic alerts

Use cases

• Pre-cutover redirect and parity QA
• First two weeks after launch triage
• Agency migration checklists with honest alert flags

Works in Claude Code, Cursor and Codex · stdlib Python, offline, no API keys · HTTP codes and traffic are never invented · questions answered within 24h Need the redirect map built first? Plan it with the skill below, then QA it here. More tools: github.com/cygnixlabs-cmd · Apify actors: apify.com/cygnix_labs

Pairs well with (Cygnix Labs, on Agensi):

• Plan 301 Redirects for a Site Migration Without Losing SEO: build the map and server rules (agensi.io/skills/plan-301-redirects-for-a-site-migration-without-losing-seo)
• Migrate Sites Without Losing SEO: Redirect + Parity Audit: 35 prompts and an 8-tab workbook for the full project (agensi.io/skills/migrate-sites-without-losing-seo-redirect-parity-audit)
• Find Orphan Pages and Fix Your Internal Linking: re-link pages the migration left orphaned (agensi.io/skills/find-orphan-pages-and-fix-your-internal-linking)
• Fix Keyword Cannibalization Using Google Search Console: stop old and new pages competing (agensi.io/skills/fix-keyword-cannibalization-using-google-search-console)
• Find Decaying Pages: GSC Triage + Content Refresh Plan: catch traffic drops after cutover (agensi.io/skills/find-decaying-pages-gsc-triage-content-refresh-plan)

Before launch → 301 Planner · After launch → Migration QA · Both + client sign-off → Migration Kit.