A redesign is a migration project, even when the new design looks completely different. The highest-risk failures usually happen behind the scenes: vanished URLs, lost analytics, broken forms, missing media, outdated hours and a domain account nobody can access.
Before anyone designs a page
Export the current sitemap and crawl the old site. Record live URLs, important downloads, current metadata, canonical destinations, conversion pages, forms, integrations and pages that earn organic impressions. Save a copy of the current analytics and Search Console performance if you control those accounts.
Interview the staff who maintain the site. An elegant design will fail in practice if a busy office cannot edit opening hours, change season dates or publish urgent notices.
- Old URL inventory and page-to-page redirect map
- Content ownership and image rights audit
- Existing form destinations and leads workflow
- Search Console and analytics access
- DNS, registrar, hosting and SSL ownership
During the build
Build important page templates and navigation before bulk migration. Decide which content is kept, combined, rewritten or retired, and record the destination for every significant old URL. Preserve useful headings and context where they serve the same search intent.
Test staging with real phone sizes and keyboard navigation. Stage sites should not accidentally replace the production canonical in search results.
- Content matrix with owner and review status
- Stable, descriptive URLs and internal links
- Alt text and semantic headings
- Forms tested with real confirmation and error paths
- Noindex or access control on preview as appropriate
At launch
For changed URLs, configure permanent server-side redirects from old to equivalent new pages. Point canonical tags and XML sitemaps at the final URLs. Verify that robots directives allow crawling of pages intended to rank.
Check the site from outside the hosting dashboard: an actual contact form submission, mobile menu, telephone links, booking path, 404 behavior, social sharing preview, sitemap and the home page under a cold cache.
- 301 redirects validated with a representative URL list
- Live robots.txt, sitemap and canonical checks
- Analytics and Search Console reverified
- Production form notifications tested
- Rollback contacts and incident owner documented
First 30 days
Search engines need time to recrawl and process changed URLs. Use Search Console to inspect unexpected indexing drops and crawl errors; do not treat a short-term fluctuation as proof of failure. Measure conversions too, since organic ranking alone is not the business goal.
Retain old URL maps and launch logs. If a key page was forgotten, you want to correct the redirect promptly rather than reverse-engineer the old site later.
Sources and further reading
We link directly to relevant primary documentation. Company prices, public services, standards and guidance may change; verify before making purchasing or compliance decisions.
Editorial disclosure
Alaska Web Company is operated by FOUR Media Group LLC. FOURAK is the operator's own brand and Martin Media is a professional partner. Editorial guidance is not an independent agency ranking, a legal opinion or an individualized quote. Read our methodology.