Does Your Business Need a Website Refresh, Redesign, or Rebuild?

Start with the business, not the age of the website

A site doesn't need a redesign just because it's been online for a few years. A newer site can be a poor match for the business. An older one may have a sound structure and only need focused work.

Here's where I start. First, I want to understand the business, the problems it's facing, and its short-term and long-term goals. That understanding comes before recommending what needs to change on the website.

That order is also how a project finds its real size. OLA of Eastern Long Island initially approached me for a website and logo. Through the research, the project expanded into rebuilding the website and developing the broader brand.

It keeps the decision about the business, not about anyone's taste, including mine. Nielsen Norman Group makes a similar case: choose between small changes and a major overhaul based on evidence, user needs and business goals.

Refresh, redesign, rebuild and replatform: what each one changes

Agencies don't use these words the same way, so here's how I use them.

These overlap. You might redesign and rebuild on the platform you already have. You might move platforms and keep most of the design. Or one project might include all four.

When the problem is contained: a refresh

A refresh makes sense when the site still reflects your business, people can find what they need, and the platform can handle what comes next.

The work might cover outdated photos, inconsistent visuals, stale service descriptions, a clumsy form, mobile layout problems or a handful of components. These can be real improvements. What makes it a refresh is that the structure underneath still does its job.

Pages that are hard to update, or trouble with hosting, don't automatically mean a rebuild. Find out whether the problem is isolated or a sign of something bigger before you widen the scope.

When the business has outgrown the site: a redesign

A redesign makes sense when the site no longer explains your business well, or doesn't help people decide.

That happens when services change, a new audience matters, positioning gets sharper, or the navigation still reflects an older version of the organization. It also happens when proof is hard to find, pages have no clear job, or visitors can't tell what to do next.

When AJ Speech Services came to me, the starting point was "an existing website that didn't adequately communicate her expertise, positioning, or services." When a site doesn't communicate the business clearly, a visual update alone rarely fixes it. Look at the message, how the content is organized, and the path to each service first. That on its own doesn't tell you whether the platform should change.

When the build or the platform is the problem: a rebuild or a move

A rebuild is about how the site is built. A replatform is about where it's built.

A site can be rebuilt on the same platform when its templates, code, content structure or integrations need major work. A site can also move to a new platform and keep much of its design and structure. Many projects do both, but they're two different decisions.

Most of my website projects involve moving clients to a platform that fits their needs better. That doesn't mean every project needs a move. Platform fit depends on your content, how you edit, your integrations, who maintains the site and where the business is headed.

If a move changes your URLs, Google recommends mapping old URLs to new ones, setting up redirects and monitoring the move. Google also notes that rankings may fluctuate for a while as pages are recrawled and reindexed.

What a bigger project touches besides the design

A redesign or rebuild means deciding which content to keep, rewrite, combine or remove. Digital.gov's conversation on content audits names redesigns and CMS migrations as common reasons to take a full inventory first.

It can also touch:

• forms and integrations
• analytics and tracking
• domain, hosting and account access
• who can edit what
• photos, media and downloadable files
• redirects and search checks
• training, and who owns the site after launch

Accessibility belongs in the scope too. W3C explains that poorly designed sites can keep people with disabilities from using them. A new look doesn't make a site accessible on its own, so name the requirements and who tests them.

The bigger the change, the more carefully you decide what to keep. Not everything. Just what still has value.

A quick way to work out your scope

Use these five questions before you talk to anyone about a project. A closer review may still change the answer.

1. Start with the business. What problems should the website help solve? What are your short- and long-term goals? If the site no longer reflects your services, audience or priorities, look at a redesign.
2. Watch someone use it. Ask a person outside your business to find a service and send an inquiry. Notice where they hesitate, go back or give up. It's a first check, not formal user testing. Trouble with navigation or the path to contact points to a redesign. Trouble with one page, form or component points to a refresh.
3. See how far the problem goes. If it's limited to some content, images or components, a refresh may be enough. If it shows up across many pages, check whether one shared element can be fixed or the structure itself needs a redesign.
4. Look at the build and the platform separately. Major reconstruction on a platform that still fits: rebuild. A platform that no longer fits: replatform. Hard updates or hosting trouble on their own: find the cause first.
5. List what has to survive. URLs, content, data, analytics, files, permissions, integrations and workflows that still have value. If your answers point to more than one kind of change, plan a combined scope, such as a redesign plus a rebuild.

If the signals conflict, dig further before you lock the scope.

Compare proposals by what's inside them

Two agencies can both call their work a "redesign." One means new visuals and templates on your current platform. Another includes research, positioning, content, copywriting, development, migration, redirects, training and support after launch.

Look beyond the project label and ask what the proposal actually includes: what stays, what changes, whether the platform will change, who handles the migration and testing, and what support is available afterward.

Before you sign, also check that it spells out:

• what content or data moves over
• whether URLs change, and who owns the redirect plan
• which integrations and tracking get tested
• what's excluded
• who controls the accounts and files after launch

A good proposal makes the tradeoffs visible. It also leaves room for discovery to change the plan.

Choose the smallest scope that solves the whole problem

The right scope fixes the business problem without throwing away work that's still good, or leaving a known problem in place.

Start with the business, name the problem and get clear on your goals. Then decide what the website needs.

If you'd like a second set of eyes first, our free Website & SEO Audit is a written review of up to three key pages on your public site. It shows what's working and what deserves attention next, with no account access or strategy call needed. If you're already planning a project, here's how I approach web design.