Why a redesign doesn’t always mean starting over.

If your website feels outdated, don’t assume the whole thing needs replacing.

It’s a thought I hear surprisingly often.

“My website no longer represents my business.”

Sometimes it’s because the design feels old. Sometimes the business has changed direction. Sometimes the owner has changed, new services have been introduced, or the brand has simply matured over time.

The first instinct is often to rebuild everything from scratch. In my experience, that’s not always the right answer.

One of the projects that reinforced this for me was a rebrand I completed for Georgie Mullen, formerly known as Georgie Eats.

On the surface, it looked like a website redesign. In reality, it was a lesson in deciding what shouldn’t change.

The Website Wasn’t the Problem

By the time Georgie contacted me, her website had been online for several years.

It contained hundreds of recipes, many of which had been shared across social media, bookmarked by readers and indexed by search engines. More importantly, it had become an integral part of her business. She had an established way of publishing new recipes, managing content and interacting with her audience.

The website wasn’t failing. The business had simply evolved. Georgie had decided to move away from Georgie Eats and establish a stronger personal brand under her own name, Georgie Mullen. She already had a new visual identity prepared by her designer. My role was to implement that new branding on the website and manage the technical transition to the new domain.

Before I started making changes, I wanted to understand what the website was already doing well. The design was changing, but many other things were already working exactly as they should. Readers could easily find recipes, the content structure was well established, and Georgie was comfortable managing the website herself.

That shaped the way I approached the project.

Instead of treating it as a completely new website, I treated it as an evolution of an existing one. My goal wasn’t simply to implement the new branding, it was to make sure the transition preserved the value the website had already built over the years.

Implementing the New Brand

The creative direction had already been established. Georgie’s designer had created the new branding, and my role was to bring that vision to life on the existing website.

Applying the new colours, typography and decorative elements wasn’t the difficult part. The technical challenge was implementing those changes while protecting everything the website had already built over the years.

That meant preserving existing URLs, keeping the publishing workflow familiar, planning the migration to a new domain and making sure readers could continue finding recipes without interruption.

One of the things I enjoy most about WordPress projects like this is that the technical decisions often have a much bigger impact than the visible ones. Visitors notice the new design, but they rarely notice that years of shared links still work, that the client doesn’t have to learn a new editing workflow, or that the transition happened without disrupting the business.

For me, those are often the most rewarding parts of the project.

Sometimes the best technical decision is not rebuilding everything.

It would have been perfectly possible to rebuild the website using a completely different setup.

Instead, I chose to build on what was already working.

The visual identity changed to reflect the new branding, but the content structure stayed intact. I created the new pages using Gutenberg patterns so Georgie could continue editing them with tools she was already familiar with.

From her perspective, the website felt new. From an editing perspective, almost nothing changed. That’s exactly what I wanted.

One of the things I’ve learned over the years is that a successful website isn’t measured by how different it looks after launch.

It’s measured by how confidently the client can continue using it the next day.

The migration was about much more than moving files.

Changing the domain meant much more than copying a WordPress installation from one server to another. Years of recipe links already existed online. Breaking them simply wasn’t an option.

So one of my priorities was preserving the entire URL structure. Every request to the old domain was redirected to the corresponding page on the new domain, allowing readers to continue using old links without even realising the website had moved.

Behind the scenes, I also configured DNS changes, email forwarding and the infrastructure needed to support the new domain. Most visitors never noticed any of it. That’s exactly how it should be.

Then came the unexpected part.

Halfway through the project, I discovered that the hosting account didn’t have enough storage to hold both the existing website and the redesigned version during the migration. At that point, I had two choices.

Try to force the migration on the live server and introduce unnecessary risk…

…or rethink the deployment.

I moved the development to my own server, completed the work there and only migrated everything once Georgie had approved the final result. Before deployment, I freed enough space on the production server to complete the migration safely.

It wasn’t the original plan. But good projects rarely follow the original plan exactly. The important part is recognising the problem early and adapting without compromising the final outcome.

Looking back, this wasn’t really a redesign project.

• It was a continuity project.
• The branding changed.
• The domain changed.
• The visual identity changed.
• But the things that mattered most to the business stayed intact.
• Readers could still find recipes through links that had been shared years earlier.
• Georgie could continue managing the website without learning a new system.
• The transition felt natural because it had been planned that way.

Looking back, I think that’s what good WordPress development is really about. It’s not just writing code or installing plugins. It’s understanding how a business uses its website and making technical decisions that support that business rather than disrupt it.

Could your website evolve without starting over?

If your website no longer reflects where your business is today, rebuilding everything isn’t always the answer.

Sometimes the best solution is to build on what already works, preserve the value you’ve spent years creating, and evolve the website alongside your business.

Every project is different. The first step isn’t choosing a theme or a page builder. It’s understanding what your business can’t afford to lose. If that’s a conversation you’d like to have, I’d be happy to help.