Website Redesign SEO Checklist: Redesign Without Losing Rankings (2026)

Last updated: 29 October 2026

A website redesign keeps its rankings when the URLs, the words that rank and the internal links survive it. Before design starts, list the pages that earn search traffic and freeze their URLs. During the build, keep each page's title, headings and content, the same on mobile as on desktop. On launch day, redirect anything that moved and remove staging blocks. Then compare every top page against a benchmark for the first few weeks.

Search engines do not rank a design. They rank pages: their addresses, their words, the links between them and how well they load. A redesign changes all four at once, which is why redesigns are a well-known way to lose traffic. This checklist runs in the order the work happens, and each Google rule in it comes from Google's own documentation, read on 29 October 2026.

If the redesign also moves the site to a new platform or domain, read how to migrate a website without losing SEO alongside this one. That guide covers the move. This one covers the design.

Why redesigns lose rankings

What the redesign changes	What can go wrong
URLs	Old addresses return 404, and the links and history behind them stop counting
Copy	A long page that answered a search becomes a short one that does not
Navigation	Pages drop out of the menu and lose the internal links that pointed at them
Mobile layout	Content hidden or cut on phones, which is the version Google indexes
Code	Links built as buttons, images as CSS backgrounds, content that loads only after a click
Speed	Heavy video, fonts and animation slow the page and shift the layout
Metadata	Titles, descriptions and structured data left behind in the old templates

Each one is avoidable. They are missed because nobody owns them while the team is busy with the design.

Before design starts

1. Take a benchmark

Export the Performance report from Google Search Console for the last three and twelve months, by page and by query. Save the Core Web Vitals report too. After launch, this is how you tell a normal wobble from a page that broke.

2. Find the pages that earn traffic

Sort the export by clicks. The pages at the top set the rules for the redesign: their URLs stay, their content stays, and they are the first pages checked at launch. Add the pages other sites link to most, from the Links report in Search Console.

3. Freeze the URLs

Treat every URL as fixed unless there is a real reason to change it. A kept URL needs no redirect and carries no risk. Where one has to change, map it to its closest new page now, not the week of launch. My redirect map guide shows how.

4. Record the words that rank

For each top page, note the queries it ranks for and where on the page those words appear: the title, the main heading, the subheadings, the body. A redesign can keep the meaning of a page and still lose the exact phrases searchers use. The copy can be rewritten, but the new version has to answer the same searches at least as well.

5. Plan the navigation with the links in mind

Google uses links to find pages and to judge what they are about, according to its link best practices. A page that loses its place in the menu and footer loses many of the links pointing at it. If the new navigation is smaller, link the dropped pages from related pages instead.

6. Decide what to merge and what to drop

Redesigns are a good time to prune, and pruning is where traffic quietly leaks. Google's site move guide gives the two rules:

• Merged pages: when several old pages become one, redirect each old URL to the new consolidated page.
• Dropped pages: content you are not keeping should return a 404 or 410, not redirect to the homepage. Google says many URLs redirected to one unrelated page can be treated as soft 404s.

Before dropping a page, check the benchmark. A page that looks dated can still bring steady clicks or links from other sites, and those are worth keeping or merging.

What a redesign can safely change

Most of what people mean by a redesign carries little search risk on its own: colours, type, imagery, spacing, components, the order of sections and the wording of copy that does not rank. The risk sits in a short list of things that look like design decisions but are search decisions: URLs, the words on ranking pages, navigation links, what shows on mobile and how fast the page loads. Keep those deliberate and the rest of the design is free to change.

During design and build

Design for mobile first, with the same content

Google indexes and ranks the mobile version of a page. Its mobile-first indexing guide asks for the same content, the same clear headings, the same title and meta description, and the same structured data on mobile as on desktop. It allows a different design, such as moving content into accordions or tabs, as long as the content is equivalent. Cutting a section from the phone layout cuts it from Google's view of the page.

Build links and images that Google can read

• Links: Google says it can generally crawl a link only if it is an <a> element with an href. A clickable card or button that navigates with a script may not be followed.
• Anchor text: the visible text of a link tells people and Google what is on the other side. "Read more" tells neither.
• Images: Google's image SEO guide says it does not index CSS background images. Images that matter belong in <img> elements with useful alt text.
• Hidden content: Google won't load content that needs a click, swipe or typing to appear. Primary content should be in the page when it loads, even if it sits in a closed accordion.

Carry over the metadata

Every page needs its title tag, meta description, canonical tag and structured data in the new templates. These live in the page head, so they are easy to lose when templates are rebuilt. Preview new titles in the SERP snippet preview and rebuild markup with the schema generator. Each page should name itself as its canonical URL.

Keep the new design fast

Google highly recommends good Core Web Vitals for success with Search. The thresholds for a good experience:

Metric	Measures	Good	Redesign risk
Largest Contentful Paint (LCP)	Loading	Within 2.5 seconds	Hero videos, large images, slow web fonts
Interaction to Next Paint (INP)	Responsiveness	200 milliseconds or less	Heavy scripts, animation libraries, chat widgets
Cumulative Layout Shift (CLS)	Visual stability	0.1 or less	Images without set sizes, late banners, font swaps

Source: web.dev's Web Vitals guide, which says to measure at the 75th percentile of page loads, on mobile and desktop separately. Motion can be part of a fast page. It has to be built for it: animate transforms and opacity, size every image, and load what sits below the fold later.

Block the staging site

Keep the staging copy out of search with a noindex rule or password protection, and write down what has to be removed on launch day. A staging block that reaches the live site can take the whole site out of search.

Before launch: the QA pass

Run through the top pages from step 2, on the staging site, against the benchmark:

1. Same URL, or a mapped redirect to its new one
2. Title, meta description and main heading present and intended
3. The content that answered its searches still on the page, on mobile too
4. Structured data present, and valid in Google's Rich Results Test
5. Canonical tag pointing at itself
6. Internal links to it from the menu, footer or related pages
7. Images in <img> elements with alt text
8. Core Web Vitals checked with a lab tool such as Lighthouse
9. Forms, tracking and analytics firing on the new templates

Then crawl the whole staging site with a crawler such as Screaming Frog to catch broken links, missing titles and orphan pages that no other page links to.

On launch day

• Remove the staging noindex rule or robots.txt block, and confirm the live robots.txt
• Turn on redirects for any URL that changed, and test each one
• Submit an updated sitemap in Search Console
• Inspect the top pages with Search Console's URL Inspection tool
• Check that analytics and conversion tracking record visits

The first few weeks

Compare the top pages against the benchmark each week. Some movement while Google recrawls is normal, and when URLs change, Google's site move guide says most pages of a small or medium site move within a few weeks. What is not normal is one page losing most of its clicks while the rest hold. That points to a problem on that page: a missing redirect, cut content, a noindex left behind or a lost internal link.

Watch the page indexing report for new not found errors, and the Core Web Vitals report as real-user data arrives. Fix problems page by page and request indexing for the pages you fix.

The checklist on one screen

When	Do this
Before design	Benchmark, find the pages that earn traffic, freeze URLs, record the ranking words, plan navigation links
During build	Same content on mobile, crawlable links, images in <img>, metadata and structured data carried over, Core Web Vitals in the good range, staging blocked
Before launch	Page by page QA of the top pages, full crawl of staging
Launch day	Remove staging blocks, turn on and test redirects, submit sitemap, inspect top pages, check tracking
After launch	Weekly comparison with the benchmark, indexing and Core Web Vitals reports, page by page fixes

How I run a redesign

My website redesign sprint is $1,999 fixed and 14 days for a site of up to about 25 pages, rebuilt in Framer. The rankings side of it:

• Two days reading which pages earn their traffic before anything is redrawn
• Every page designed against the real content, not placeholder text
• Every existing URL mapped and redirected before launch
• The old site kept live until you approve the new one, and 30 days of support after launch

More on the service is on the website redesign page. If you are not sure the site needs a redesign at all, a $499 UX audit finds what to fix in 3 days, and its price is credited against a sprint booked within 30 days.