
Website Redesign SEO Checklist: How to Protect Your Rankings
A website redesign can make your business look more credible, simplify navigation and help visitors become customers. It can also remove the pages, links and content that brought those visitors to your website in the first place.
The problem usually starts before launch. Someone changes the URL structure without recording the existing addresses. A useful service page disappears because its layout looks dated. A development setting prevents important pages from being indexed.
None of these decisions needs to happen deliberately to cause damage. A website redesign SEO checklist helps you identify what already works, carry it into the new website and verify that the finished version remains accessible to users and search engines.
This guide explains what to check before, during and after a redesign. It applies to business websites, service websites and online shops, with additional migration steps where URLs, domains or platforms change.
Can You Redesign a Website Without Losing SEO?
You can reduce the risk of losing organic visibility by planning the redesign around existing search performance. However, no agency or checklist can guarantee that every ranking will remain unchanged. A redesign may alter content, navigation, page layout, internal links and technical behaviour. Search engines need to assess those changes, and some fluctuations are possible.
The practical goal is to preserve valuable assets, avoid preventable errors and identify problems quickly. For example, a page generating qualified enquiries should receive closer attention than an outdated announcement with no remaining purpose. That does not mean keeping the old design. It means understanding why the page matters before changing it.
Website Redesign vs SEO Migration
A redesign changes how a website looks or works. An SEO migration involves changes that can affect how search engines access, identify or interpret its pages. The two often overlap, but they are not identical.
| Project | Main SEO consideration |
|---|---|
| Visual refresh with unchanged URLs | Content, navigation, rendering and performance |
| CMS change with unchanged URLs | Templates, metadata, technical settings and functionality |
| URL structure change | URL mapping, redirects and updated references |
| Domain change | Domain migration planning and property verification |
| Hosting change | Availability, response behaviour and infrastructure |
| Content consolidation | Relevance, page purpose and appropriate destinations |
Do not create redirects simply because the website has a new appearance. If a useful page keeps the same address and purpose, it can usually remain at that URL.
Before the Redesign: Understand What You Need to Protect

The first deliverable should be a record of the existing website. Without this baseline, a post-launch traffic change becomes harder to explain. You may know that visits have fallen without knowing which pages, queries or customer journeys were affected.
1. Record Organic Search and Conversion Performance
Export relevant data from Google Search Console and your analytics platform before development begins.
Record:
- Organic landing pages and their traffic.
- Search queries associated with important pages.
- Clicks, impressions and search visibility.
- Enquiries, purchases or other meaningful conversions.
- Device and country breakdowns where relevant.
- Seasonal patterns that could affect comparisons.
Choose a reporting period that reflects your business. A short snapshot can help with recent performance, but a longer period is useful for identifying seasonality.
Average position should not be your only success measure. A website can lose visibility for low-value searches while improving the enquiries that matter to the business.
2. Build a Complete URL Inventory
A website crawl is a useful starting point, but it may miss pages that have no discoverable internal links. Combine your crawl with available URLs from the CMS, XML sitemaps, Search Console, analytics and backlink data. Include valuable PDFs and other assets where relevant.
This is also a good opportunity to investigate disconnected content. Our guide to finding orphan pages on a website explains how to identify pages that may be missing from the normal navigation structure.
The result should be a working inventory with a clear decision for each relevant URL.
3. Decide Which Pages to Keep, Improve, Merge or Remove
Avoid treating every existing page as equally valuable. Equally, avoid deleting content simply because its design looks old.
Review each page against its purpose:
| Decision | Appropriate situation | What to document |
|---|---|---|
| Keep | The page remains useful and relevant | Existing URL and important elements |
| Improve | The purpose is valid, but the page needs work | Content and usability changes |
| Merge | Several pages genuinely serve the same need | Content to retain and final destination |
| Remove | The content has no continuing purpose | Reason and intended response |
| Create | An important user need is not covered | Page purpose and target audience |
Low traffic alone does not prove that a page has no value. It may support existing customers, attract relevant links or answer a narrow but commercially important question.
4. Map Search Intent to the New Website Structure
Before approving the sitemap, establish which page should answer each important search need. A service page, pricing guide and case study can relate to the same subject while serving different purposes. Combining them into one attractive page may make the website simpler visually but less useful for visitors.
Use a keyword mapping process to connect topics and search intent to the appropriate pages. The aim is clarity. Each important page should have a defined role, while supporting content should help visitors move towards the next relevant step.
Plan Your URL Mapping and Redirects
If URLs are changing, create the mapping before launch. This spreadsheet should show where each existing address will lead and why that destination is appropriate. It is a practical implementation document, not something to reconstruct after broken pages appear.
5. Match Old URLs to Relevant New Destinations
The following example is illustrative:
| Existing URL | Planned destination | Action |
|---|---|---|
/web-design/ |
/web-design/ |
Retain the URL |
/website-development.html |
/services/web-development/ |
Permanent redirect |
/old-seo-checklist/ |
/technical-seo-checklist/ |
Redirect if the new guide replaces it |
/expired-event/ |
No relevant replacement | Return a genuine 404 or 410 |
/resources/brochure.pdf |
/downloads/brochure.pdf |
Redirect if the asset moves |
Do not send every removed page to the homepage. A destination should satisfy the original visitor’s need. Where no suitable replacement exists, an appropriate error response is preferable to an unrelated redirect.
Google’s migration guidance recommends planning URL mappings, testing the new website and monitoring the transition. It also recommends retaining redirects for at least a year, and longer where they remain useful.
6. Test Redirect Behaviour
For permanent URL moves, use server-side permanent redirects, normally 301 or 308, where possible.
Check the full journey:
- The old address returns the intended redirect.
- The destination is the correct page.
- The destination loads successfully.
- There is no redirect loop.
- Avoidable intermediate redirects have been removed.
A redirect can work technically while still sending the visitor to the wrong content. Test relevance as well as status codes. Permanent redirects communicate a lasting move; temporary redirects serve a different purpose. Choose the response according to the change being made.
During Development: Preserve the Elements That Support SEO

A working prototype can look complete while important search elements remain missing. Review actual templates and representative pages throughout development. Testing only the homepage leaves too much of the website unchecked.
7. Protect Useful Content When Updating the Design
A common redesign mistake is replacing a detailed service page with a short headline, a large image and a contact button.
The new layout may look cleaner, but it may no longer explain the service well enough.
Preserve useful information such as:
- Who the service is for.
- What the service includes.
- Relevant expertise and evidence.
- How the process works.
- Questions that affect the buying decision.
- Clear next steps.
This does not mean preserving every sentence. Improve outdated or repetitive material, while keeping the information that helps visitors understand and evaluate the offer. A bespoke website design project should accommodate the content your customers need, rather than forcing every page into the same restrictive layout.
8. Review Titles, Headings and Page Metadata
Export the old page titles and descriptions, then compare them with the new versions. Look for missing titles, repeated template text and important pages that have inherited generic metadata. Use a clear main heading and logical subheadings. Include the page’s main topic naturally, without repeating the same keyword in every heading.
Meta descriptions should accurately summarise the page and give people a reason to visit. They should not make promises that the content does not support.
9. Rebuild Internal Links Around Useful Journeys
A navigation redesign can leave important pages harder to find, even when their URLs remain unchanged. Check menus, breadcrumbs, footer links and links within the main content. Update links to moved pages so they point directly to the final destination. Consider the visitor’s journey. Someone reading about redesign risks may need a technical review, while someone comparing development options may need a detailed service explanation.
Internal linking should make those next steps easier. Avoid placing a service link in every paragraph simply to increase link frequency.
10. Check Canonical URLs
A canonical annotation helps indicate the preferred URL among duplicate or similar pages. Check that the new website does not publish staging addresses, outdated domains or incorrect canonical targets. A template error that points multiple unrelated pages to the homepage deserves immediate attention.
For unique pages intended to be indexed, a self-referencing canonical is commonly appropriate. Where duplicates exist, the preferred version should be chosen deliberately. Canonical annotations, internal links and sitemap entries should support a consistent URL strategy. However, a canonical is a signal rather than a guarantee of Google’s selection.
11. Handle Staging Restrictions Carefully
Keep the development website protected from unintended public access, for example through authentication. Before launch, check the production configuration for inherited restrictions. Review both HTML robots directives and HTTP headers.
A noindex directive can prevent an accessible page from appearing in search results. A robots.txt crawl block serves a different purpose: it does not reliably keep a URL out of the index.
Google must be able to crawl a page to see its noindex instruction. Do not assume that combining a crawl block with noindex makes the instruction more effective.
12. Verify Rendered Content and Navigation
If the redesign changes how JavaScript is used, check the rendered pages as well as their source HTML. Confirm that important content and links are available without requiring a visitor to perform an action that a crawler may not complete.
Test representative service pages, articles and product or category templates where applicable. Look for missing text, failed resources and navigation elements that do not produce usable links.
A page that looks correct in one browser session may still have rendering problems. Google’s JavaScript documentation explains why crawling and rendering both matter when assessing the content it can process.
13. Test Mobile Usability and Performance
Check the new website on realistic mobile conditions. Large hero images, animation, video and third-party scripts can affect loading and interaction. Forms may also become difficult to use even when the desktop layout looks excellent.
Review Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift alongside practical usability checks. Pre-launch lab tests help identify problems. Post-launch field data, where available, helps reveal real-user experience. Good Core Web Vitals support page experience, but strong scores do not guarantee high rankings.
14. Validate Tracking and Customer Actions
Complete a real test of each important action: submitting an enquiry, booking a call or placing a test order where appropriate. Confirm that the action works, the business receives it and the relevant analytics event is recorded as intended. Check that tracking does not fire twice.
Keep measurement definitions consistent where possible. If consent behaviour or analytics configuration changes during the redesign, document it. Otherwise, a reporting difference may be mistaken for an SEO decline.
Website Redesign SEO Launch Checklist
Schedule the release when the people responsible for development, hosting and SEO can respond.
Have a backup and a clear recovery plan. Record the launch time and the changes included in the release.
| Launch check | Expected result |
|---|---|
| Important live pages | Correct content and successful responses |
| Moved URLs | Correct permanent redirects |
| Robots directives | Intended indexability |
| Canonicals | Correct production URLs |
| Internal links | Relevant final destinations |
| XML sitemap | Intended canonical URLs |
| Images and downloads | Accessible and correctly linked |
| Structured data, where applicable | Accurate and consistent with visible content |
| Forms and transactions | Working end to end |
| Analytics | Recording expected activity |
| Mobile templates | Usable without major layout problems |
| Hosting and HTTPS | Stable and correctly configured |
Crawl the production website after deployment. A staging audit cannot confirm that production redirects, caching, security rules and headers behave correctly. Where the project also changes hosting, verify availability and response behaviour on the new infrastructure. Google provides separate guidance for hosting moves that keep the existing URLs.
After Launch: Monitor SEO Performance by Page and Purpose
Launch day is the start of validation.
Use a practical monitoring schedule, adjusted to the size and risk of the project:
| Period | Main focus |
|---|---|
| Immediately after launch | Access, redirects, tracking and customer actions |
| First week | Crawl errors, indexability and priority pages |
| Following weeks | Search visibility, landing-page traffic and conversions |
| Longer term | Persistent issues and opportunities to improve |
These are working review periods, not a promise about how quickly search performance will settle.
Compare Equivalent Pages
If a service page moves, compare the old and new addresses together. Looking only at the original URL will naturally show a decline after its replacement takes over. Where several pages have been merged, compare the combined topic group. Also compare equivalent weekdays and consider seasonality. Separate branded searches from non-branded searches where that helps explain the pattern.
Investigate Changes in Enquiries, Not Just Visits
If organic visits remain stable but enquiries fall, check forms, calls to action, tracking and page messaging. If Search Console clicks remain stable while analytics sessions fall sharply, investigate measurement and consent changes alongside technical access.
These patterns help narrow the diagnosis. They do not prove the cause on their own.
What to Do If Traffic Drops After a Website Redesign

Start with the affected pages and the release record.
Check for:
- Accidental
noindexdirectives or access restrictions. - Broken URLs and incorrect redirect destinations.
- Canonicals pointing to the wrong location.
- Missing content or rendering failures.
- Important pages losing internal links.
- Analytics changes that distort the comparison.
Prioritise widespread issues before rewriting individual pages. A template error can affect hundreds of URLs, while a content issue may be limited to one section. Avoid making several unrelated changes before understanding the problem. That makes it harder to identify which correction helped.
For businesses that need a structured technical and content review, our search engine optimisation services provide a relevant starting point.
Frequently Asked Questions About Website Redesign SEO
Does a website redesign always hurt SEO?
No. A redesign can improve usability and resolve existing problems. Risk increases when valuable content, URLs or technical settings change without planning and testing.
Should I change URLs to make them look cleaner?
Only when there is a clear reason. A shorter URL alone rarely justifies disrupting a useful, established address. If a URL must change, document and test the move.
Do I need redirects if the URLs stay the same?
Not for those unchanged pages. Redirect planning is needed for addresses that move or are replaced.
Is a redirect enough to protect a page’s performance?
No. The destination must remain useful and relevant. Content, internal links, accessibility and other changes still need assessment.
Can I remove old blog posts during a redesign?
Yes, where there is a sound reason. First check their purpose, links, search visibility and usefulness. Age alone is not a reason to delete a page.
Can an agency guarantee no ranking losses?
No. An agency can offer a careful process, testing and monitoring. It cannot control search rankings or guarantee that every position will remain unchanged.
Plan SEO Before Approving the New Design
A successful redesign starts with understanding the website you already have: which pages attract relevant visitors, which content supports decisions and which journeys generate enquiries.
Use that evidence to guide the structure, preserve useful content and test the production website thoroughly.
If you are preparing to redesign your business website, explore London Design’s bespoke website design services and discuss the pages, functionality and search visibility your project needs to support.





























