Home / Website Redesign Checklist

Website Redesign Checklist

A website redesign should start by recording what currently works — your best-performing pages, your existing URLs and your current traffic — so none of it is lost in the rebuild. The most common and most damaging mistake is launching without mapping old URLs to new ones. A&B Consulting Group plans and builds redesigns from Burr Ridge, Illinois, serving Chicago and the western suburbs.

Most redesigns are judged on how the site looks and that is why so many of them lose traffic. The new site is better in every way anybody discussed, and three weeks later enquiries are down by half, because the pages that were quietly producing them no longer exist at the addresses Google knew.

This is the checklist we work through. The order matters more than the contents — almost everything that goes wrong in a redesign goes wrong because something in the first phase was skipped.

The mistake that causes most redesign disasters

Launching without a redirect map. It is unglamorous work and it is the single highest-stakes task in the project.

Every page on your current site has an address Google has indexed, other sites link to, and customers have bookmarked. Change the addresses without telling anybody where things went, and every one of those becomes a dead end. The rankings do not transfer, the links stop passing authority, and the traffic goes to whoever is still reachable.

The damage is also slow to appear, which is why it so often goes undiagnosed. Rankings decay over weeks, so the decline gets blamed on seasonality or the market long after the cause is fixable cheaply.

When not to redesign

A redesign is the expensive answer and is frequently aimed at the wrong problem.

If the site looks dated but converts well, the honest move is usually to leave it and spend the money on getting more people to it. If nobody is finding you, that is a search and content problem, and a new design does not create pages that do not exist. If enquiries arrive and sit unanswered until Thursday, nothing about the website changes that.

The cases where redesign genuinely is the answer: the site is slow enough to lose people, it is not usable on a phone, it has no structure for the services and locations you need to rank for, or it cannot be edited without a developer. Those are structural and cannot be fixed by spending more upstream.

Who should own what

Redesigns stall for organisational reasons more than technical ones, and the two predictable failures are worth naming up front.

Content: someone internally has to own supplying or approving copy, with a date. In most late projects the delay is a page of text waiting on a person who has a day job.

Decisions: one person with authority to approve. Design by committee produces a site that averages five opinions and expresses none, and it adds weeks.

From our side you get one point of contact rather than a ticket queue, and we would rather tell you a deadline is slipping because copy has not arrived than let it slide quietly.

The Checklist

In the order it needs doing.

01Before you touch anything — record what works

  • Export a full list of current URLs. Every page, including the ones nobody remembers publishing
  • Pull your top 50 pages by organic traffic and by conversions. These are the pages the redesign must not break
  • Record current rankings for your main terms, so you can tell afterwards whether something moved
  • Note which pages have external links pointing at them — those carry authority that dies with a broken URL
  • Screenshot or archive current analytics: sessions, enquiries, conversion rate by page, over the last twelve months
  • Record current page speed scores on mobile, so the new site can be held to being faster rather than assumed to be

02Decide what the site has to do

  • Write down the enquiry the site should produce, and from whom. A redesign without this becomes a decorating exercise
  • List the services and locations needing their own page — this drives the structure, not the visual design
  • Confirm who writes the content, and when. Copy is the usual reason redesigns run late
  • Decide what integrations are required: CRM, booking, payment, inventory
  • Agree what is explicitly out of scope, so phase two does not quietly become phase one

03Build, with search in mind from the start

  • Keep URL structure where it already works. Changing a URL for tidiness costs ranking and gains nothing
  • Carry over the content that ranks. A shorter, prettier version of a page that was working is a downgrade
  • Give every page a unique title and meta description — a template that leaves them identical is worse than none
  • Build the page for what people search, not what the company calls it internally
  • Test on a real phone on a slow connection, not just a desktop browser window made narrow
  • Keep tracking in the build: analytics, tag manager, conversion events on forms and calls

04Map every old URL to a new one

  • Produce a redirect map: every old URL, and the single most relevant new page it should point to
  • Redirect to the closest equivalent page, never to the homepage in bulk — a mass homepage redirect is treated as a soft 404
  • Use permanent redirects, so authority transfers rather than being held in limbo
  • Check for redirect chains: old URL to second URL to final page loses value at each hop
  • Test the map before launch on the staging site, not after
  • Keep the map on file. You will need it the next time somebody rebuilds

05Launch week

  • Confirm the staging site is not indexable, and that the live site is — a staging noindex tag shipped to production is a catastrophic and surprisingly common mistake
  • Submit the new sitemap in Google Search Console
  • Crawl the live site immediately for broken links and unexpected 404s
  • Verify analytics and conversion tracking are firing on the live pages, not just in preview
  • Check that forms actually deliver, to a real inbox somebody monitors. Test one end to end
  • Confirm the phone number is correct everywhere and matches your Google Business Profile exactly

06The first ninety days

  • Watch Search Console for crawl errors and a spike in 404s — the first sign of a redirect gap
  • Compare traffic and enquiries against the figures recorded in phase one, by page rather than in total
  • Expect a brief dip as Google reprocesses the site. Expect recovery within weeks, not months
  • Investigate if a specific high-value page loses traffic. That is almost always a mapping problem, not an algorithm one
  • Keep publishing. A redesign resets nothing on its own — the content cadence is what moves the site forward
FAQs

Related questions

Will a redesign hurt my search rankings?

It can, and the cause is almost always the same: URLs changed without redirects mapping old addresses to new pages. Done properly — URL structure preserved where it works, ranking content carried over, every old URL permanently redirected to its closest equivalent — a redesign should hold rankings and usually improves them through better speed and structure.

How long does a redesign take?

A few weeks for a standard custom build once content is settled. Content is almost always the bottleneck rather than design or development, which is why we agree what the pages are and who writes them before anything gets built.

Should I keep my old URLs?

Where they work, yes. Changing a URL purely for tidiness costs ranking and gains nothing a visitor will notice. Change them when the structure is genuinely wrong — no service or location pages, for instance — and redirect every old address to its closest new equivalent when you do.

What is a redirect map and do I really need one?

A list pairing every old URL with the single most relevant new page. You need one for any redesign where addresses change. Redirecting everything to the homepage instead is treated as a soft 404 and throws away the authority those pages had earned.

How do I know if the redesign worked?

By comparing against the figures you recorded before starting — traffic and enquiries page by page rather than in total, plus rankings for your main terms. Without that baseline you are guessing, which is why phase one of the checklist is recording rather than planning.

Should I redesign or just improve what I have?

Improve it, unless the problems are structural. Slow, unusable on a phone, no structure for the pages you need to rank for, or uneditable without a developer — those justify a rebuild. Looking dated while converting well does not, and that money is usually better spent getting more people to the site.

Want a number for your situation?

Tell us what you have now and what you are trying to fix. We will scope it honestly — and if you do not need us yet, we will say so.

CallGet Started