Website Redesign SEO Checklist: How to Protect Rankings and Traffic

Redesigning a website can improve almost everything about it.

You can create a clearer brand, improve navigation, modernize the design, make the website easier to manage, improve mobile usability, strengthen conversion paths and remove years of accumulated clutter.

But if the existing website already receives traffic from Google, there is another consideration that cannot be left until launch day:

SEO.

A successful redesign should improve the website without accidentally throwing away the search visibility the old site has built over the years.

That does not mean every heading, paragraph or URL must remain frozen forever.

A redesign is often the right time to improve poor content, simplify the structure and remove pages that no longer serve a purpose.

The important part is knowing what you are changing, why you are changing it and what SEO signals need to be preserved or redirected.

At Ray Creations, we prefer to treat SEO as part of the redesign plan rather than something that gets checked after the new website goes live.

This website redesign SEO checklist explains how.

If you are still deciding whether the website needs a full rebuild in the first place, our guide to signs it may be time to redesign your website is a useful place to start.

Does a Website Redesign Automatically Hurt SEO?

No.

A redesign by itself does not automatically cause rankings to fall.

If the URLs, content, internal linking and technical signals remain largely intact, a visual redesign may have relatively little effect on search visibility.

The risk becomes greater when the redesign also involves changes such as:

• new URLs;
• different site structure;
• moving to another CMS;
• rewriting large amounts of content;
• removing pages;
• changing domain;
• changing navigation;
• changing internal links;
• changing canonical tags;
• moving images or downloads;
• altering how important content is rendered.

At that point, the project is no longer merely a visual redesign.

It is also a website migration.

Google may need time to recrawl and reassess substantial changes, particularly when URLs or site structure change.

The objective of good redesign SEO is therefore not:

Prevent Google from noticing that anything changed.

The objective is:

Make it easy for users and search engines to understand what changed and where everything now belongs.

What Can Go Wrong With SEO During a Website Redesign?

Most redesign SEO problems are surprisingly ordinary.

An important page gets forgotten during migration.

A URL changes without a redirect.

The staging site’s noindex setting remains enabled after launch.

Internal links continue pointing through old URLs.

Canonical tags point to the development domain.

A navigation change leaves important pages buried.

A high-performing page gets replaced by two paragraphs of marketing copy.

A contact form looks fine but stops submitting.

Analytics disappear during the theme change.

An old page with valuable backlinks is deleted because nobody checked whether it had search value.

Individually, these are small mistakes.

Across several hundred pages, they can become a serious SEO problem.

That is why the safest approach starts before the new website is built.

Our broader website planning guide explains why structure, content and business goals should be decided before visual design takes over the project.

Before the Redesign: Establish Your SEO Baseline

1. Back Up the Existing Website

Before changing anything, make sure there is a complete usable backup of the current website.

For a CMS such as WordPress, that normally means:

• website files;
• database;
• uploaded media;
• important configuration;
• any custom code.

A backup is primarily a recovery measure.

The new website should not depend on the old hosting account continuing to remain available indefinitely.

And as we discuss in our guide to updating WordPress safely, merely having a backup is not enough.

You should know:

• where it is;
• what it contains;
• how recent it is;
• how it could actually be restored.

2. Crawl or Inventory the Existing Website

Before redesigning a website with established search visibility, create a list of its current URLs.

For a small website, this may be manageable manually.

For a larger site, use:

• the XML sitemap;
• the CMS;
• a site crawler;
• Google Search Console;
• analytics;
• server logs where appropriate.

The objective is to create an inventory of the pages that exist before migration.

This becomes one of the most valuable documents in the redesign project.

For each important URL, you can then decide:

• keep the URL;
• move it;
• merge it;
• replace it;
• retire it.

Without this list, pages tend to disappear accidentally.

3. Identify the Pages That Already Matter

Not every URL has equal SEO value.

Before redesigning, identify pages that currently receive:

• organic clicks;
• impressions;
• conversions;
• external links;
• internal links;
• important keyword rankings.

Google Search Console is particularly useful here.

A page with only a handful of monthly visits may still be important if it ranks for a commercially valuable query or has strong backlinks.

Conversely, a page that exists in WordPress but has never attracted traffic, links or useful engagement may not deserve the same preservation effort.

This is why we would not recommend blindly copying every old page simply because it exists.

Preserve value, not clutter.

If search visibility is a major part of the redesign, it also makes sense to involve SEO thinking before development begins rather than after launch. Our Search Engine Optimization service follows the same principle: understand what is already working before changing the structure around it.

4. Record Important On-Page SEO Elements

For pages worth protecting, retain a record of useful information such as:

• current URL;
• page title;
• meta description;
• H1;
• main content;
• canonical;
• indexability;
• structured data;
• important internal links;
• image URLs where relevant.

You do not necessarily have to reproduce every one of these exactly.

But you should know what was there before replacing it.

That distinction matters.

A redesign should involve intentional changes, not accidental losses.

Create an Old-to-New URL Map

If any URLs are changing, create a redirect map before launch.

A simple spreadsheet can contain:

Old URL	New URL	Action
/old-service/	/new-service/	301
/service-a/	/services/service-a/	301
/obsolete-page/	—	404/410
/important-page/	Same	No change

This map becomes the foundation of the migration.

Keep Existing URLs Where It Makes Sense

Changing a design does not mean URLs must change.

If an existing URL:

• is clear;
• already ranks;
• has backlinks;
• still represents the same topic;

there may be little reason to replace it.

For example, if:

/industrial-web-design/

already represents the same industrial web design service after the redesign, changing it simply because the website is new creates unnecessary migration work.

On the other hand, an ugly or misleading legacy structure may justify improvement.

The point is not:

Never change URLs.

It is:

Do not change URLs without a reason and a migration plan.

Use Proper Permanent Redirects When URLs Change

When a page moves permanently, redirect the old URL to the most relevant new URL.

Server-side permanent redirects such as 301 or 308 are generally the appropriate choice.

But redirects still need to be implemented correctly.

Redirect Old Pages to Their True Replacements

If:

/old-web-design/

becomes:

/custom-website-design/

redirect the old URL directly to the new page.

Do not redirect every removed page to the homepage simply because the homepage exists.

The destination should make sense for the user arriving through the old URL.

If you are rebuilding the site around a new design and structure, this is one of the areas we handle as part of Custom Website Design rather than treating redirects as an afterthought.

Avoid Redirect Chains

Avoid:

Old Page → Temporary Page → New Page

when you can simply use:

Old Page → New Page

Redirect chains:

• add unnecessary requests;
• slow users down;
• complicate troubleshooting;
• make migrations harder to maintain.

If old redirects already exist, update them wherever practical so they point directly to the final destination.

This is something we pay particular attention to during older website rebuilds because sites frequently accumulate several generations of redirects.

Do Not Redirect Pages That Have No Replacement

Sometimes a page genuinely deserves to disappear.

Perhaps it covers:

• an obsolete service;
• an expired promotion;
• outdated software;
• a discontinued product;
• content that no longer has any useful equivalent.

If there is no relevant replacement, returning a real 404 or 410 may be more appropriate than forcing the visitor onto an unrelated page.

Before deleting the URL, however, check whether it has meaningful:

• traffic;
• backlinks;
• conversions;
• search impressions.

Sometimes the better option is to rebuild the page.

Sometimes it is to merge its useful content into another page and redirect it there.

And sometimes the right answer is simply to retire it.

Protect the Staging Website From Accidental Indexing

A redesign is usually built somewhere separate from the live website.

That might be:

• a staging domain;
• subdomain;
• temporary hosting location;
• private development environment.

You do not want the unfinished copy competing with the current site in search results.

The safest approach is generally to keep the development environment inaccessible to the public and search engines, for example through authentication.

A noindex directive can also be used where appropriate.

What we would not recommend is assuming that a robots.txt disallow rule alone guarantees that development URLs can never appear in search.

And this creates one of the most important launch checks:

Make absolutely sure staging restrictions do not carry over to production.

Leaving a production website with a staging noindex rule is one of the more painful redesign mistakes because the new site can look completely normal to visitors while telling search engines not to index it.

Preserve Important Content — But Do Not Be Afraid to Improve It

An old SEO rule is sometimes interpreted as:

Never change content during a redesign.

That is too simplistic.

If an existing page ranks well and converts well, changing its:

• purpose;
• primary topic;
• useful content;
• title;
• internal links;

all at once introduces unnecessary uncertainty.

So for high-performing pages, restraint often makes sense.

But what if an existing page is thin, outdated or performing badly?

Then preserving poor content simply because it is old makes little sense.

A redesign can be an excellent opportunity to improve it.

The important distinction is between:

intentional improvement

and

accidental content loss.

If a 2,000-word service page explaining a complex offering becomes a 150-word visual page because the new design prefers large photographs, that may substantially change what search engines and users can understand about the page.

The visual redesign should support the content strategy rather than silently replace it.

Preserve Search Intent on Important Pages

When rebuilding a page that already performs in search, ask:

What question or need was this page satisfying?

A redesign may change:

• layout;
• fonts;
• blocks;
• visuals;
• CMS;
• templates;

without changing that underlying purpose.

For example, if a page ranks for:

industrial website design

then the rebuilt page should still clearly be about industrial website design unless you have deliberately decided to change its SEO strategy.

Do not accidentally turn a focused page into a generic company page.

That is particularly important when redesigns are driven primarily by visual mockups.

Beautiful design cannot compensate for a page whose subject has become unclear.

Review Page Titles and Meta Descriptions

Existing page titles do not have to remain permanently unchanged.

But high-performing titles should not be casually replaced simply because the new website is launching.

Before changing them, ask:

• What queries does this page already receive impressions for?
• Does the existing title reflect those queries?
• Is the title outdated?
• Is the search intent changing?
• Is there a real opportunity to improve CTR or relevance?

The same applies to meta descriptions.

Descriptions are not something we would preserve blindly, but there is little benefit in losing carefully written metadata simply because nobody transferred it into the new CMS.

Migration should be deliberate.

Check Heading Structure

The H1 and supporting headings help communicate page structure to both users and search engines.

You do not need identical HTML markup between old and new designs.

But make sure the rebuilt page still has:

• a clear H1;
• logical H2/H3 structure;
• headings that describe the content beneath them.

A redesign should improve information hierarchy, not reduce it.

Preserve and Improve Internal Linking

Internal linking is one of the easiest things to lose during a rebuild.

Old pages may contain useful contextual links between:

• services;
• related articles;
• industries;
• supporting resources;
• conversion pages.

When content is manually migrated or rewritten, those links can disappear.

Navigation changes can also affect how deeply pages sit within the website.

Before launch, review:

• primary navigation;
• footer links;
• contextual links;
• breadcrumbs;
• related content;
• category relationships.

If URLs changed, update the internal links to point directly to the new URLs rather than leaving them pointing through redirects.

This is also why the website’s information architecture should be planned before development. A clearer structure benefits both users and search engines.

Review Canonical URLs

Canonical tags deserve special attention during redesigns.

Development sites sometimes contain canonicals pointing to:

• the staging domain;
• old URLs;
• temporary URLs.

After launch, important pages should normally use the correct production canonical.

For a standard unique page that you want indexed, that will commonly be a self-referencing canonical.

This is not something we leave to chance during migration.

Review Structured Data

If the old website contains structured data, make sure important markup survives the redesign where appropriate.

Examples might include:

• Organization;
• Article;
• Breadcrumb;
• Product;
• LocalBusiness;
• other page-specific schema.

A different theme or CMS may generate structured data differently.

After launch, test representative pages rather than assuming the old markup automatically carried over.

Keep Images and Other Search Assets in Mind

Website migrations do not involve only HTML pages.

Images, PDFs and other assets may also have:

• search visibility;
• backlinks;
• traffic.

If an important image or downloadable file moves, consider whether its old URL should redirect too.

Also preserve useful:

• file names where practical;
• alt text;
• image context.

This is particularly relevant for websites with portfolios, product photography, diagrams, project galleries or downloadable resources.

Make the Redesign Mobile-Friendly

A modern redesign should work well across screen sizes from the beginning.

That includes more than stacking desktop columns vertically.

Check:

• navigation;
• tap targets;
• forms;
• font sizing;
• heading wrapping;
• image cropping;
• tables;
• buttons;
• interactive elements;
• content order.

Our Responsive Web Design approach follows the same principle: responsive behaviour should be part of the design system, not an emergency adjustment after the desktop version is complete.

Improve Performance Without Breaking Functionality

A redesign often introduces new:

• scripts;
• animations;
• fonts;
• videos;
• sliders;
• tracking tools;
• page-builder assets.

Individually, each may seem harmless.

Together, they can make the new website considerably heavier than the old one.

Before launch, compare important page types and check:

• loading performance;
• image optimization;
• caching;
• unnecessary scripts;
• third-party tools;
• layout stability.

Do not sacrifice usability and functionality merely to chase a perfect performance score.

But equally, do not assume a visually modern site is automatically technically better.

Check Analytics and Conversion Tracking

SEO traffic is useful only if you can measure what it does.

A redesign can accidentally remove or change:

• Google Analytics;
• Google Tag Manager;
• conversion events;
• advertising pixels;
• form tracking;
• call tracking;
• ecommerce tracking;
• consent settings.

Record the existing measurement setup before migration.

Then verify it again after launch.

Without that step, you could mistakenly conclude that organic conversions disappeared when the real problem is that tracking disappeared.

Test Forms and Business-Critical Functionality

This deserves its own place in an SEO redesign checklist because losing organic traffic is not the only way a redesign can cost money.

Imagine rankings remain unchanged, but the new contact form stops sending notifications.

From an SEO dashboard, everything may look fine.

From the business’s perspective, the website has failed.

Before launch, test:

• contact forms;
• quotation forms;
• newsletter signups;
• checkout;
• payments;
• booking systems;
• logins;
• downloads;
• CRM integrations;
• transactional emails.

For many service businesses, I would consider a successful form submission more important than a minor SEO score difference.

And if a website looks good after a redesign but still produces very few enquiries, the problem may lie elsewhere in the conversion journey. Our guide to why a website may not be generating leads covers those wider issues.

Website Redesign SEO Checklist Before Launch

Before the new website replaces the old one, run through this checklist.

Indexing and crawling

• Is the production website indexable?
• Have staging noindex rules been removed?
• Is robots.txt appropriate for production?
• Are important pages accessible to search engines?

URLs

• Is the old URL inventory complete?
• Have unchanged URLs stayed unchanged where sensible?
• Does every changed important URL have a mapped destination?
• Are permanent redirects ready?
• Are redirects pointing directly to their final destination?
• Are unrelated deleted pages returning proper 404/410 responses?

On-page SEO

• Are important page titles present?
• Are meta descriptions present?
• Does each page have an appropriate H1?
• Is important content present?
• Have important contextual links survived?

Technical signals

• Are canonical tags correct?
• Is structured data working?
• Are breadcrumbs working?
• Are image URLs and alt text appropriate?
• Is the XML sitemap correct?

Functionality

• Do forms submit?
• Do emails arrive?
• Does ecommerce work?
• Do logins work?
• Do third-party integrations work?
• Does analytics work?

UX and performance

• Does the site work properly on mobile?
• Is navigation intuitive?
• Are important pages easy to reach?
• Are there obvious layout problems?
• Is performance acceptable?

SEO measurement

• Is Search Console verified?
• Is analytics collecting data?
• Have baseline rankings and organic traffic been recorded?

Do not wait until after launch to answer these questions.

Launching the Redesigned Website

Avoid Changing Everything at Once Where Possible

Simultaneously changing:

• domain;
• CMS;
• site architecture;
• design;
• URL structure;

makes troubleshooting much more difficult if visibility changes afterwards.

Sometimes a project genuinely requires several changes together.

But where you have a choice, reducing the number of moving parts makes the migration easier to understand and monitor.

Launch During a Sensible Traffic Period

If the website has predictable low-traffic periods, launching then can make sense.

You are giving the team time to identify problems while fewer users are affected.

That does not mean launching at 3 AM simply because nobody is awake.

You want the appropriate developers and decision-makers available if anything needs attention.

Immediately After Launch

1. Crawl the New Website

Compare the new site against the pre-launch inventory.

Look for:

• missing pages;
• broken links;
• incorrect status codes;
• redirect chains;
• unexpected noindex tags;
• incorrect canonicals;
• orphaned pages.

The old-site crawl and the new-site crawl should tell a coherent story.

2. Test Important Redirects

Do not merely check that a redirect happens.

Check that:

Old URL → correct final URL

and preferably in one permanent redirect.

Pay special attention to:

• highest-traffic pages;
• pages with backlinks;
• old landing pages;
• old service URLs.

3. Submit the Updated XML Sitemap

Once the production site is live and its URLs are correct, submit the sitemap in Google Search Console.

This helps Google discover the new site structure and URLs.

4. Inspect Important URLs

Use Search Console’s URL Inspection tool on representative high-value pages.

Check:

• crawl availability;
• indexability;
• canonical;
• rendered content.

You do not need to manually request indexing for every page on a large website.

Start with the most important URLs and make sure the overall technical setup is correct.

5. Use Change of Address When the Domain Changes

If the redesign also moves the website to a different domain or subdomain, additional migration steps apply.

A normal redesign on the same domain does not require this.

Monitor SEO After the Website Redesign

A redesign SEO project does not end when the website goes live.

For the following days and weeks, monitor:

• organic clicks;
• impressions;
• rankings;
• indexed pages;
• crawl errors;
• 404s;
• conversions;
• important landing pages.

If URL structures changed substantially, some temporary search fluctuations may occur while search engines recrawl and process the migration.

The key is to distinguish a normal transition from an actual migration problem.

What Should You Do If Rankings Drop After a Redesign?

Do not immediately start rewriting everything again.

That adds another layer of change while you are trying to understand the first one.

Start systematically.

Check whether the pages are indexed

Use Search Console.

If an important page disappeared from the index, investigate:

• noindex;
• robots;
• canonical;
• redirects;
• server response;
• rendering.

Check the old URLs

Are they redirecting to the correct destinations?

Did important redirects get missed?

Are there chains?

Are several unrelated pages being redirected to one generic page?

Compare old and new content

Did the redesign remove:

• important sections;
• headings;
• supporting copy;
• FAQs;
• internal links;
• images?

Has the page’s subject changed substantially?

Check internal links

Did navigation or content migration make important pages harder to discover?

Do old internal links still go through redirects?

Check canonicals

A staging canonical copied into production can cause serious confusion.

Check server errors and performance

Are search engines or visitors encountering:

• 5xx errors;
• timeouts;
• broken assets;
• very slow pages?

Check query-level Search Console data

Do not look only at overall traffic.

Identify:

• which page lost visibility;
• which queries changed;
• whether impressions fell;
• whether position fell;
• whether another URL started appearing instead.

That often points directly towards the problem.

How Long Should You Keep Redesign Redirects?

Do not remove them immediately after search engines discover the new pages.

For major migrations, keeping redirects for at least a year is a sensible minimum, and from the user’s perspective keeping useful redirects indefinitely can often make sense.

Why?

Because old URLs may still exist in:

• external backlinks;
• bookmarks;
• old emails;
• documents;
• social posts;
• historical search indexes.

A redirect continues helping those visitors long after the redesign itself is forgotten.

Redesigning a Website Without Losing SEO Is Mostly About Preparation

There is no magic setting that preserves search visibility during a redesign.

The process is primarily about maintaining continuity.

Know what exists.

Know what currently has value.

Know what is changing.

Map old URLs to new URLs.

Preserve important content and intent.

Redirect intelligently.

Update internal links.

Check technical signals.

Test the new website.

Monitor it after launch.

Most serious redesign SEO problems are preventable when those decisions happen before launch rather than after rankings disappear.

The Website Redesign Process We Prefer

When working on an existing website, we like to keep the live and development versions available side by side during the build whenever practical.

That makes it much easier to compare:

• pages;
• content;
• navigation;
• URLs;
• functionality.

Before migration, we want to know which existing URLs are staying and which are changing.

If URLs change, we would rather have the redirect map prepared before launch than discover missing pages from Search Console afterwards.

Then after launch, the work is not considered finished simply because the homepage looks correct.

We check important pages, redirects, forms, mobile behaviour, analytics and indexing signals.

It is not particularly glamorous work.

But that is exactly why it is valuable.

A good redesign should feel exciting to the business and almost boring from a migration perspective.

If you are unsure whether your existing website is ready for a redesign or simply needs targeted improvements, our Site Review Request gives us a way to examine the current site’s structure, usability, content and technical issues before recommending a larger rebuild.

Final Thoughts

A website redesign should make the website better.

Better for visitors.

Better for the business.

Better to use.

Better to maintain.

And ideally better for search too.

SEO should not become a reason to remain trapped forever in an outdated website.

The answer is not to avoid redesigning.

It is to redesign with an understanding of the search value the existing website has already earned.

Keep strong URLs where appropriate.

Improve weak content deliberately.

Protect valuable pages.

Use proper redirects when things move.

Verify canonicals, indexability and internal links.

And monitor the site after launch rather than assuming everything worked because the new design looks good.

If your existing website is reaching the point where a redesign may be necessary, our guide to signs it is time to redesign your website can help you decide whether the problem is primarily visual, technical, usability-related or strategic.

For broader planning before a rebuild, see our Website Planning Guide.

And if the redesign is driven by poor enquiry performance rather than appearance alone, first read Why Your Website Is Not Getting Leads. Sometimes the problem requires a redesign; sometimes it does not.

At Ray Creations, our aim with a redesign is not simply to replace the old website with something newer.

It is to understand what is already working, protect what deserves to be protected, improve what needs improvement and launch the new site with as little unnecessary disruption as possible.