A website migration can preserve organic visibility, campaign attribution, and valuable short links—but only when every important URL has a documented destination and a tested redirect. This reusable website migration link mapping checklist shows how to build a URL inventory, choose redirect rules, preserve query strings and UTMs, test the staging site, and validate the launch.
Overview
Website migrations include more than moving page content. A domain change, CMS rebuild, URL structure update, rebrand, or site consolidation can affect organic landing pages, backlinks, bookmarked URLs, paid campaigns, email links, QR codes, and branded short links. Treating the migration as a link-management project helps prevent avoidable broken journeys and unclear attribution.
The central document is a URL-to-destination mapping table. It should record the old URL, its intended new URL, the redirect status, page purpose, traffic or backlink importance, query-string behavior, and testing result. Build the inventory from several sources rather than relying on a single crawl:
- Crawl the current site, including important HTML pages, image URLs, downloadable files, and canonical URLs.
- Export URLs from analytics, search reporting, server logs, the XML sitemap, and your CMS.
- Collect URLs from paid media, email templates, partner placements, social profiles, QR codes, and printed materials.
- Export short links from your link management platform and identify their current destinations.
- Ask teams responsible for sales, support, events, and campaigns for links that may not appear in a site crawl.
Prioritize pages with organic visits, external backlinks, conversions, active campaigns, or strong brand recognition. A low-traffic URL can still matter if it is printed on packaging or embedded in a long-running presentation.
Reusable URL redirect mapping template
| Old URL | New URL | Action | Query strings | Owner | QA result |
|---|---|---|---|---|---|
| https://old.example.com/guide | https://new.example.com/resources/guide | Permanent redirect | Retain unless replaced | SEO | Pending |
| https://old.example.com/offer | https://new.example.com/offers/current | Redirect or campaign update | Test UTMs | Marketing | Pending |
| https://old.example.com/retired-page | None | 410 or relevant alternative | Not applicable | Content | Pending |
Use one canonical format for the inventory. Decide how to represent protocol, host, trailing slashes, capitalization, fragments, and encoded characters before comparing lists. This avoids treating minor formatting differences as separate URLs.
Checklist by scenario
1. Domain change or rebrand
- List every important URL on the old domain and match it to the closest equivalent on the new domain.
- Redirect old URLs directly to their final destinations; avoid sending them through several intermediate URLs.
- Keep the old domain registered and controlled for as long as needed to support existing links, redirects, and brand references.
- Update internal links, canonicals, hreflang where applicable, XML sitemaps, structured data references, and social profile links.
- Notify owners of high-value backlinks and partner links when a direct update is practical.
- Check branded short links separately. Their destination may need updating in the short-link platform rather than at the web server.
2. CMS, platform, or URL structure change
- Compare the old crawl with the staging crawl and classify every missing URL.
- Map changed paths by page intent, not just by similar words in the URL.
- Preserve useful page content and metadata where the page’s purpose remains the same.
- Review media, PDF, feed, API, and search-result URLs if they are linked externally or used operationally.
- Confirm that the new platform does not automatically append, remove, or rewrite query parameters.
3. Campaign URL migration
- Inventory active paid, email, affiliate, social, QR, and partner URLs.
- Keep campaign parameters intact when the destination changes, unless the tracking plan has deliberately been revised.
- Use consistent lowercase naming and documented values for source, medium, campaign, content, and term fields.
- Update ad, email, automation, and QR-code source files rather than depending only on a redirect.
- Test that the final analytics landing page records the intended campaign information without exposing malformed or duplicated parameters.
For platform-specific parameter conventions, use a documented governance process such as the UTM parameters by ad platform guide. A preflight review can also catch destination, redirect, and tracking errors before campaign launch; see the marketing link preflight checklist.
4. Short links and QR codes
- Export each short code, current destination, owner, campaign, expiration setting, and usage location.
- Choose whether to preserve the existing short link, create a replacement, or archive it after a controlled transition.
- Test the short link on mobile and desktop, with and without tracking parameters where relevant.
- For printed QR codes, verify that the code still resolves to the intended short link and that the destination works on mobile networks.
- Do not retire a short link merely because the original campaign has ended if it appears on permanent material without a replacement plan.
The short link lifecycle guide can help document ownership and archive decisions. For newly printed materials, also review the QR code print quality guide.
What to double-check
Redirect behavior
Test representative URLs from every rule group, including uppercase variants, trailing-slash variants, legacy paths, files, and URLs with query strings. Confirm the response status, final destination, redirect count, and whether the browser receives the expected parameters. A redirect should lead to a relevant final page, not simply the new home page.
Canonical and indexability signals
On the new site, verify that canonical URLs use the preferred protocol and hostname, point to live pages, and are not accidentally left on staging addresses. Check that important pages are not blocked by robots directives, noindex settings, login requirements, or accidental password protection. Make sure the XML sitemap contains the new canonical URLs rather than the old locations.
Internal and external link paths
Crawl the new site for links that still reference the old domain, redirecting URLs, broken destinations, or inconsistent hostname formats. Review navigation, footer links, structured data, downloadable files, and templates separately. External backlinks cannot always be changed, so the redirect map must remain reliable for those referrals.
Analytics and attribution
Open representative campaign URLs and follow them through the entire redirect chain. Confirm that UTMs survive when they should, that analytics tags load on the final page, and that consent or privacy controls do not create a misleading testing result. Compare link clicks, sessions, conversions, and landing-page data after launch, while accounting for normal reporting delays and differences between tools. For ongoing review, use a documented marketing link governance audit.
Common mistakes
- Mapping every old URL to the homepage: this loses page context and creates a poor experience. Map to the closest relevant replacement or make a deliberate retirement decision.
- Relying only on the current sitemap: sitemaps omit historical, campaign, and externally shared URLs. Combine crawl, analytics, backlink, server, and campaign data.
- Testing only the homepage: sample every redirect pattern, template, language version, file type, and query-string rule.
- Breaking UTMs during redirects: test complete campaign URLs, not just clean page paths.
- Creating redirect chains: point legacy URLs directly to final destinations where possible.
- Deleting the old domain too soon: preserve control of it while old links, campaign materials, and redirects still matter.
- Ignoring short links: a migration can leave a branded link technically active but pointed at an obsolete page. Export and test the short-link inventory separately.
- Failing to assign owners: every unresolved mapping, campaign, and retired page should have a named decision-maker and due date.
After launch, automated checks can reduce manual effort. A scheduled health-check workflow can monitor redirect failures and alert the responsible team; see URL shortener API automation. For large campaigns, maintain an import and QA process using a bulk short link generator workflow.
When to revisit
Rebuild or refresh the inventory before every domain change, rebrand, CMS migration, URL restructuring, or major seasonal campaign. Recheck it when a short-link provider, analytics setup, hosting environment, or redirect configuration changes. A practical cadence is to review high-value redirects and active campaign links monthly, then run a broader crawl and mapping audit before planned migration work.
At launch, assign one person to monitor errors, redirect logs, analytics, and search landing pages. Check immediately after release, again after the first reporting cycle, and once more after campaign traffic reaches normal volume. Record every correction in the mapping table so it becomes the next migration’s starting inventory.
Final action list: freeze the old URL inventory, approve the mapping, test staging rules, update owned campaign links, deploy redirects, crawl the live site, verify UTMs and canonicals, monitor errors, and archive the final results. Revisit the checklist whenever the underlying domains, tools, campaigns, or URL rules change.