The website redesign checklist (2026): an ordered plan that keeps your Google rankings

A website redesign checklist is only useful if it runs in the right order, because the thing that goes wrong is rarely the design. It is the migration. The full ordered list is below, but here is the one-line version: baseline what you have, protect the pages that already rank, map every URL to a new one with 301 redirects, build, test hard before launch, then watch the numbers for ninety days.

The fear underneath most redesigns is simple and correct. You spend money, the new site looks better, and your enquiries fall off a cliff because the rankings you spent years earning vanished overnight. That happens, and it is avoidable. It almost always comes down to URLs that changed without redirects and content that got deleted without anyone noticing. Follow the order here and you keep the traffic while you upgrade the site.

When should you redesign your website?

Quickly, because this post is about how, not whether. Redesign when the site is actively costing you: it is not responsive on a phone, it loads slowly, the design dates you against competitors, or the enquiries have dried up and the site is the reason. A redesign is a real project with real risk, so do it when there is a problem to solve, not because you are bored of the colours. We covered the honest tells in signs your website needs a redesign. If the issue is specifically that visitors arrive and leave, read why is my website not converting before you rebuild, because a prettier version of a page that does not convert just converts more slowly.

The website redesign checklist

Run these steps in order. The early steps protect the value the later steps put at risk.

1. Baseline your analytics and current rankings. Before you touch anything, record where you are. Export your traffic, your top landing pages, and the search queries you rank for from Google Analytics and Google Search Console. This is your before picture. Without it you cannot tell, after launch, whether the redesign helped or quietly hurt.
2. Set goals and KPIs. Name what the new site must do better: more enquiries, faster load, lower bounce, a specific page ranking. Vague goals (“make it modern”) give you no way to judge the result. Pick numbers you can check in ninety days.
3. Inventory your content and map every URL. List every page on the current site and its exact URL. A free crawler will pull this for you. This list becomes the backbone of the whole project, and it is the step most checklists skip.
4. Identify and protect the pages that already rank. Cross-reference your inventory with the Search Console data from step one. Mark every page that brings traffic, earns links, or generates enquiries as protected. That content survives the rebuild, full stop. Most ranking losses are self-inflicted right here.
5. Plan the information architecture and wireframes. Decide the structure before the design: what the navigation is, how pages relate, what each page is for. Wireframe the key templates in greyscale so you are arguing about structure and not colour.
6. Build a design system. Settle the fonts, colours, spacing, and reusable components once, up front. A small consistent system beats designing every page from scratch and looks far more considered.
7. Write the copy. Words before visuals, always. The copy decides the layout, not the other way round. This is usually the real bottleneck in any redesign, so start it early.
8. Build. Now you build, against agreed wireframes, copy, and a design system. By this point the build is assembly, not invention, which is why it is fast.
9. Create a 301 redirect map. For every old URL that is changing, write down the closest matching new URL and a permanent 301 redirect between them. This is the single most important SEO step in the whole project, and the next section is entirely about it.
10. Pre-launch QA and Core Web Vitals. Test everything on staging while it is still set to noindex. The full QA list is below.
11. Launch. Flip it live, remove the noindex, and immediately resubmit your sitemap in Google Search Console.
12. Monitor at 30, 60 and 90 days. Watch rankings, traffic, and enquiries against the baseline from step one, and fix anything that slipped fast.

How do you redesign without losing your Google rankings?

This is the part that keeps owners awake, so here is exactly how to protect the rankings you already have.

• Keep the same URLs wherever you can. A URL that does not change cannot break. If a page is staying, keep its address identical and you have nothing to redirect.
• Map every URL that has to change. Where a URL must change, write the old address and the new one side by side. Every old URL needs a destination. None can simply disappear.
• Set a permanent 301 redirect for each one. A 301 tells Google the page has moved for good and passes the ranking value to the new address. A page deleted with no redirect returns a 404, loses its rankings, and breaks every link pointing at it. Redirect to the closest equivalent page, never lazily to the homepage.
• Preserve the content that performs. A redirect points Google somewhere; it does not recreate the content. If a page ranked because it answered a question well, that answer has to exist on the new site, or the redirect just sends people to something weaker.
• Resubmit your sitemap the day you launch. In Google Search Console, submit the new sitemap so Google recrawls quickly, then watch the Pages report for crawl errors over the following weeks.

Do these five things and a redesign protects your rankings. Skip the redirect map and you are gambling years of SEO on luck. Google’s own guidance on redirects and site moves with URL changes is the source of truth here, and it is blunt about how much a botched migration can cost.

A pre-launch QA checklist

Before the site goes live, work through this. A relaunch that breaks the contact form is worse than no relaunch at all, and it is the most common miss.

• Every form submits and delivers to a real, monitored inbox. Send a genuine test and confirm it arrives.
• Every internal link and navigation item goes where it should, with no dead ends.
• Every old URL redirects to the correct new page. Test the redirect map directly, do not assume it works.
• The site is checked on a real phone, not just a shrunk desktop browser. Most of your visitors are on mobile.
• Key pages pass a Core Web Vitals test for speed and stability. Google measures this and it affects both rankings and whether visitors stay.
• The copy is proofread by a human, with no placeholder text left in.
• Analytics and any conversion tracking are installed and firing before launch, not bolted on a week later.
• The staging site stays set to noindex until the moment you go live, so a half-built version is never crawled.

If a page fails QA, it does not launch. That gate is the difference between a relaunch you are proud of and one you spend the following month apologising for. It is the same standard that turned Dunnrite Scaffolding around: an outdated, non-responsive site where enquiries had dropped to almost nothing, rebuilt into a seven page conversion engine in ten working days, tested before it ever went live.

What should you monitor after launch?

The job is not done at launch. The first ninety days tell you whether the redesign worked.

• First week: check Google Search Console daily for crawl errors and 404s, and confirm every redirect still holds. Watch your form submissions to be sure nothing silently broke.
• 30 days: compare rankings and organic traffic against your baseline. A small dip as Google reprocesses the site is normal; a steep, sustained drop means a redirect or content problem to hunt down now.
• 60 days: look at behaviour. Are people staying, reading, and enquiring more than before? If traffic held but enquiries did not, the issue is the page, not the migration, and why is my website not getting enquiries is the next thing to read.
• 90 days: judge the redesign against the KPIs you set in step two. By now the rankings have settled and the numbers are honest. This is the real verdict.

Build it once, build it right

A redesign is one of the few projects where the marginal cost of doing it properly is tiny and the cost of doing it badly is everything you had. The order in this checklist exists to protect that. Baseline, protect, map, build, test, monitor.

If you would rather not carry the migration risk alone, that is the work we do. Book a free thirty minute call and we will run your current site against this exact checklist, tell you which pages must be protected, and show you what a clean relaunch would cost. If you want the rankings designed in rather than rescued after, our website design and SEO work builds the redirect map and the search intent in from day one, at a fixed price in pounds before you sign. No “from £X”, no mystery, and no relaunch that loses you the traffic you already earned.