A redesign can make a website clearer, faster and easier to use, but it can also remove useful content or break routes that customers and search engines rely on. Protecting SEO starts before design approval, with an inventory of what the existing site does well and a plan for anything that changes.
No agency can guarantee that rankings will stay completely still through a major change. The practical goal is to avoid preventable losses, preserve useful signals and identify problems quickly. Google's site migration guidance explains that search visibility can fluctuate while changed pages are crawled and processed.
Record a meaningful baseline
Before the build, save a list of existing URLs and the information needed to assess them. Include page titles, headings, indexing settings, canonical URLs and response codes. Add available Search Console and analytics information, keeping the date range and filters with the export.
Look beyond the homepage. A service page, product category or older guide may bring in useful visits even if nobody in the business talks about it. Identify pages that attract enquiries, sales, relevant searches or valuable external links. Those deserve deliberate decisions rather than being lost during a content tidy-up.
Compare appropriate periods. A seasonal business should not judge a launch simply by comparing a quiet month with its busiest month. Keep a record of other changes, including campaigns and tracking settings, so later differences are not automatically attributed to the redesign.
Keep good URLs when there is no reason to change them
A new visual design does not require new page addresses. If a clear URL already represents the same service, keeping it can reduce migration work and avoid unnecessary redirects. Change URLs when there is a useful structural reason, rather than to make the project feel newer.
Page names in a menu and page addresses are separate decisions. You can simplify navigation without rewriting every URL. During website design, assess the information architecture alongside the existing search evidence so the new structure serves both established and new visitors.
Map every important old page to an outcome
Create a migration sheet with an old URL, proposed destination and reason. Some pages stay where they are. Others move to a close equivalent. Some may be combined into a stronger resource. A page with no suitable replacement may need to be removed properly.
For example, if two overlapping service pages become one genuinely comprehensive service page, both old routes may have a relevant new destination. An obsolete event page does not automatically belong on the homepage. A visitor following an old link should reach information that makes sense for the original intent.
Avoid sending every removed URL to the homepage. That is rarely useful to a visitor and can be treated as an error by search systems. Record decisions before launch so redirect rules follow the content plan, rather than being improvised after traffic drops.
Use appropriate redirects and update your own links
When a page permanently moves, Google recommends a permanent server-side redirect where possible. Its redirect documentation explains the distinction between permanent and temporary moves. The implementation depends on the platform and hosting, and should be tested against the mapping sheet.
Check that each old route reaches the intended final page without loops or unnecessary chains. Test variations that people actually use, such as the preferred hostname and HTTPS address. Keep useful redirects in place after launch, and document them so a future hosting change does not silently remove them.
Update internal links to point directly to the final pages. That includes navigation, contextual links, breadcrumbs, article references and links in structured data. Where practical, update important business profiles and campaign destinations too.
Preserve the information people came for
A redesign is a chance to improve content, but removing detail just to create a cleaner layout can weaken the page. Keep accurate service explanations, useful specifications, clear location information and genuine supporting evidence. Improve how they are organised rather than assuming shorter always means better.
Work with your SEO plan to decide which topics belong on each page. Avoid turning distinct services into near-identical pages, or combining unrelated information into one page because the template is convenient. The content should still answer the customer's question after the visual style changes.
Test the staging site and launch settings
A staging site should be protected from unintended public discovery, but those controls need deliberate handling at launch. Check the production robots rules, page-level indexing directives and canonical URLs. A beautifully rebuilt website can struggle if the live pages still identify a test domain or tell crawlers not to index them.
- Confirm important pages return the intended status and are accessible without a login.
- Check titles, main headings, descriptions and meaningful image text alternatives.
- Verify mobile navigation, forms, search and relevant checkout journeys.
- Test sitemap contents against the final canonical, indexable URLs.
- Confirm analytics and agreed conversion measurement are operating on the right domain.
- Keep a recoverable before copy and a defined rollback route.
Our development work includes the behaviour behind the new pages. A migration check should cover real user journeys and integrations, rather than only a scanner score or a handful of screenshots.
Choose a launch window with support available
Arrange the release when the people responsible can check it and respond. A late-Friday switch may be inconvenient if the business takes weekend bookings and the relevant supplier is unavailable. Agree who can approve a rollback and what evidence would trigger it. That decision is easier to make before there is pressure from a live fault.
Monitor the release with a clear record
After launch, check important old and new URLs directly. Review server errors, redirects, indexing and the sitemap response. Google's Search Console overview explains the tools available for monitoring search performance and indexing.
Compare page groups and relevant queries over suitable periods. A fall affecting one redirected section needs a different investigation from a site-wide change. Do not make repeated large edits before you understand the evidence; that makes it harder to identify the original cause.
A useful handover includes the URL map, release date, test results, recovery information and responsibilities for follow-up. Our ongoing care can support the site after launch, while a redesign proposal should make the migration work explicit from the outset. Talk to us before rebuilding if the existing site already supports important enquiries or sales.