Skip to content

checklist

Website redesign checklist: keeping the rankings you already have

Irfan5 min read

How do you redesign a website without losing search rankings?

Rankings survive a redesign when every existing URL either stays the same or redirects to its closest equivalent, when the content that earns rankings is preserved rather than trimmed, and when the new site is at least as crawlable and fast as the old one. Almost all ranking loss is decided before design begins — by choosing a new URL structure, or by treating existing content as material to be shortened.

The expensive part of a redesign is rarely the design. It is that the previous site had earned rankings, links and traffic over years, and a redesign can discard that in a single deployment — invisibly, with the damage surfacing weeks later when everyone has moved on.

This is ordered by when the damage happens. Most of it is decided in the first section, before anything is designed.

Stage 1 — Before design starts

This is where redesigns are won or lost. Nothing here is design work, and skipping it is the single most common cause of a redesign that costs more than it delivered.

  • Complete URL inventory of the existing site. Every indexed URL, from the sitemap, from a crawl, and from Search Console. All three, because each finds pages the others miss
  • Identify which pages earn traffic, using impressions and clicks rather than opinion
  • Identify which pages earn external links. These are the hardest asset to replace and the easiest to discard accidentally
  • Record current rankings for the terms that matter, so you have a baseline. Without one you cannot tell afterwards whether anything changed
  • Record current Core Web Vitals from field data, for the same reason
  • Decide the URL policy: keep unless there is a reason to change. A tidier structure is not a reason
  • Build the redirect map — old URL to closest equivalent, one row per URL. This document matters more than any design file in the project
  • Flag pages with no equivalent and decide deliberately: retire with a 410, or build an equivalent
  • Audit content before it is rewritten. Length and depth are often why a page ranks

Because almost all of the risk sits in this stage rather than in the visual work, it is the part we scope first in

a redesign that treats ranking preservation as a requirement.

Stage 2 — During design

  • Design around real content, especially for pages that currently rank
  • Do not shorten ranking pages for visual balance. If a page needs to be long, design a layout that carries length well
  • Preserve heading structure and hierarchy on pages that perform
  • Keep internal links that exist. A redesign that drops a navigation section silently removes link equity from everything it pointed to
  • Set a performance budget and hold the design to it — hero images, custom fonts and animation all have measurable costs
  • Design for the content your team can actually produce, not for perfectly cropped photography that will never exist again after launch
  • Check the mobile layout against real tasks, not against a review meeting on a large monitor

Stage 3 — During build

  • Implement every redirect from the map, as 301, before launch
  • Flatten redirect chains. A to B to C should be A to C
  • Self-referencing canonicals on every page that should be indexed
  • Trailing slash consistency between canonicals, sitemap, and internal links
  • Preserve title and description on pages that rank well, unless there is a measured reason to change them
  • Carry structured data across — it is easy to lose in a rebuild and nobody notices until rich results disappear
  • Confirm the new site is crawlable: navigation present in the server-rendered HTML, no unintended noindex, robots.txt correct
  • Preserve image URLs where images are indexed, or redirect them
  • Keep the same domain and protocol unless migrating deliberately — a redesign and a domain migration are two projects and combining them makes diagnosis impossible

Stage 4 — Launch day

  • Test a sample of redirects immediately — high-traffic pages first, checking the status is 301 and the destination is the intended page
  • Submit the new sitemap
  • Confirm robots.txt does not block the site. A staging Disallow: / carried into production is a classic and catastrophic launch error
  • Spot-check canonicals on the pages that matter most
  • Verify structured data renders and validates
  • Check the site with a browser-like request, not just in a browser — some hosts behave differently for non-browser clients
  • Confirm analytics and conversion tracking still fire. These break in redesigns constantly, and the loss is invisible until you need the data

Stage 5 — The weeks after

Damage does not appear on launch day. This is the stage most projects skip because the team has moved on.

  • Watch crawl errors daily for the first fortnight. A rising 404 count means the redirect map missed something
  • Watch indexed page count against expected. A widening gap is the finding
  • Compare rankings to the Stage 1 baseline at two, four and six weeks
  • Compare Core Web Vitals field data to baseline once 28 days have accumulated
  • Check for pages that lost impressions sharply and investigate individually
  • Watch for the old site's URLs appearing as 404s in referral traffic from external links you did not know existed

Expect a temporary dip. Re-crawling and re-evaluation take time, and a modest short-term decline that recovers within a few weeks is normal. A decline that keeps going is not, and the difference is only visible if you took the Stage 1 baseline.

The three that cause most of the damage

If you do nothing else on this list:

  1. Inventory every URL and build the redirect map before design starts. Almost all preventable loss traces to this
  2. Do not trim content on pages that rank. Length is frequently the reason they do
  3. Verify redirects, canonicals and robots.txt on launch day, not when someone notices traffic has fallen

The full technical review, ordered by dependency, is in the SEO audit checklist — worth running against the new site once it is live, treating any Stage 1 or 2 failure there as a launch defect rather than an improvement opportunity.

Working through this list?

Most teams get through the audit and stall on the remediation. That is the part we usually take on.

See the service: Web DesignAsk a question

Key takeaways

  • Most redesign ranking loss is decided before design starts, not during the build.
  • The URL inventory is the single most important document in the project.
  • Content length is often why a page ranks. Trimming for visual balance removes the reason.
  • A 301 to the homepage is not a redirect strategy — map to the closest equivalent page.
  • Damage surfaces weeks after launch, so verify immediately rather than waiting to notice.
FAQ

Questions about this

It can, and it usually does when URLs change without a redirect map or when content is cut for aesthetic reasons. It does not have to. A redesign that preserves URLs, keeps the content earning rankings, and does not regress on speed or crawlability typically holds its performance and sometimes improves it through better internal linking.

Related services

Web DesignDesign that serves the conversion, not the portfolio.SEOOrganic growth built on technical foundations.

More on Web Design

UI vs UX: what the difference actually costs youThe distinction only matters when it changes a decision. Where each one fails, which problems get misdiagnosed as the other, and how to tell them apart.
TopicsWebsite redesignWeb designTechnical SEOIndexing
Chat with us