A redesign is a chance to make your website clearer, faster and easier to maintain. It can also change the URLs and content that customers and search engines already use to find you.
Before choosing a new layout, make a plan for the information that matters. A migration checklist helps preserve the useful parts of the existing site while giving the new one room to improve.
Inventory what already brings people in
List your current public URLs. Use the sitemap, site navigation, available analytics and Search Console data to identify important landing pages. Include pages with valuable inquiries, relevant search visibility, external links or essential business information.
Do not evaluate pages only by raw traffic. A specialist service page may have fewer visits than a broad article but attract a more relevant audience. Record the page’s purpose and the visitor question it answers.
Capture current titles, descriptions, canonical URLs and indexing directives for representative templates. Keep a baseline that you can compare against the redesigned site.
Give each old URL an intentional destination
When a URL changes, map it to the closest relevant new page. Sending every removed page to the homepage ignores what the visitor was looking for.
Google’s site migration guidance recommends mapping old URLs to new destinations and using permanent server-side redirects when moving URLs. Keep the route direct where possible and update internal links to point to the final address. Google also recommends keeping redirects for at least a year.
If there is no suitable replacement, use an appropriate missing-page response rather than pretending unrelated content is the same resource. Preserve a useful error page with navigation so a person who follows an old link can recover.
Keep answers while improving the structure
A simpler design should still answer the questions that made a page useful. If you merge several service pages, check that the resulting page explains the distinct offerings clearly. If you remove an article, decide whether its information is outdated, duplicated or still needed.
Use descriptive headings and links that make sense in context. Write accurate titles and descriptions for the actual page content. Metadata supports how a page is understood and presented; it cannot compensate for a page that no longer answers the visitor’s question.
Google’s SEO starter guide provides a foundation for clear organization and understandable content. Apply it to the pages people need, rather than adding words solely to reach a target length.
Check what the deployed site actually serves
Preview environments and production environments can have different configuration. Before launch, verify the final hostname, status codes and rendered public content. Check that canonical URLs point to the intended live pages and that the sitemap lists the right addresses.
A staging noindex directive can accidentally remain on production. Conversely, a staging site may be exposed earlier than intended. Include indexing configuration in the release checklist rather than assuming it follows automatically from the design.
For applications with public and private pages, make the distinction explicit. Public service content should be accessible as intended; customer dashboards need appropriate access controls. Indexing directives are not a substitute for protecting private data.
Rehearse the important paths
Test a sample of old URLs before switching over: a service page, an article, a changed category and a deleted page. Check the response and destination for each. Include query strings where they have a real role in the user journey.
Then test the business journey on the new site. Can someone understand the offer, find supporting work and send an inquiry? A migration that preserves redirects but breaks the contact form has missed an essential part of the launch.
Keep a recovery plan and identify who can change deployment and routing configuration. If a release causes a serious problem, the team should know which changes can be rolled back and which data changes need separate handling.
Monitor after launch
Track important landing pages, unexpected missing-page requests, inquiry completion and search reports. Search engines need time to process changes, and visibility can fluctuate during a migration. Review patterns before attributing every movement to one design decision.
Separate an implementation fault from a broader search outcome. An incorrect redirect or indexing directive can be checked directly. A ranking change may involve several factors and needs more evidence.
Your redesign handover checklist
- A URL inventory and a reviewed redirect map.
- Relevant content preserved or intentionally replaced.
- Verified production canonicals, sitemap and indexing configuration.
- Working navigation, forms and key customer journeys.
- A performance baseline for representative page templates.
- Named owners for monitoring, fixes and recovery.
A careful launch connects the old site’s useful history with the new site’s improvements. That planning is part of web development, alongside the interface and code.
Plan your redesign before rebuilding
If you are considering a redesign, send me your current URL, the pages most important to your business and what you want the new site to improve. We can discuss a technical SEO and performance scope that includes the migration, rather than leaving it until launch day.