How to Do a Bulk 404 Check Before a Site Migration

Website migrations—whether migrating to a new domain, switching CMS platforms (e.g., WordPress to Shopify), or re-architecting URL structures—are among the highest-risk projects in technical SEO. As emphasized in Google Search Central's Site Move Guide, when URLs change without proper 301 redirects, search engine bots encounter 404 Not Found errors, link equity evaporates, and organic rankings collapse.

The single most important safeguard during any migration is a rigorous bulk 404 check before and immediately after launch. In this guide, we provide a complete step-by-step audit framework to ensure zero traffic loss.

Why 404 Errors Destroy SEO Traffic

Every established page on your website carries historical value in Google's index: internal link weight, external backlink equity (PageRank), and user engagement history. When a page returns an unhandled 404 status code:

• Google removes the page from search results after several crawl attempts.
• All inbound backlinks pointing to that broken URL lose 100% of their PageRank equity.
• Users clicking search links or social shares hit dead ends, causing bounce rates to skyrocket.

The Hidden Threat: Beware of "Soft 404s"

A standard 404 error occurs when your web server correctly returns the HTTP status code 404 Not Found or 410 Gone.

A Soft 404, however, is much more deceptive: the server responds with a 200 OK status code, but the webpage content clearly states "Page Not Found", displays a blank screen, or redirects users to an unrelated homepage.

Google hates Soft 404s because they waste crawler resources. Googlebot will often treat deceptive 200 OK pages as 404s, leading to unexpected index drops.

Pre-Migration 404 Audit Checklist

Step 1: Compile Your Master URL List

Never rely on a single source. Combine exports from:

1. Google Search Console: Export all indexed pages from the "Pages" report.
2. XML Sitemaps: Scrape all active URLs from your live sitemap.xml files.
3. Analytics Tools: Export all URLs that received at least 1 organic session in the past 12 months.
4. Backlink Audits: Export all URLs receiving external backlinks via tools like Ahrefs, Semrush, or Moz.

Step 2: Build Your 301 Redirect Mapping Spreadsheet

Map every legacy URL to its exact 1:1 equivalent on the new architecture:

• Old URL: /services/seo-auditing → New URL: /seo-audit-services
• Avoid redirecting everything to the homepage: Google treats mass homepage redirects as Soft 404s and strips historical link equity.

Step 3: Run a Bulk HTTP Status Check in Staging

Before pointing DNS to production, test every redirect rule using our Bulk HTTP Status Checker:

1. Upload your batch of legacy URLs into the tester.
2. Verify that each URL returns a clean 301 Moved Permanently.
3. Inspect redirect chains: ensure URL A does not bounce to URL B, then URL C before settling on URL D. Every hop in a redirect chain degrades crawl budget and dilutes PageRank.

Post-Launch Verification

Within 24 hours of going live on production, execute these three validation steps:

1. Re-run Bulk Status Scan: Confirm that legacy URLs resolve cleanly to their target destinations without throwing 404 or 500 errors.
2. Inspect Canonical Tags: Ensure new URLs point canonical references to themselves and not to legacy staging domains.
3. Verify Live Indexation: Use our Google Index Checker to track how rapidly Google indexes the new URLs and retires old slugs.

By automating your 404 detection, you turn what is typically a nerve-wracking site migration into a predictable, error-free deployment.