Quick answer
A safe website redesign has four stages. Benchmark current traffic, rankings, and conversions. Plan the new structure and map every old URL to its new one. Build and test on a blocked staging site, keeping content that ranks. At launch, add 301 redirects, unblock indexing, submit the sitemap, and monitor Search Console and conversions daily for several weeks.
- Most traffic losses after a redesign come from missing redirects and lost content.
- Never launch with a staging noindex or robots.txt block still in place.
- Keep tracking working from the first minute after launch.
- Expect some ranking movement while Google processes the change.
What should you do before a website redesign?
- Export traffic, top landing pages, and conversions from analytics
- Export queries, pages, and links from Google Search Console
- Crawl the current site to list every URL, title, and status code
- Note pages with backlinks and pages that bring leads
- Record current Core Web Vitals and speed
- Agree goals for the new site and how they will be measured
How do you plan the new site structure?
- Keep what works. Pages that rank or convert keep their content and, ideally, their URL.
- Map every URL. A spreadsheet of each old URL and its closest new equivalent. Remove only what has no value.
- Plan redirects. One 301 per changed URL, straight to the final page, with no chains.
- Plan metadata. Titles, descriptions, headings, and structured data for each template.
- Plan tracking. Analytics, tag manager, conversion events, and call and form tracking.
What should be tested before launch?
- Staging site blocked from indexing and protected by a password
- All mapped content present, including FAQs and copy that ranked
- Internal links point to new URLs, not through redirects
- Forms, calls, WhatsApp links, and tracking fire correctly
- Speed and Core Web Vitals on mobile
- Accessibility checks against WCAG 2.2 AA
- Canonical tags, hreflang, and structured data on every template
What is on the launch day checklist?
- Remove staging noindex tags and robots.txt blocks
- Deploy and test 301 redirects for every mapped URL
- Submit the new XML sitemap in Search Console
- Use the Change of Address tool only if the domain itself changes
- Check key pages with URL Inspection
- Confirm analytics and conversion tracking are recording
What should you monitor after a relaunch?
- Search Console Page indexing and crawl errors, daily at first
- 404 errors and missing redirects, fixed as found
- Rankings and clicks for top queries against the benchmark
- Leads and sales against the benchmark
- Speed and Core Web Vitals in field data
Google documents how to move a site with URL changes; the guide is linked below.
Website redesigns by Hudace
Hudace runs website development and SEO in one team, so every redesign includes a URL map, redirect plan, tracking plan, and post-launch monitoring. We also offer website migration SEO for platform and domain changes. Talk to us.
Frequently asked questions
Will a website redesign hurt SEO?
It can if URLs change without redirects, ranking content is removed, or indexing is blocked. A URL map, 301 redirects, and careful launch checks protect rankings.
How long does it take Google to process a redesign?
It varies with site size and crawl frequency. Expect some movement for a few weeks and monitor Search Console closely.
Should we keep the same URLs when redesigning?
Where possible, yes. Keeping URLs avoids redirects altogether. Change them only when the new structure is clearly better.
What is a 301 redirect?
A permanent redirect that sends users and search engines from an old URL to its new location and signals that the move is permanent.
Do we need to tell Google about a redesign?
Submit the new sitemap and inspect key pages. Use the Change of Address tool only if the domain changes.
How often should a website be redesigned?
When it no longer serves your goals, brand, or technology needs. Many sites benefit more from continuous improvement than from frequent full redesigns.