Inside a Website Redesign Project: Our Process, Step by Step

Why Redesigns Fail When There's No Process

Most website redesigns don't fail because of bad design. They fail because nobody wrote down what "done" looks like before the work started, so the project drifts, the scope grows, and the launch date keeps slipping. A redesign project needs the same discipline as any other build — just applied to a site that already exists, already ranks for something, and already has customers using it.

Here's what that process actually looks like on our end, from the first look at your current site to the day it goes live.

Step 1: Auditing What You Already Have

Before we touch a single design file, we go through the existing site in detail. That means:

• Traffic and conversion data — which pages actually get visits, which ones convert, and which are dead weight.
• Technical debt — broken plugins, outdated code, slow-loading assets, orphaned pages nobody remembers building.
• SEO equity — what's currently ranking, which URLs have backlinks pointing at them, and what needs to be preserved rather than rebuilt from scratch.
• Content inventory — copy, images, and forms worth keeping versus content that's stale or duplicated.

This audit matters because a redesign that ignores existing SEO equity can quietly tank your rankings for months after launch, even if the new site looks better. We treat URL structure and redirects as a first-class part of the plan, not an afterthought fixed after launch.

Step 2: Defining the Actual Problem

"We want a redesign" is a starting point, not a brief. We push to get specific about what isn't working: Is the site not converting visitors into calls or bookings? Is it slow on mobile? Does it look dated next to competitors? Is it hard for your own team to update? The answer shapes everything downstream — a conversion problem gets solved differently than a performance problem, even though both might look like "the site needs a redesign" from the outside.

This is where we also decide whether a redesign is even the right move, or whether a lighter refresh — new copy, better calls to action, a faster host — would solve the actual problem without a full rebuild. See our related piece on what we look for before taking on a new web project for more on how we think about fit and scope at this stage.

Step 3: Information Architecture and Wireframes

Before any visual design happens, we map out the structure: what pages exist, how they're organized, what the primary navigation paths are, and what action we want a visitor to take on each page. For local and service businesses this usually means a hard look at whether booking, quote requests, or phone calls are as close to one click as they can be.

Wireframes stay intentionally rough at this stage — boxes and labels, not colors and fonts. The goal is agreement on structure before anyone gets attached to a visual direction.

Step 4: Visual Design

Once the structure is signed off, we move into actual design — layout, typography, color, imagery, and brand consistency. We typically present a homepage concept first, since it sets the visual language for every other page, then move through key interior templates (service pages, about, contact, blog) rather than designing every single page individually.

Feedback rounds happen here, and this is usually where a project's timeline expands or contracts the most, since design revisions are the step most affected by how quickly a client can review and respond. We talk through what a realistic revision timeline looks like in what a website project timeline actually looks like.

Step 5: Build

Approved designs go into development. For most redesigns today that means a custom build rather than a page-builder theme — faster load times, more control over structure, and no dependency on a third-party plugin ecosystem that can break with an update. We cover the reasoning behind that choice in more detail in why we build on Next.js instead of WordPress.

During the build, we're also setting up the pieces that don't show up in a screenshot: form handling, analytics, structured data for search engines, redirect mapping from old URLs to new ones, and any integrations with a CRM or booking tool you already use.

Step 6: Content Migration and QA

Content gets moved over — not copy-pasted blindly, but reviewed for what should be rewritten, trimmed, or expanded given the new structure. Then QA: every form tested, every link checked, every page tested across real devices and browsers, not just desktop Chrome. Redirects get tested individually, since a single missed redirect on a page with backlinks is a real, avoidable loss.

Step 7: Launch Checklist

Before anything goes live, we run through a fixed checklist rather than relying on memory:

• SSL and domain configuration confirmed
• Analytics and conversion tracking verified as firing correctly
• Redirects from every old URL that had traffic or backlinks
• Search engine sitemap submitted
• Forms tested end to end, including confirmation emails
• Site speed and mobile rendering checked one final time
• Backups and monitoring in place from day one

What Happens After Launch

A redesign isn't really finished at launch — it's finished once you've had a few weeks of real traffic to see how it performs against the problem you started with. We keep an eye on the metrics that mattered in step one and flag anything that needs adjusting. If SEO was part of the goal, that's a slower-moving signal that takes longer to read clearly, which is part of why we treat search strategy as something built into the site from day one rather than bolted on after. More on that in how we approach SEO for a newly launched website.