Website Redesign SEO: Protect Rankings When You Relaunch

A website redesign can improve your brand, simplify navigation and make enquiries easier. It can also remove the pages people find through Google, break valuable links or accidentally block search engines. Website redesign SEO means protecting what already works while improving what does not. Use this checklist before design begins, during development and after launch—not just when traffic drops.

1. Record what your current website is doing well

Before changing your website, save a baseline. Without one, you cannot reliably tell whether the redesign improved performance or introduced a problem.

Use Google Search Console to review search clicks, impressions, queries and landing pages. In your analytics platform, check organic landing-page visits and meaningful actions, such as completed enquiry forms or bookings. Compare a representative period, accounting for seasonal demand where possible.

Build a spreadsheet with one row per important URL. Include:

• Page purpose: which service, question or audience it serves.
• Search performance: relevant queries, clicks and impressions.
• Business value: enquiries, bookings or other tracked outcomes.
• Existing signals: page title, main heading, canonical URL and indexability.
• Planned action: keep, improve, merge or remove.

Include pages that receive worthwhile links from other websites, even if their current traffic is modest. Also save a crawl or inventory of your existing URLs and take a full website backup.

Do not judge pages by traffic alone. A specialist service page may attract few visitors but generate relevant enquiries. A popular article may support awareness without directly producing sales. Both can deserve a place in the new site.

If you need an initial audit, search engine optimisation support can help identify which pages and technical settings need protection.

2. Plan your URLs and redirects before development

Changing a page’s design does not require changing its address. Keep existing URLs when they remain accurate and useful. Renaming every page for a cleaner-looking structure creates unnecessary migration work.

Where URLs must change, create a redirect map. This is a spreadsheet matching each old address to its most relevant new destination, with a reason for the change.

Match pages by purpose, not convenience

Suppose your old website has a page at /corporate-video/ and the new site uses /services/corporate-video-production/. A permanent server-side redirect, usually a 301, should send visitors and search engines directly from the old page to the new equivalent.

Do not redirect every removed URL to the homepage. Someone following a link about corporate filming expects that service, not a general introduction. Unrelated redirects can confuse visitors and may be treated as soft 404s by search engines.

• If an equivalent page exists, redirect to it.
• If several pages are merged, ensure the destination genuinely covers their useful content.
• If a page has no suitable replacement, a proper 404 or 410 response may be appropriate.
• If the URL stays unchanged, no redirect is needed.

Avoid redirect chains: the old URL should reach the final destination in one step wherever possible. Update internal links to point directly to the new address rather than relying on redirects.

Keep useful redirects in place long term. Google generally recommends retaining redirects for at least a year during site moves; valuable external links and bookmarks may justify keeping them longer.

3. Improve the design without removing useful content

A common redesign mistake is replacing specific, helpful content with short slogans. The new page may look tidier while no longer answering the questions that brought visitors there.

For each priority page, preserve or improve its main purpose. Explain what you offer, who it suits, how the process works and what the visitor should do next. Retain useful examples, relevant project details and genuine answers to buying questions.

This does not mean keeping every paragraph. Remove repetition and outdated information. Keep page titles and main headings clear, and make substantial content changes deliberately rather than accidentally during layout work.

Check templates as well as individual pages

A template error can affect your entire website. During website development, check that:

• Important text and links are accessible to search engines, including on JavaScript-heavy pages.
• Each indexable page has an appropriate title and a clear main heading.
• Canonical tags identify the intended live URLs, not the staging domain.
• Navigation and contextual links make priority pages easy to reach.
• Images are compressed, and informative images have useful alternative text.
• Structured data, where used, matches the visible content and remains valid.

Test mobile layouts carefully. Oversized videos, shifting elements and difficult menus can undermine an otherwise attractive redesign. Check page experience using tools such as PageSpeed Insights, but prioritise real usability rather than chasing a perfect score.

If embedded video matters to a service page, retain the supporting explanation and a clear next step. A video should strengthen the page, not replace all its useful written information.

4. Run a launch checklist on the production website

Protect the staging website from public indexing, preferably with authentication. A noindex instruction can provide additional protection, but search engines must be able to crawl a page to see it. Do not assume a robots.txt block alone prevents indexing.

Before launch, agree who owns redirects, technical checks, analytics and final approval. Then test the live website, not just the development version.

1. Check indexability. Remove unintended noindex instructions and confirm robots.txt does not block important public pages or required resources.
2. Test priority URLs. Important pages should load successfully, while old addresses should redirect to the correct destinations.
3. Inspect canonical tags. They should reference the preferred live URLs and use the correct domain and protocol.
4. Check the XML sitemap. Include intended, indexable canonical URLs that return successful responses, then submit it in Search Console.
5. Test business actions. Submit forms, check booking journeys and verify that confirmation messages and notifications work.
6. Verify measurement. Confirm analytics and conversion tracking operate as intended, with consent controls appropriate to your requirements.
7. Crawl the live site. Look for broken internal links, unexpected redirects, missing metadata and server errors.

Launch when your team can monitor and fix issues. Keep backups and a documented rollback plan, but assess problems before reverting: repeated switches between versions can create further inconsistencies.

5. Monitor visibility and enquiries after launch

Some search fluctuation can follow a substantial redesign. However, a sudden decline across important pages deserves investigation rather than an automatic assumption that everything will recover.

Check critical journeys immediately after launch and review technical issues frequently during the first few days. Over subsequent weeks, compare Search Console and analytics data with your baseline.

Start with three questions:

• Can search engines access the pages? Check indexing reports, URL Inspection and server responses.
• Are the right pages receiving visibility? Compare priority landing pages and relevant search queries.
• Can visitors still enquire? Check forms, mobile usability and conversion tracking.

If reported traffic falls but Search Console clicks remain stable, investigate measurement changes before rewriting content. If particular pages lose visibility, inspect their redirects, canonical tags, internal links and content changes.

Avoid changing everything at once in response to a short-term movement. Fix confirmed faults first, record what changed and assess patterns over comparable periods. Recovery timing varies; no responsible agency can promise an exact date.

Frequently asked questions

Will redesigning my website automatically hurt SEO?

No. A redesign can improve usability, content and technical performance. Risk increases when important URLs, content or indexing settings change without planning. An audit, redirect map and launch checks help reduce avoidable disruption.

Should I change my domain during a redesign?

Only when there is a clear business reason. Changing the domain, platform, structure and content together makes troubleshooting harder. If a domain move is necessary, plan redirects carefully and follow Google’s applicable site-move guidance.

How long should I monitor SEO after launch?

Check technical essentials immediately and monitor closely over the following weeks. Larger migrations may require longer observation. Keep ongoing reporting in place so you can distinguish launch issues from seasonality, competition and normal search changes.

Planning a redesign? Filtershots can help align design, development and SEO before your new website goes live. Discuss your website project and build a launch plan around the pages and enquiries that matter.