Website migration SEO: how to protect search visibility
4th Nov 2026 23 minutes read 13 sections
Overview
Replacing an existing website involves more than updating its design or content management system. Over time, a website can build a strong presence in search results, driving traffic to key pages and helping users find the information they need.
A redevelopment can improve all of these things, but it can also put existing search performance at risk. Changing URLs, reorganising content or introducing technical problems may affect how search engines understand and rank the replacement website.
Website migration SEO helps organisations manage those risks. It brings search performance into the redevelopment process from the beginning, rather than treating optimisation as something to address once the new website is ready.
This guide covers the main stages of an SEO migration, from auditing the existing website and planning content changes through to redirects, technical testing, launch and ongoing monitoring.
What is website migration SEO?
Website migration SEO is the process of protecting and managing a website’s organic search performance when you make significant changes to its content, structure, or underlying technology.
A migration could involve moving to a different content management system, changing domain names, restructuring URLs, or replacing the website entirely. Even when the domain stays the same, changes to content and internal linking can affect search visibility.
The purpose isn’t necessarily to keep everything exactly as it was. A redevelopment should provide opportunities to improve content, usability and technical performance. Migration SEO helps organisations make those improvements without unnecessarily losing the search visibility their existing website has established.
Common types of website migration
Website redesign
Updating the appearance, layouts and functionality of an existing website. SEO considerations depend on whether content, URLs and internal links also change.
CMS migration
Moving a website to a different content management system, such as switching from an older platform to WordPress.
Domain migration
Moving a website to a new domain name, for example, when an organisation changes its name or rebrands.
URL restructuring
Changing how website addresses are organised, usually alongside improvements to navigation or information architecture.
Content migration
Transferring, rewriting, consolidating or removing content as part of a website redevelopment.
Website consolidation
Combining multiple websites or domains into a single platform, often involving substantial content and URL mapping.
Read more
Website migrations will rarely fall neatly into one category. For example, a university replacing an older CMS might also introduce a new design, reorganise its course information and change hundreds of URLs. Each decision can affect search performance.
The level of SEO risk depends on the extent of those changes. A visual redesign that preserves existing URLs and content is generally less disruptive than a migration involving a new domain, revised navigation and substantial content changes.
This is why migration planning needs to begin before development. Understanding what will change allows the project team to identify potential problems, agree responsibilities and establish how existing search visibility will be protected.
It’s also worth distinguishing between migration SEO and ongoing search optimisation. Migration SEO concentrates on managing a period of significant change. Once the replacement website has launched and settled, the focus returns to improving content, technical performance and search visibility over time.
Explore this further
CMS migration: moving to a new content management system
More information coming soon
Planning a website redesign
More information coming soon
Website content migration: what to keep, improve or remove
More information coming soon
Why can website migration affect SEO?
Search engines build an understanding of a website through its content, URLs, internal links and technical signals. Over time, individual pages may become associated with specific search queries, attract links from other websites and establish visibility for important subjects.
When a website changes, search engines need to discover and process those changes.
If an established URL disappears without a suitable redirect, people and search engines may no longer be able to reach the information it previously contained. If important content is removed or substantially rewritten, the replacement page may no longer be relevant to the same searches.
Problems can also arise when a new website is technically inaccessible, internal links are incorrect or indexing settings haven’t been updated for launch.
These issues don’t mean organisations should avoid making changes. They mean those changes need to be planned with an understanding of what already works.
Read more
Search engines don’t simply transfer all existing rankings to a replacement website because it belongs to the same organisation. They need to understand how the new pages relate to the old ones and whether the content remains relevant to the searches for which it previously appeared.
Permanent redirects, known as 301 redirects, help communicate when URLs have moved. Internal links help search engines discover important pages and understand their relationships. Canonical tags, XML sitemaps and indexing directives provide additional technical information about which pages should appear in search results.
A page might be doing well in Google because it contains detailed answers to questions people are searching for. Strip that information out during a redesign and there’s a chance it’ll stop appearing for some of those searches. It’s something we need to watch when rewriting content or merging several pages into one.
There can be a bit of movement in Google after a new website goes live, too. Some pages get picked up quickly, while others take longer. We’d expect to see things settle, but if a page that previously brought in enquiries suddenly stops getting traffic, we’d want to know what’s happened.
A well-managed migration reduces unnecessary disruption and makes it easier to identify the cause of problems when they occur.
Explore this further
Measuring website success beyond traffic
Traffic tells part of the story. Learn how to measure website success by choosing the…
Understanding technical SEO and website indexing
More information coming soon
Auditing your existing website
Before planning the replacement website, it’s important to understand how the current one performs.
A pre-migration SEO audit identifies the pages that attract organic traffic, the searches they appear for and the content that contributes to enquiries, applications or other important actions.
It’s worth checking this information before deciding what stays on the new website and how the navigation will work. Otherwise, you could end up removing pages that perform well in search or changing URLs that would have been better left alone.
The audit also provides a baseline for measuring performance after launch. Rather than relying on impressions about whether traffic has improved or declined, the project team can compare results against recorded evidence.
What should the audit cover?
Organic search performance
Identify important landing pages, search queries, clicks, impressions and ranking trends.
Content and URLs
Record existing pages, their purpose, current addresses and whether they should be retained, improved or removed.
Technical SEO
Review indexing, redirects, canonical URLs, broken links, metadata and existing technical issues.
Conversions and business value
Identify pages that support enquiries, applications, bookings or other organisational objectives.
Read more
Google Search Console is particularly useful when you’re trying to understand which pages receive impressions and clicks from Google Search. Analytics provides another perspective by showing what people do after reaching the website.
Neither source tells the complete story on its own. A page with relatively little organic traffic might still attract highly relevant enquiries, while a frequently visited page may have limited value to the organisation.
A website crawler can help create an inventory of existing URLs and identify technical issues. However, crawlers generally discover pages through links, so their results should be compared with XML sitemaps, Search Console and CMS exports to identify content that may otherwise be missed.
External backlinks also deserve attention. A page might receive links from other organisations, publications or authoritative resources. Even if that page attracts limited direct traffic, those links are worth considering when deciding what happens to its URL.
The outcome should be a practical record that informs the redevelopment. It doesn’t need to become an unnecessarily complicated document, but it should provide enough information for content editors, designers, developers and SEO specialists to make informed decisions.
Explore this further
How to carry out a website SEO audit
More information coming soon
Website content audits: reviewing content before redevelopment
More information coming soon
Planning website content migration
Content migration is often one of the largest parts of a website redevelopment, particularly for organisations managing hundreds or thousands of pages.
It’s also an opportunity to improve the quality and organisation of information. Outdated content can be updated, overlapping pages consolidated and important subjects given more appropriate prominence.
We’ve worked on websites where some of the most useful pages have been around for years, quietly bringing in traffic from Google. You wouldn’t want to lose those during a redevelopment. Equally, there’s not much sense in copying across hundreds of pages without checking whether they’re still needed. Some might be out of date, others might cover almost identical subjects. It’s about working out what’s worth keeping, what needs improving and what can be left behind.
The aim is to decide what the replacement website needs while protecting useful content and the search visibility associated with it.
Deciding what happens to existing content
Keep
Retain content that remains accurate, relevant and useful, particularly where it already performs well in search.
Improve
Update content that needs attention while preserving the information and subject matter that make it valuable.
Consolidate
Combine overlapping pages where a single destination would provide a better experience and adequately cover their subjects.
Remove
Retire content that is no longer needed, considering existing traffic, links and whether a suitable replacement exists. Add redirects where appropriate.
Read more
A content inventory should record each existing page and its intended outcome. For pages being moved or replaced, it should also identify the destination URL.
This creates an important connection between editorial decisions and technical migration work. If several pages are consolidated, for example, the development team needs to know which new page should receive their redirects.
Content performance shouldn’t be the only factor in these decisions. Some information may be essential for existing users even if it attracts little search traffic. Other pages may support important organisational requirements or provide information that people expect to find.
Rewriting a page doesn’t mean starting again with completely different content. If people are finding it through Google because it answers particular questions, we need to make sure those answers are still there. The wording can change, and there’s often plenty of room for improvement, but we don’t want to lose the information that made the page useful in the first place.
Removing content also requires judgement. If a page has a suitable replacement, a permanent redirect will usually be appropriate. If the information has been withdrawn and there is no relevant destination, returning a genuine 404 or 410 response may be preferable to sending people somewhere unrelated.
For large websites, clear ownership is particularly important. Content teams need to know which pages they’re responsible for reviewing, while developers need reliable information about content relationships, redirects and publishing requirements.
Explore this further
Website content migration: what to keep, improve or remove
More information coming soon
Information architecture during a website redesign
More information coming soon
Managing URLs and redirects
URLs are one of the most important considerations during a website migration.
An established URL may already appear in search results, receive links from other websites and be referenced in documents, emails or external resources.
Changing that address without planning what happens next can make the content difficult to find and disrupt its existing search visibility.
Where possible, retaining suitable URLs reduces migration complexity. However, changes may be necessary when a website introduces a new content hierarchy, combines sections or replaces an older CMS.
In those circumstances, a redirect plan helps connect the existing website to its replacement.
Creating a URL migration map
A URL migration map records the old address of each page and its intended destination.
Course page
- Old URL: /courses/business-studies/
- New URL: /study/business/
- Action: Permanent redirect to the replacement course page.
Team page
- Old URL: /about/our-team/
- New URL: /about/team/
- Action: Permanent redirect to the replacement team page.
Existing service page
- Current URL: /services/consultancy/
- New URL: Unchanged.
- Action: Retain the existing address.
Read more
One of the bigger jobs during a migration is making sure old website addresses still work. We normally use 301 redirects for this, although 308 redirects are another option. Both tell Google that a page has permanently moved.
Getting the destination right matters. Say you’ve changed the address of a course page. Someone finding it through an old Google result should still reach that course, not end up on the homepage wondering where to go next. The same applies to service pages, articles and anything else people might have bookmarked or linked to.
There are a few technical things to watch for, too. We’ve seen redirects that send people through several different addresses before reaching the page they wanted. Sometimes they even point back to each other, creating a loop that prevents the page from loading. Neither is something you want to discover after launch.
We’d also update the links throughout the new website. There’s little point having a brand-new navigation system that still points to old addresses, even if the redirects technically work.
And the redirects need to stay in place. Google recommends keeping them for at least a year after a site move, but we’d generally leave them running for longer. An article published five years ago might still contain a link to your old website, and there’s no reason to break that connection.
Before launch, we’d work through the redirect list and check where each address leads. We’d repeat those tests on the live website, looking for incorrect destinations, broken links and any redirects that aren’t behaving as expected.
Explore this further
Website redirects explained: 301s, 308s and URL mapping
More information coming soon
Website migration checklist: preparing for launch
More information coming soon
Technical SEO during redevelopment
A replacement website needs to be technically accessible to search engines.
Even when content and redirects have been managed correctly, indexing restrictions, incorrect canonical URLs or broken internal links can prevent important pages from appearing in search results.
Technical SEO should therefore be included in development requirements and testing from the beginning.
This is particularly important when changing CMS platforms. Different systems may generate metadata, XML sitemaps, canonical URLs and other technical elements in different ways.
The replacement website should preserve the necessary functionality while taking opportunities to improve performance, accessibility and maintainability.
Technical SEO requirements
- Page titles and meta descriptions
- Heading structure and content hierarchy
- Canonical URLs
- Robots directives and indexing settings
- XML sitemaps
- Structured data and Schema.org markup
- Internal links and breadcrumbs
- Mobile usability and website performance
- Staging and development environment restrictions
Read more
Page titles, descriptions and headings should be reviewed as part of content migration. Important pages need appropriate metadata that reflects their subject and the information they contain.
Canonical tags tell Google which version of a page we’d prefer it to use when similar content appears at more than one address. During a migration, we need to check that these haven’t been left pointing to the old website or, worse, a development version that was never intended to appear in search results.
There’s a similar risk with indexing settings. We normally prevent Google from indexing a website while it’s being developed, but those restrictions need removing when the new site goes live. Leave a noindex instruction in place and Google could exclude an important page from its search results, even though everything looks perfectly normal to someone browsing the website.
XML sitemaps should contain the intended canonical URLs for the replacement website. Redirected and deliberately non-indexable pages generally shouldn’t appear in them.
Structured data needs reviewing where page types or content relationships change. It should accurately describe the published information rather than simply reproduce markup from the previous website.
Internal linking is equally important. Navigation, breadcrumbs and related content help people and search engines discover pages and understand how subjects connect.
Finally, redevelopment provides an opportunity to improve website performance. Loading speed, mobile usability and accessibility should be tested across representative page types, rather than relying on a single homepage test.
Explore this further
What is structured data? How search engines and AI understand your website
Learn what structured data is, how Schema.org and JSON-LD work, and why structured data helps…
Technical SEO migration checklist
More information coming soon
Website indexing explained: robots.txt, noindex and canonical URLs
More information coming soon
Preparing for website launch
A website migration needs a coordinated launch plan.
Development, content, SEO, hosting and analytics all have responsibilities, and those responsibilities should be agreed before the replacement website goes live.
For larger organisations, several teams may be involved. Content editors might be reviewing hundreds of pages while developers prepare redirects and technical changes. Marketing teams may also need to check analytics, campaigns and conversion tracking.
A clear launch process reduces the risk of overlooking important tasks.
Planning the launch
The launch date should allow enough time for testing and monitoring. Where possible, avoid periods when website availability is particularly important, such as major campaigns, application deadlines or organisational events.
The team should also agree on what to do if a significant problem is discovered.
This might involve correcting configuration issues, restoring a previous deployment or implementing a wider recovery plan.
Read more
Before launch, the replacement website should be tested in an environment that closely reflects production.
Important page types, user journeys and technical functionality need checking. This includes forms, search, navigation, redirects, integrations and any functionality that depends on external services.
The launch plan should identify who is responsible for activating redirects, checking indexing settings, validating analytics and monitoring errors. It should also establish who can make decisions if a problem requires immediate attention.
Backups and rollback arrangements need to be understood before deployment. Returning to a previous website version isn’t always straightforward, particularly when databases, content or external systems have changed.
The SEO team should have access to the information needed to check the live website immediately after launch. This includes the redirect map, important URL lists, Search Console and relevant analytics reports.
Once the replacement website is live, a fresh crawl can help identify broken links, incorrect redirects and technical problems that weren’t apparent during staging.
Explore this further
Website migration checklist: preparing for launch
More information coming soon
Website launch testing: what to check before going live
More information coming soon
Monitoring SEO after migration
Website migration SEO continues after launch.
Search engines need time to discover the replacement pages, process redirects and update their understanding of the website.
Monitoring helps establish whether the migration is progressing as expected and identifies problems that need attention.
Google Search Console provides useful information about indexing, search queries, impressions and clicks. Analytics can help establish whether people are continuing to reach important content and complete relevant actions.
Both should be reviewed against the baseline recorded before migration.
What should be monitored?
Search visibility
Changes in organic clicks, impressions, rankings and important landing pages.
Indexing and crawling
Unexpected exclusions, missing pages, crawl errors and canonicalisation issues.
Redirects and broken links
Old URLs, 404 errors, redirect chains and incorrect destinations.
Conversions and user journeys
Whether people can still complete enquiries, applications, bookings and other important tasks.
Read more
Performance comparisons should account for seasonal demand, campaigns and other factors that might influence traffic independently of the migration.
Site-wide figures can also hide problems affecting individual sections. A website might retain its overall traffic while losing visibility for an important service or subject area.
Reviewing individual landing pages and search queries can help identify where changes have occurred. If a page loses visibility, investigate whether its content, URL, internal links or technical settings changed during redevelopment.
Google Search Console can help us spot pages that aren’t being indexed when they should be. It might be something as simple as a noindex setting left in place after launch, a page Google can’t access or a canonical tag pointing to the wrong address. We’d also check the old URLs to make sure their redirects are still working and taking people to the right pages.
If the migration involves a qualifying domain move, Google’s Change of Address tool may also be appropriate. It isn’t needed for ordinary URL changes within the same domain or HTTP-to-HTTPS migrations.
Some ranking fluctuations are expected during a substantial migration, and there is no universal recovery period. The time required depends on the extent of the changes, how frequently Google crawls the website and whether issues need resolving.
Persistent losses should be investigated rather than assumed to be temporary.
Explore this further
Measuring website success beyond traffic
Traffic tells part of the story. Learn how to measure website success by choosing the…
How to monitor SEO performance after a website migration
More information coming soon
Common website migration SEO mistakes
Many migration problems can be traced back to decisions made before launch.
Understanding the most common mistakes helps organisations avoid unnecessary disruption.
Changing URLs without a clear reason
When rebuilding a website, we’d always recommend looking at the existing URLs before deciding whether to change them. If things are working well, there’s usually little benefit in replacing them. Every address that changes needs a redirect, and we’d rather avoid that extra work where it isn’t necessary, particularly when other websites already link to those pages.
Removing content without checking its performance
It’s easy to look at an old page and assume nobody needs it anymore. But it might still be attracting people through Google or providing information that a particular audience relies on. We’d always check how a page is being used before deciding whether to remove it.
Redirecting unrelated pages to the homepage
Redirects should lead to relevant destinations. Sending unrelated URLs to the homepage can confuse people and may be treated by Google as a soft 404.
Changing too much at once
A migration involving a new domain, CMS, navigation and substantial content rewrites introduces more variables. Sometimes these changes are necessary, but each should be planned and tested.
Forgetting internal links
Redirects may keep old links working, but internal navigation should point directly to current URLs.
Leaving staging restrictions in place
Incorrect noindex directives or robots.txt rules can prevent important production pages from being indexed.
Failing to monitor after launch
Some problems only become apparent when search engines begin crawling and processing the replacement website. Without monitoring, those issues can remain unresolved.
Website migration SEO checklist
A practical checklist helps keep migration tasks visible throughout the project.
The following covers the main SEO responsibilities before, during and after launch.
Before migration
- Audit existing organic search performance.
- Record important keywords, landing pages and conversions.
- Identify valuable URLs and external backlinks.
- Complete the content inventory.
- Agree which pages will be retained, improved, consolidated or removed.
- Review the replacement website’s information architecture.
- Preserve existing URLs wherever practical.
- Prepare and review the redirect map.
- Check metadata, headings and internal linking requirements.
- Confirm canonical and indexing settings.
- Test the replacement website’s technical SEO.
- Agree launch responsibilities and recovery procedures.
During launch
- Confirm the production website is accessible.
- Activate and test permanent redirects.
- Check important pages return the correct HTTP status.
- Confirm production pages aren’t unintentionally blocked or marked noindex.
- Validate canonical URLs.
- Check navigation and internal links.
- Verify analytics and conversion tracking.
- Generate and submit the updated XML sitemap.
- Crawl the live website.
- Investigate broken links and server errors.
After migration
- Monitor Google Search Console.
- Compare organic search performance with the baseline.
- Review important keyword rankings and landing pages.
- Investigate unexpected 404 errors.
- Check that redirects continue working.
- Monitor conversions and important user journeys.
- Review performance across representative page types.
- Resolve persistent technical or content-related problems.
- Continue monitoring throughout the following weeks and months.
The checklist should be adapted to the migration. A domain change, for example, involves additional considerations compared with a redesign that retains the same domain and URLs.
Frequently asked questions about website migration SEO
Is website redesign SEO different from website migration SEO? 
Website redesign SEO focuses on maintaining and improving search performance during a redesign.
Website migration SEO covers a wider range of changes, including CMS migrations, domain moves, URL restructuring and content consolidation.
The two often overlap when an organisation replaces an existing website.
Should pages with little traffic be migrated?
Traffic shouldn’t be the only consideration.
Some pages serve important organisational purposes or attract a small number of highly relevant enquiries. Assess their usefulness, accuracy, search performance and whether suitable replacement content exists.
Should I change URLs during a website redesign?
Only where there is a good reason.
Improving an unclear or restrictive URL structure can be worthwhile, but changing established URLs without a clear benefit adds unnecessary migration work.
Do I need 301 redirects when redesigning a website?
Permanent redirects are generally needed when existing URLs are permanently replaced with new addresses.
If a redesign retains the same URLs, redirects may not be necessary for those pages.
How long does SEO take to recover after a website migration?
There is no fixed recovery period.
Some changes may be processed relatively quickly, while larger migrations can take weeks or months to settle. The outcome depends on the scale of the migration, the quality of its implementation and whether important content and technical signals have been preserved.
Does migrating a website affect SEO?
It can. Changes to URLs, content, internal links and technical settings may influence how search engines crawl, index and rank a website.
Careful planning helps protect existing visibility and reduce avoidable disruption.
Protecting search visibility starts before development
Website migration SEO works best when it’s included in the project from the beginning.
Auditing existing performance, reviewing content, planning redirects and agreeing technical requirements all help reduce risk before the replacement website reaches launch.
The objective isn’t simply to preserve rankings. It’s to retain what already works while creating a website that better supports your organisation and the people using it.
At Feel Created, we approach website redevelopment as a connected process involving strategy, content, UX, development and technical optimisation. That means considering existing search performance alongside the wider improvements a new website needs to deliver.
Whether you’re replacing an ageing CMS, reorganising a large website or planning a complete redevelopment, involving SEO early gives the project a stronger starting point.
Planning a website redevelopment? Talk to Feel Created about building a website that protects your existing investment while supporting what comes next.