A little look around

Start a Project
All insights
Websites

Does your website need a refresh or a rebuild?

A tired homepage does not always mean starting again. Look at what works, what fails and what needs to change before choosing the size of the job.

Two people pointing at a laptop screen

A website can look dated and still have a useful structure. It can also look current while hiding broken forms, awkward editing and a checkout that nobody trusts.

A refresh improves what is already working. A rebuild changes the foundations because the existing system cannot reasonably support the business. The distinction is about evidence, not how bored you are with the hero image.

Start with three real tasks

Try finding a service, sending an enquiry and updating an important piece of content. Use a phone as well as a computer. Note exactly where something becomes difficult.

If the tasks work well and the content is sound, a focused refresh may cover the problem: clearer typography, better images, simpler navigation or improved mobile spacing.

Look underneath the surface

A rebuild becomes more plausible when the underlying system is unsupported, editing is unreliable, essential integrations cannot be maintained or core visitor journeys need substantial restructuring.

“Old” alone is not a diagnosis. Ask a developer to identify the actual constraints and explain the cost of repairing them. Sometimes the sensible answer is a small technical fix, followed by a visual update.

Protect what already earns its keep

Before replacing pages, record the URLs, useful search traffic and successful enquiry paths. Identify content that clients regularly use. Plan redirects for changed URLs and check the important forms after launch.

For a Belgian business with several languages, repeat this review across the language versions. A successful English test says little about a Dutch form or a French confirmation email.

Ask for two scoped options

Where practical, request a repair-and-refresh option alongside a rebuild proposal. Both should explain what is included, what stays constrained and who maintains the result.

Be suspicious of a recommendation that skips the inspection. A new website can be the right investment, but it should solve a defined problem rather than simply replace something unfashionable.

Before your next discussion, write one sentence: “Our current website makes it difficult for people to…” Finish it with an observable task. That sentence will do more for the project than a folder full of websites you vaguely like.

See how we distinguish the approaches in our website services, then use our quotation comparison guide when you review proposals.

More from the studio

Enough reading?

Let's make something
worth talking about.

If one of these ideas sparked a thought about your own website, we'd love to hear it.

Your choice

Choose which optional cookies you are comfortable with. You can change this whenever you like.

Strictly Necessary

Required to remember your preferences on this website.

Always active
Marketing

Not in use. We do not run advertising-tracking cookies on this website.

Not in use
Read the Cookie Policy

Rico

Your RDBK studio assistant

Rico waving hello

A little help, right here.

Hi, I’m Rico.

Good questions are my thing.
What would you like to know?

AI assistant · Enter to send

AI chat via Google Gemini. Please don’t share sensitive details. Privacy Policy