Auditing URL Inventories Before and After a Migration

Guide · Published July 16, 2026

A URL inventory comparison shows which crawlable pages survived a redesign, platform move, domain change, or information-architecture update. Compare normalized URL keys, investigate both directional differences, and validate redirects and page status separately before launch.

Build two clearly defined URL inventories

List 1 should represent the old site population you intend to preserve or redirect. Combine sources such as XML sitemaps, a complete crawl, analytics landing pages, backlink exports, and known campaign URLs. List 2 should represent the expected new URLs from the staging or production crawl. Label and date both files.

Normalize URLs without erasing meaning

Decide whether to compare full URLs or paths. For a domain migration, comparing paths often reveals structural changes more clearly. Normalize protocol, hostname case, default ports, fragments, and consistent trailing-slash rules. Do not remove query parameters blindly; some parameters identify indexable content while others are only tracking values.

What each result means in a migration

• Old only: pages that need a mapped replacement, intentional retirement, or further investigation.
• New only: newly created pages, changed paths, or unexpected crawl discoveries.
• Intersection: URLs retained exactly after normalization.
• Union: the full URL population observed across both versions.
• Symmetric difference: the migration’s total structural change set.

A list diff does not validate redirects

URL presence is only the first control. For every old-only URL, verify the destination, HTTP status, redirect chain length, canonical target, indexability, internal links, and content relevance. A one-to-one redirect to the closest equivalent page is usually more useful than sending many unrelated URLs to the homepage.

Pre-launch URL comparison checklist

1. Collect old URLs from more than one source.
2. Crawl the new environment using the intended indexability rules.
3. Normalize both lists with one documented URL policy.
4. Review old-only and new-only groups with page owners.
5. Test redirect mappings and final status codes.
6. Update internal links, canonicals, hreflang, and XML sitemaps.
7. Repeat the comparison immediately after launch and during monitoring.

Use the comparison as an audit trail

Export the exception sets and record why each URL changed. The final report should distinguish intentional removals, merged pages, renamed paths, new pages, and defects. That context helps developers, content owners, and SEO teams resolve issues without debating which inventory is current.