Website Redesign SEO: A Checklist to Keep Your Rankings

Website redesign SEO is the work of changing how a site looks and is built without losing the search traffic it already earns. The core steps are a baseline, a full URL inventory, a 301 redirect map, preserved titles and content, correct canonicals and hreflang, and monitoring after launch. The same steps are the core of website migration services when a site moves to a new platform or domain.

A redesign that changes URLs, rewrites content or drops metadata can push pages out of Google's results. Repeatable steps before, during and after launch prevent that.

Why do rankings drop after a redesign?

Search engines rank individual pages, identified by their URLs. A redesign puts those pages at risk in a few predictable ways:

• URLs change and the old ones return errors instead of redirecting.
• Content is removed or rewritten so a page no longer answers the query it ranked for.
• Titles, headings and metadata are lost when templates change.
• Internal links break or point at old addresses, so authority no longer flows where it should.
• Pages become hard to crawl because of blocked resources, heavy scripts or a new navigation that hides content.
• The site gets slower after a heavier design.
• Staging settings reach production, such as a noindex tag or a robots.txt that blocks everything.

Every item on the checklist below prevents one of these. Our wider guide on website redesign services explains how this fits into the full redesign process.

What goes into a website redesign checklist?

Work through these in order. The first four happen before a single page is rebuilt.

1. Capture a baseline

You cannot judge the result without knowing the starting point. Before any change:

• Export performance data from Google Search Console: queries, pages, clicks and impressions.
• Export organic traffic and conversions per page from your analytics tool.
• Record rankings for your most important keywords.
• Run a crawl of the current site and save it.

This baseline tells you after launch whether the migration worked. An SEO audit of the current site gives you the same baseline with its problems ranked.

2. Build a complete URL inventory

List every URL on the current site. Combine three sources so nothing is missed: a crawl of the site, the sitemap, and the pages that appear in Search Console and analytics. Add any pages with backlinks. For each URL record its title, main heading, traffic, links pointing to it and whether it should stay, change, merge or go.

Pages that earn traffic or links are the ones to protect. Pages that earn nothing and say nothing are candidates for removal, but decide that deliberately, with data.

3. Decide what stays, what changes and what goes

For each URL choose one outcome:

• Keep as is. The address and the content stay. This is always the safest option for a page that ranks.
• Keep the content, change the address. Needs a 301 redirect.
• Merge into another page. Redirect to the page that now covers the topic.
• Remove. Redirect to the closest relevant page when one exists. If no relevant page exists, a 404 or 410 is acceptable.

The simplest way to cut risk is to change fewer URLs. If the existing structure works, keep it.

4. Create the 301 redirect map

The redirect map is a table of old URL to new URL. Google explains when and how to use permanent redirects in its documentation. A few rules make it reliable:

• Send each old URL to the closest equivalent page, not to the homepage. Redirecting everything to the homepage is often treated like an error by search engines.
• Avoid chains. If A redirects to B and B redirects to C, point A straight to C.
• Include variants: with and without trailing slash, http and https, with and without www, and uppercase or lowercase versions if they existed.
• Keep redirects in place long term. Removing them after a few weeks throws away the signals they carry.
• Test the full map on staging before launch.

5. Keep content, titles and headings that perform

Rewrite for clarity, but keep the substance of pages that rank. Preserve the main heading, the topics covered and the title tag unless you have a reason to change them. A page that ranks for a query keeps ranking when the new version still answers that query at least as well. Improve a page by adding to it.

Check that metadata carries over: title tags, meta descriptions, heading structure, image alt text and structured data. Templates are where this usually breaks.

6. Set canonical tags correctly

Each indexable page needs a canonical tag that points to its own preferred URL. On the new site, check that:

• canonicals point at the new, final addresses, never at staging or old URLs;
• parameter and filter versions point to the main page;
• no page canonicalizes to a redirecting or erroring address.

A wrong canonical can tell Google to ignore the page you want ranked. Google's guide to consolidating duplicate URLs covers the canonical methods.

7. Handle hreflang on multilingual sites

If the site has more than one language or regional version, hreflang annotations tell search engines which version belongs to which audience. During a redesign:

• every language version must list all its alternates and itself, as Google's guide to localized versions describes;
• the references must be reciprocal, so each page points to the others and they point back;
• the URLs in hreflang must be the final new addresses, and each must return a normal page;
• language and region codes must be valid.

Broken hreflang is a common casualty of redesigns, because the annotations live in templates or plugins that change with the platform.

8. Rebuild internal linking

Internal links carry authority between pages. After the redesign:

• update navigation, footer and in-content links to the new addresses so they do not rely on redirects;
• make sure your most important pages are still reachable in a few clicks;
• fix orphan pages that no longer have links pointing to them;
• keep descriptive anchor text.

9. Check technical foundations on staging

Before launch, crawl the staging site and confirm:

• no noindex tag or blocking robots.txt rule is carried over from staging;
• every page returns the right status code;
• the XML sitemap lists only final, indexable URLs;
• pages render their main content without relying on slow scripts;
• images are sized and compressed, and the site meets Core Web Vitals targets on mobile;
• structured data is valid.

Performance matters here because a redesign that makes pages heavier can cancel out the SEO work.

10. Launch with a plan

Launch at a time when you can watch the site, which rules out a Friday evening. On launch day:

• switch over, then immediately test the redirect map against the live site;
• check that the robots.txt is correct and nothing is set to noindex;
• submit the new sitemap in Google Search Console;
• confirm analytics and conversion tracking are firing;
• spot check the most valuable pages in a browser and in Search Console's URL inspection tool.

If the domain changes, add Search Console's change of address step. If only paths change on the same domain, skip it.

11. Monitor after launch

Monitoring catches problems before they cost you months of traffic. After launch, check Search Console coverage and indexing for pages that are not indexed, blocked or showing errors, and look at crawl errors and 404s to fix redirects that were missed. Compare impressions, clicks and positions for key pages and queries against the baseline, clean up redirect chains and loops, confirm that real-user speed and Core Web Vitals data stay healthy, and check that important backlinks still resolve through redirects.

Review daily in the first week, then weekly for the next few months. Small shifts are normal while search engines reprocess the site. A steep drop that continues is a reason to investigate immediately.

What do website migration services and migration SEO cover?

A redesign changes how a site looks and works. A migration changes where or what it runs on: a new platform, a new domain, a move to HTTPS or a merge of several sites. Google covers this in its documentation on site moves and migrations. Website migration SEO adds a few concerns on top of the checklist above, depending on the kind of change.

Change	Example	Extra SEO concern
Redesign	New look and templates on the same domain	Metadata, content and internal links lost in templates
Platform move	Switching content systems	URL patterns and default metadata change on their own
Domain change	One domain name to another	Redirects for every page, change of address, external links
Site merge	Two sites become one	Deciding which page wins on each topic

Website migration services should cover the whole chain, from the first inventory to the weeks after the move. Before the move, expect the baseline, the URL inventory, the decision on what stays and the 301 map, agreed with you in writing. A staging build follows: a complete copy of the new site, crawled for status codes, canonicals, hreflang, robots rules and speed before anything goes live. The technical SEO services guide describes that kind of review in more detail.

The launch itself should happen when someone is watching, with redirects tested on the live site straight away, the sitemap submitted and tracking checked. In the weeks after, the checks run daily at first and then weekly against the baseline, and someone is named to fix what they find. A good provider also has a rollback plan in case indexing collapses in the first days. Ask who owns each of these steps and for a sample of the monitoring report. A team that designs and builds the new site itself can make the URL decisions together with the design, before they are expensive to change.

Beyond the checklist, the kind of change adds its own concerns. Platform changes often alter URL patterns, templates and default metadata without anyone asking for it. Domain changes need redirects for every page, the change of address step in Search Console and updates to links you control, such as profiles and listings. Merging sites requires deciding which page wins when two cover the same topic, and server changes can affect speed, caching and error handling.

What are the most common redesign SEO mistakes?

• Launching with a noindex tag left over from staging.
• Redirecting every old page to the homepage.
• Changing URLs for tidiness when the old ones worked.
• Deleting old blog posts that still bring visitors.
• Forgetting the sitemap, hreflang and structured data in the new templates.
• Treating SEO as a task for after launch, when most of it has to happen before.

How do we handle SEO in a redesign?

At OZGN we build the technical SEO foundation into the project before launch: structure, metadata, performance and how search engines understand the site. That matches step seven of our process, content and optimization. Because one team designs and builds the site, decisions about URLs, templates and speed are made together. Read more about our SEO service and web design and development service, and if you are still choosing a partner, our guide to website redesign services explains what to look for. For smaller sites, SEO for small business covers where to focus.

What did redirects teach us on a live product?

Two lessons from NovaOracles apply to any redesign. First, a retired blog slug there is redirected with an explicit 301 status, because the framework's permanent flag sends a 308 instead. Second, language alternates must list only versions that exist. An automatic header advertised every language for every page, Google crawled pages that existed in one language only and reported them as 404s, so we turned the header off and declare alternates page by page. Check your own inventory for both before launch. The NovaOracles case study describes the product.

FAQ

Does a website redesign affect SEO?

Yes, it can in both directions. Changed URLs without redirects, removed content, lost titles and broken internal links usually cost traffic. A redesign that keeps or improves content, maps every old URL to a new one and speeds up the site can hold rankings and often lift them. The outcome depends on how carefully the migration is handled.

Do I need 301 redirects after a redesign?

Yes, for every URL that changes. A 301 redirect tells browsers and search engines that a page has moved permanently and sends visitors and ranking signals to the new address. If the URL stays exactly the same, no redirect is needed. Each redirect should go straight to the closest equivalent page, not to the homepage.

How long do rankings take to recover after a migration?

There is no fixed answer. Search engines need to recrawl and process the changes, and larger sites take longer. Small movement in the first weeks is normal. A sharp, sustained drop is a sign that something is wrong, usually redirects, blocked pages or missing content, and the monitoring setup is how you catch it early.

Should I use Search Console's change of address tool?

Only when the domain itself changes, for example from one domain name to another. It does not apply to a redesign that keeps the same domain, or to changes in URL paths on the same domain. For domain moves, it is one step in a longer process that still depends on correct redirects.

Can I redesign my site in stages to reduce risk?

Yes. Moving section by section limits the damage if something goes wrong and makes problems easier to trace. The trade-off is that the site looks mixed for a while and you maintain two systems. For sites with substantial traffic, staged launches are often worth it.

What should I monitor after the new site goes live?

Watch indexing and crawl errors in Google Search Console, impressions and clicks for your key pages, 404 errors, redirect chains, page speed and your sitemap status. Compare against the baseline you captured before the launch, and review it daily at first, then weekly.

Where to start

For a redesign or a migration, send the address of the site you plan to replace, at hello@ozgnstudio.com, and we will outline the audit and the analytics access needed to identify valuable URLs before design starts. The SEO service page describes the audit.