A new website should bring in more business, not wipe out the search traffic you spent years earning. Website redesign SEO is the process of protecting your rankings while you change design, content, URLs or platform, and most of the risk is avoidable with planning. This checklist walks you through four phases (before, during, launch and after) with a sample 301 redirect map, a QA list and a post-launch monitoring plan.
Quick answer: To redesign a website without losing SEO, benchmark current traffic, crawl every existing URL, keep or improve content on valuable pages, and map each changed URL to its closest new equivalent with a 301 redirect. Test everything on a protected staging site, then monitor Search Console closely for several weeks after launch.
On this page
- Key takeaways
- What is a website redesign SEO checklist?
- What are the biggest SEO risks in a website redesign?
- Phase 1: Before the redesign
- Example 301 redirect map
- Phase 2: During the build
- SEO QA list: test these before go-live
- Phase 3: Launch day
- Phase 4: After launch, monitoring and fixes
- Frequently asked questions
- Next steps
Key takeaways
- Most ranking losses after a redesign come from missing redirects, removed content, accidental noindex tags and broken internal links, not from the new design itself.
- Benchmark before you touch anything. Without a baseline, you cannot tell a normal dip from a real problem.
- Build a page-by-page 301 redirect map before development starts, and send each old URL to its most relevant new page rather than the homepage.
- Keep the staging site out of search with password protection, then remove every block on launch day.
- Google Search Central advises keeping redirects in place for as long as possible, generally at least one year.
- Expect some temporary fluctuation. Google notes that visibility can fluctuate during a move and that most pages on a small to medium site can take a few weeks to move.
What is a website redesign SEO checklist?
A website redesign SEO checklist is a step-by-step list of tasks that preserve search visibility when a site changes. It matters because search engines rank individual URLs, and each URL carries history: links from other sites, accumulated relevance and user signals. Change or remove that URL carelessly and the history can be lost.
Not every redesign carries the same risk. Use this table to understand where your project sits.
| Type of change | Example | SEO risk level |
|---|---|---|
| Visual refresh only | New colors, fonts and layout; same URLs and content | Low |
| Content and structure changes | Pages merged, rewritten or removed; new navigation | Medium |
| URL changes on the same domain | /services.php?id=4 becomes /services/roof-repair/ | High |
| Platform migration | Moving from one CMS or e-commerce platform to another | High |
| Domain change | Moving from oldbrand.com to newbrand.com | Highest |
Many projects combine several of these. A rebrand with a new platform, new structure and new domain stacks every risk at once, so it deserves the most careful planning. If you are still choosing a platform, our guide to Webflow vs WordPress vs custom code explains how each one handles redirects and URL control.
What are the biggest SEO risks in a website redesign?
The biggest SEO risks in a redesign are losing URLs without redirects, removing content that earned rankings, and launching technical blocks that stop Google from indexing the new site. Here is what typically goes wrong and how to prevent it.
| Risk | What happens | How to prevent it |
|---|---|---|
| Missing redirects | Old URLs return 404 errors, and their link value and rankings are lost | Build and test a full redirect map |
| Redirecting everything to the homepage | Google may treat irrelevant redirects like soft 404s | Map each URL to its closest equivalent |
| Removed or thinned content | Pages lose the text that made them rank | Keep or improve content on valuable pages |
| Staging blocks left in place | Noindex tags or robots.txt rules hide the new site | Launch-day checklist to remove all blocks |
| Changed titles and headings | Pages lose relevance for their main keywords | Carry over or deliberately improve on-page elements |
| Broken internal links | Crawlers and users hit dead ends | Update links to new URLs, not just redirect them |
| Lost structured data | Rich result eligibility disappears | Recreate markup on new templates |
| Slower pages | Worse user experience and Core Web Vitals | Performance budget and testing before launch |
| Analytics gaps | You cannot measure the impact of launch | Install and test tracking on staging |
Phase 1: Before the redesign
The before phase is where you capture what you have today and decide what the new site must protect. Skipping it is the single most common cause of post-launch traffic loss.
Benchmark current performance
Record a baseline you can compare against after launch. Export at least 12 months of data where possible, so seasonality is visible.
- Export organic sessions and conversions by landing page from your analytics.
- Export queries, pages, clicks, impressions and average position from Search Console.
- Note the number of indexed pages in the Page indexing report.
- Record rankings for your priority keywords.
- Save Core Web Vitals data and a sample of page speed test results.
- Take screenshots of key pages for reference.
Crawl and inventory every URL
Create a complete list of existing URLs from several sources, because no single source catches everything.
- Crawl the live site with an SEO crawler.
- Download URLs from your XML sitemaps.
- Export landing pages from analytics and Search Console.
- Export pages with external backlinks from a backlink tool.
- Include PDFs, images and other files that attract traffic or links.
Identify your most valuable pages
Rank every URL by its traffic, conversions and backlinks. The top pages deserve extra protection: keep their URLs if you can, keep their core content, and test their redirects first.
Decide what to keep, merge or remove
For each URL, choose one action: keep as is, keep and improve, merge into another page, or remove. Removed pages that have traffic or links still need a redirect to the most relevant alternative.
Write SEO requirements into the brief
Make SEO a requirement, not an afterthought. State that the provider must preserve URL structure where possible, implement your redirect map, carry over metadata and structured data, and meet performance targets. Include this work in the project scope and in your rebuild budget, because migration tasks take real time.
Example 301 redirect map
A redirect map is a spreadsheet that pairs every old URL with its new destination and the type of redirect to use. The example below is for a hypothetical home services company moving from an older site structure to a cleaner one.
| Old URL | New URL | Status code | Reason | Priority |
|---|---|---|---|---|
| /index.php | / | 301 | Old homepage address | High |
| /services.php?id=4 | /services/roof-repair/ | 301 | Same service, cleaner URL | High |
| /services.php?id=7 | /services/gutter-cleaning/ | 301 | Same service, cleaner URL | High |
| /about-us.html | /about/ | 301 | Same content, new format | Medium |
| /blog/2019/05/winter-roof-tips | /blog/winter-roof-maintenance/ | 301 | Updated and expanded article | High |
| /blog/2018/02/roof-tips-part-2 | /blog/winter-roof-maintenance/ | 301 | Merged into stronger article | Medium |
| /areas/springfield-roofing.html | /locations/springfield/ | 301 | Location page restructured | High |
| /promo-summer-2023 | /offers/ | 301 | Expired offer, closest relevant page | Low |
| /team/old-employee | /about/ | 301 | Profile removed, team info on About | Low |
| /contact.html | /contact/ | 301 | Same content, new format | High |
Redirect mapping rules
Follow these rules to keep the map clean:
- Use 301 (permanent) redirects for permanent changes. Google Search Central describes permanent server-side redirects as the most reliable way to send people and Google to the new URL.
- Redirect to the closest equivalent. A roof repair page should point to the new roof repair page, not to the homepage.
- Avoid chains. Redirect old URLs straight to the final destination rather than through several hops, including URLs that were already redirected by a previous redesign.
- Handle variations. Include trailing slash, uppercase,
httpandwwwvariations if your old site served them. - Let genuinely dead pages go. A page with no traffic, no links and no equivalent can return a 404 or 410. That is normal and healthy.
- Keep redirects in place long term. Google Search Central recommends keeping redirects for as long as possible, generally at least one year. Many teams simply keep them permanently.
Phase 2: During the build
The during phase is about building SEO into the new site on staging, where mistakes are cheap to fix. Treat the staging site as a rehearsal for launch.
- Protect staging with a password. Password protection is a more reliable way to keep a test site out of search results than robots.txt alone.
- Match or improve on-page elements. Carry over title tags, meta descriptions, H1s and key body content from valuable pages, or improve them deliberately.
- Keep URL structure where possible. Every URL you keep is one less redirect and one less risk.
- Rebuild internal links. Link to new URLs directly in navigation, footers and body content.
- Recreate structured data. Add Organization, LocalBusiness, Article, Product or breadcrumb markup to the new templates; our schema markup guide has examples you can adapt.
- Set canonical tags correctly. Each page should point to its own preferred URL on the new site, not to the old domain or the staging address.
- Generate a new XML sitemap. It should list only live, indexable, canonical new URLs.
- Hit performance targets. Test templates against Core Web Vitals. Google’s “good” thresholds are a Largest Contentful Paint of 2.5 seconds or less, an Interaction to Next Paint of 200 milliseconds or less, and a Cumulative Layout Shift of 0.1 or less.
- Design for accessibility. A relaunch is the cheapest moment to meet WCAG requirements; see our WCAG accessibility guide.
- Install analytics and conversion tracking. Confirm events fire on staging so launch-day data is complete. Our GA4 setup guide covers the basics.
- Check mobile rendering. Google primarily uses the mobile version of a page for indexing, so mobile templates must include all important content.
SEO QA list: test these before go-live
The QA list is a set of checks run on staging before launch and repeated on the live site immediately after. Assign each check an owner and record a pass or fail.
| Check | How to test | Pass criteria |
|---|---|---|
| Redirects | Run the full old URL list through a crawler or bulk redirect checker | Every mapped URL returns one 301 hop to the correct page |
| Indexability | Inspect page source and headers on key templates | No unintended noindex tags or X-Robots-Tag headers |
| Robots.txt | Review the production robots.txt file | No Disallow: / and no blocked CSS or JavaScript needed to render pages |
| Canonicals | Crawl the site and review canonical tags | Self-referencing canonicals on indexable pages, no staging URLs |
| Internal links | Crawl the site | No internal links to 404s or redirected URLs |
| Metadata | Compare titles and H1s with the old site | Priority pages keep or improve their keyword targeting |
| Structured data | Test key templates in the Rich Results Test | No errors on important types |
| Page speed | Test key templates with lab and field tools | Meets your Core Web Vitals targets |
| Mobile | Test on real devices and narrow viewports | Content parity with desktop; no layout breakage |
| Forms and tracking | Submit every form; check analytics real-time reports | Leads arrive and conversions are recorded |
| XML sitemap | Open the sitemap and spot-check URLs | Only live, canonical, indexable URLs listed |
| 404 page | Visit a made-up URL | Returns a real 404 status with helpful navigation |
A broader technical SEO audit checklist is a good companion if you want to check crawling, indexing and site architecture in more depth.
Phase 3: Launch day
Launch day is when the staging site becomes the live site, and the main job is removing every temporary block while switching on every redirect at the same moment.
- Choose a quieter traffic period for the launch, and avoid your busiest season.
- Deploy the new site and the redirect rules together.
- Remove password protection, noindex tags and staging-only robots.txt rules.
- Re-run the QA list on the live domain, starting with redirects and indexability.
- Submit the new XML sitemap in Google Search Console.
- Inspect your homepage and top pages with the URL Inspection tool and request indexing for the most important ones.
- Confirm analytics and conversion tracking are recording live data.
- If your domain changed, verify both domains in Search Console and use the Change of Address tool. It applies only to domain-level moves and requires working 301 redirects from the old domain.
- Update your Google Business Profile, social profiles and key directory listings if URLs or the domain changed.
- Keep the old sitemap available temporarily if you want Google to discover the redirects faster.
Phase 4: After launch, monitoring and fixes
Post-launch monitoring is the process of comparing the new site against your benchmark and fixing issues before they become ranking losses. Google Search Central notes that search visibility may fluctuate temporarily during a move, and that most pages on a small to medium site can take a few weeks to move. Your job is to tell normal fluctuation from real damage.
| When | What to check | Where |
|---|---|---|
| Day 1 | Redirects, indexability, forms, tracking, server errors | Crawler, URL Inspection, analytics real-time |
| Week 1 | New 404s, crawl errors, sitemap processing | Search Console Page indexing and Sitemaps reports |
| Weeks 2 to 4 | Indexed page count, impressions and clicks versus baseline | Search Console Performance report |
| Months 2 to 3 | Rankings and conversions for priority pages | Rank tracker, analytics, Search Console |
| Ongoing | Redirect health, broken links, Core Web Vitals | Monthly crawl and Search Console reports |
What is a normal dip, and when should you worry?
A short, modest dip that recovers over a few weeks is common while Google processes redirects and recrawls pages. Worry when traffic keeps falling after several weeks, when specific high-value pages disappear entirely, or when Search Console shows growing numbers of “Not found (404)” or “URL marked ‘noindex'” pages. Compare against the same period last year to rule out seasonality.
What to do if rankings drop after a redesign
If traffic has dropped beyond normal fluctuation, work through these checks in order:
- Check for blocks. Look for leftover noindex tags, robots.txt rules or password protection on live pages.
- Check redirects. Run the old URL list again and look for 404s, chains and redirects to the homepage.
- Compare content. Put the old and new versions of your top pages side by side. Did important text, headings or FAQs disappear?
- Compare internal links. Did key pages lose links from navigation or related content?
- Check rendering and speed. Use URL Inspection to confirm Google sees the full content, then test page speed.
- Restore what worked. Reinstate content and on-page elements that were removed from your strongest pages.
If pages are missing from search altogether rather than just ranking lower, follow our guide to diagnose why a site is not showing on Google, which walks through each indexing cause in order.
Frequently asked questions
Will a website redesign hurt my SEO?
A redesign does not have to hurt SEO. Losses usually come from avoidable mistakes: missing redirects, removed content, leftover noindex tags and broken internal links. When URLs, content and technical signals are carried over carefully, many sites hold steady, and some improve thanks to better speed, structure and content. Some short-term fluctuation is normal.
How long does it take to recover SEO after a redesign?
Recovery time depends on site size and how cleanly the migration was handled. Google Search Central notes that most pages on a small to medium site can take a few weeks to move, and that visibility may fluctuate during that time. If traffic is still falling after several weeks, look for technical errors rather than waiting.
Should I keep the same URLs when redesigning?
Yes, wherever possible. Keeping URLs removes the need for redirects and preserves each page’s history with the least risk. Change URLs only when there is a clear benefit, such as replacing messy parameter URLs with readable ones. When you do change them, map every old URL to its closest new equivalent with a 301 redirect.
How long should I keep 301 redirects after a relaunch?
Google Search Central recommends keeping redirects for as long as possible, generally at least one year. Many businesses keep them permanently, because old URLs can live on in bookmarks, emails, printed materials and links from other websites. Redirects cost very little to maintain compared with the value they protect.
Do I need the Change of Address tool for a redesign?
Only if your domain changes, for example from oldbrand.com to newbrand.com. The tool in Google Search Console works at the domain level and requires 301 redirects from the old site to be in place. For a redesign on the same domain, even with new URLs, redirects and an updated sitemap are enough.
When is the best time to launch a redesigned website?
Launch during a quieter period for your business, not just before your peak season, so any temporary dip has less impact and your team has time to fix issues. Avoid launching late on a Friday or before holidays, when fewer people are available to monitor problems and respond quickly.
