ELEVÉA CLOUD — WEBSITE REDESIGN AND MIGRATION CHECKLIST Planning template | 17 November 2026 | https://eleveacloud.com Use this checklist to preserve useful content, URLs, measurement and customer journeys during a redesign. Adapt it to the website and obtain specialist advice where legal, accessibility, security or migration risks require it. 1. RECORD THE BASELINE [ ] Export or crawl every current public URL, including PDFs and important media. [ ] Record page titles, canonical URLs, status codes and indexability signals. [ ] Export current search queries, pages, clicks and impressions for comparison. [ ] Record important enquiries, form completions and other agreed conversions. [ ] Measure important templates on representative mobile and desktop devices. 2. DECIDE WHAT HAPPENS TO EACH URL [ ] Keep the URL when the topic and purpose remain substantially the same. [ ] Map every changed useful URL to its closest relevant replacement. [ ] Return a genuine 404 or 410 when removed content has no replacement. [ ] Avoid redirect chains and unrelated redirects to the homepage. [ ] Preserve approved downloads or replace their links and destinations. 3. PLAN CONTENT AND STRUCTURE [ ] Assign an owner and decision for every existing page: keep, improve, merge or remove. [ ] Give each new page a clear audience, purpose and next action. [ ] Keep important facts and evidence in visible page content. [ ] Create descriptive navigation and contextual internal links. [ ] Review titles, headings, descriptions and social sharing information. 4. BUILD AND PRE-LAUNCH TESTING [ ] Keep preview/staging environments out of public search indexes. [ ] Test navigation, forms, email delivery, phone and contact links. [ ] Test keyboard use, focus visibility, labels, contrast and alternative text. [ ] Test responsive layouts and important journeys on representative devices. [ ] Validate canonical URLs, structured data, robots rules and the XML sitemap. [ ] Prepare analytics with the same agreed conversion definitions. [ ] Back up the current site and document the rollback decision and owner. 5. LAUNCH [ ] Apply the approved one-to-one redirect map. [ ] Remove accidental noindex rules and confirm important pages return HTTP 200. [ ] Publish the canonical sitemap and reference it from robots.txt. [ ] Verify the production domain and HTTPS variants resolve consistently. [ ] Complete real form and contact journeys on production. [ ] Check analytics and Search Console ownership. 6. AFTER LAUNCH [ ] Crawl old URLs and confirm direct redirects or intended removal responses. [ ] Monitor 404s, server errors, redirect loops and blocked resources. [ ] Inspect representative important URLs in Google Search Console. [ ] Compare search and enquiry data over equal complete periods. [ ] Fix internal links that still use redirects. [ ] Keep redirects long enough for users and search systems to process the move. [ ] Record later content or technical changes separately from the launch baseline. REDIRECT WORKSHEET COLUMNS Old URL | Current status | Traffic/evidence | Decision | New URL | Redirect status | Owner | Tested before launch | Tested after launch | Notes NEXT STEP Discuss a website project: https://eleveacloud.com/contact Read the guide: https://eleveacloud.com/guides/website-redesign-checklist Website service: https://eleveacloud.com/services/website-development This template is a planning aid. It does not guarantee rankings, accessibility, security or a risk-free migration.