Concise answer
An SEO-friendly redesign starts before development with a complete URL and content inventory. Every valuable legacy page needs an intentional destination, important content and metadata must be preserved or improved, and redirects, canonicals, internal links, indexability, analytics, and forms need validation before and after launch.
Build an evidence baseline before changing URLs
A crawl shows what exists, but it does not show which pages attract qualified traffic, links, enquiries, or branded demand. Search Console, analytics, backlink data, paid-search queries, and sales feedback help identify what must be protected.
Without that baseline, teams can accidentally remove a modest-looking page that performs an important acquisition or navigation role.
Export the baseline before design work begins and store it where the whole team can reach it. It becomes the reference point for every later decision, and it is the only reliable way to judge whether the new website performs better or worse after launch.
- A full crawl of the current website, including status codes, canonicals, titles, descriptions, and headings.
- Search Console page and query data covering at least the last twelve months.
- Analytics landing-page data with enquiries, conversions, or revenue attached.
- Backlink data showing which URLs other websites link to.
- Current XML sitemaps, robots rules, and any existing redirect rules.
- A list of forms, tracking tags, and third-party scripts that must keep working.
Decide what each existing page should become
A redesign is a good moment to improve content, but every change should be deliberate. Once the inventory exists, give each URL a decision and a reason. That turns a vague goal such as tidying up the website into a list the team can review, challenge, and approve.
Pages with strong links or steady traffic deserve extra caution. If the new information architecture has no natural home for them, it is usually better to adjust the architecture than to lose the page.
- Keep: the page performs well and its purpose still matters. Move it across carefully and improve it where that helps.
- Improve: the topic is valuable but the page is thin, outdated, or hard to use. Rewrite it before launch rather than promising to fix it later.
- Merge: two or more pages answer the same question. Combine them into one stronger page and redirect the others to it.
- Retire: the page has no traffic, links, or business purpose. Remove it and decide whether it should redirect or return a 404 or 410.
Give every legacy URL an intentional outcome
A redirect map should connect each old URL to the closest useful new destination. Redirecting every removed page to the homepage weakens relevance and creates a poor user experience.
Remember the variants. HTTP and HTTPS, www and non-www, trailing slashes, uppercase paths, and old file extensions such as .php or .aspx should all resolve to the same preferred URL in a single step.
Test the redirect map before launch, not after it. Run the full list of old URLs against the staging environment and confirm each one returns a single permanent redirect to a live page. Keep the map as a maintained file afterwards, because later changes to the new website can quietly break redirects that worked on launch day.
- Keep high-value pages when their intent remains useful.
- Consolidate overlapping content only when the destination fully answers the old intent.
- Use one-hop permanent redirects and avoid chains.
- Preserve useful query parameters and remove obsolete tracking carefully.
Carry content, metadata, and structured data across
Rankings are tied to what a page says, not only to its URL. A common migration loss happens when a redesign keeps the URL but replaces detailed copy with shorter marketing text, removes headings that matched real queries, or drops FAQ content because it did not fit the new layout.
Before launch, compare each important page on the old and new websites side by side. Check that the main topic, supporting detail, headings, internal links, images, and structured data still exist or have been improved. Titles and meta descriptions should be reviewed page by page rather than regenerated from a template.
- One clear H1 that describes the topic of the page.
- Unique titles and descriptions of a sensible length.
- Structured data such as Organization, Service, Article, BreadcrumbList, and FAQPage where it reflects visible content.
- Open Graph and social sharing tags that point to production URLs.
- Image file names and alt text that describe what the image shows.
Validate the technical signals as one system
Canonical URLs, sitemap entries, internal links, structured data, Open Graph URLs, robots directives, status codes, and redirects should all point to the same preferred production URLs.
Preview deployments should be excluded from indexing without accidentally blocking production. Sitemap modification dates should reflect actual content changes rather than the latest build time.
Run these checks on staging, then repeat them on production immediately after launch. The production check matters most: a robots rule or noindex tag carried over from staging can remove an entire website from search results, and it is one of the most common causes of traffic loss after a launch.
Measure performance on the key templates at the same time. A redesign that adds heavy scripts, large images, or layout shifts can undo the benefit of better content, so Core Web Vitals should be checked before launch rather than discovered later in Search Console.
Plan the launch window
Choose a launch time when the team can watch the website closely for the following days, and avoid periods with major campaigns or seasonal peaks. Agree in advance who checks what, and how a rollback would work if something serious goes wrong.
- Remove staging restrictions and confirm robots.txt and meta robots allow indexing.
- Deploy the redirect rules and test a sample of high-value old URLs.
- Submit the new XML sitemap in Google Search Console and Bing Webmaster Tools.
- Use the Change of Address tool in Search Console if the domain itself is changing.
- Confirm that analytics, conversion tracking, and forms are recording correctly.
- Request indexing for the homepage and the most important pages.
Monitor the migration after launch
A successful deployment is not proof of a successful migration. Teams should monitor redirect hits, unexpected 404s, crawl behaviour, canonical selection, index coverage, rankings, conversions, and form delivery during the stabilisation period.
In the first few days, focus on errors: broken redirects, redirect loops, failed forms, and missing tracking. Over the following weeks, compare impressions, clicks, and conversions for important pages against the baseline. Some short-term fluctuation is normal while search engines recrawl the website; a sustained drop on specific pages usually points to a specific cause that can be investigated.
No migration can guarantee unchanged rankings. The objective is to reduce avoidable loss, preserve intent, and respond quickly when real data shows a problem.
Common migration mistakes to avoid
Most migration problems are preventable with a complete inventory, a reviewed redirect map, and disciplined checks before and after launch. These are the issues we look for first when reviewing a redesign plan.
- Launching with the staging noindex tag or robots rule still active.
- Redirecting every old URL to the homepage.
- Leaving redirect chains from earlier migrations in place.
- Replacing detailed page content with shorter design copy.
- Changing URLs that did not need to change.
- Forgetting images, PDFs, and other files that attract links or traffic.
- Losing analytics continuity because tracking was not migrated and tested.
Frequently asked questions
Will a website redesign affect my Google rankings?
It can. Rankings may change when URLs, content, internal links, or technical signals change. Careful planning reduces avoidable loss: keep valuable pages, redirect every changed URL to its closest equivalent, preserve useful content and metadata, and monitor performance after launch. No redesign can guarantee unchanged rankings, but most serious losses come from preventable mistakes.
Should I change my URLs during a redesign?
Only when there is a clear reason, such as a confusing structure, outdated platform paths, or a new information architecture that genuinely serves users better. Every changed URL adds redirect work and some risk, so keeping existing URLs where they still make sense is usually the safer choice.
Should I use 301 or 302 redirects for a website migration?
Use permanent redirects, such as 301 or 308, for pages that have moved for good. They tell search engines to consolidate signals on the new URL. Temporary 302 redirects are meant for short-term moves and should not be used for a permanent migration.
How long should redirects stay in place after a migration?
Keep them for as long as possible, ideally permanently. Old URLs can remain in bookmarks, emails, documents, and links on other websites for years, and removing redirects early sends those visitors and signals to error pages.
How long does search performance take to settle after a migration?
It depends on the size of the website, how often it is crawled, and how much has changed. Smaller websites often settle within a few weeks, while larger or more complex migrations can take longer. Watching Search Console, analytics, and crawl errors during this period helps separate normal fluctuation from real problems.
What should I check immediately after launching a redesigned website?
Confirm that robots.txt and meta robots allow indexing, that a sample of old URLs redirects correctly, that the XML sitemap lists the new URLs and has been submitted, that forms and analytics work, and that key pages return a 200 status with the correct canonical tag.

