02 / Website decisions

Should You Redesign Your Website or Improve the One You Have?

A new website can be useful, but it is not automatically the answer to a weak page, unclear offer or missing conversion data.

Back to insights
Source. Answer. Action.Use the evidence in your own context before choosing the next step.

Follow the trace

The source stays attached to the answer and the action it supports.

Source

Google Search Central: SEO Starter Guide and site-move guidance

Open public source Google Search Central: site moves with URL changes
Answer

Choose the smallest change that can address the diagnosed problem. If the structure must change, protect useful URLs, content and measurement as part of the work.

Action

Write the problem, branch to the right first step and keep an inventory, URL map, redirect test and release monitor beside any redesign plan.

The answer in context

Short sections keep the decision visible and leave room for the limits.

Start With The Problem

Write down what is failing in terms a customer or team can observe: people cannot find a service, visitors leave before the next step, the page is hard to update or the site cannot record a useful action.

  • If the offer or page message is unclear, start with content and structure.
  • If the page is clear but the form or journey loses people, start with conversion work.
  • If the site is difficult to crawl, slow, unsafe or impossible to maintain, start with a technical review. A rebuild may be justified when the evidence points to a structural constraint rather than a focused fix.
  • If the business cannot tell what is happening, fix measurement before choosing a visual direction.

Improve The Existing Site When

The current site has useful pages, stable URLs and a platform the team can maintain. A focused change to the offer, page structure, speed, navigation, forms or tracking may create learning sooner than a full rebuild.

Redesign When The Structure Blocks Progress

A redesign is more reasonable when the information architecture no longer matches the offer, the platform blocks important changes, the site cannot support the audience or market, or a major business change requires new page roles.

  • Write the new page and URL plan before choosing a visual treatment.
  • Name the content, redirects, tracking and approval owners.
  • Test the new journey on mobile and with real actions before launch.

Protect What Already Works

A new design can change URLs, content, internal links and measurement, even when your offer stays the same. The migration steps below show what to protect before and after an agreed release.

Choose the branch that matches the problem.

Do not choose a rebuild until the observable problem points there.

Message or content

The page does not answer who the offer is for, what it solves or why the next step makes sense.

First step

Review page roles, offer language, evidence and the questions buyers ask.

Journey or conversion

People understand the offer but lose the path through navigation, forms, checkout, speed or the next action.

First step

Trace a real task on mobile and inspect each point where a person must decide.

Technical or maintenance

The site is difficult to crawl, slow, unsafe or impossible for the team to update without repeated workarounds.

First step

List the constraints, dependencies and page types before choosing a platform or visual treatment.

Measurement

The team cannot tell what happened after a visit or whether the action was useful to the business.

First step

Agree the action, owner and source of truth before judging a new design.

Protect what already works.

A migration is part of the redesign, not a task to leave until the end.

  1. Inventory the current URLs, important content, internal links and measurement events.
  2. Map old and new page roles and name an owner for each redirect decision.
  3. Test redirects, canonical links, forms and tracking before an agreed public release, then check them again on the public site after release.
  4. Monitor crawl, index and conversion signals after launch, then record what changed and what remains uncertain.

Questions before improving or rebuilding a website.

Does a weak website always need a rebuild?

No. A specific message, journey or measurement problem may be addressed through a focused improvement.

How can we tell whether the platform is the problem?

Identify the change you need and the constraint that prevents it. Appearance alone does not establish a platform limitation.

What if the offer is unclear?

Clarify the audience, information and next action before assuming a new layout will fix the problem.

What if visitors cannot complete an enquiry?

Review the route and the actual failure, including forms and destinations, before deciding the scope.

Can we judge a redesign using page views alone?

Page views do not establish whether visitors completed a useful action. Agree the relevant evidence first.

Should pages that already work be kept?

Retain accurate useful content and routes unless there is a clear reason to change them.

What should happen to old URLs?

Inventory them, map changed addresses to relevant replacements and test redirects and internal links.

Does a redirect plan guarantee rankings stay the same?

No. It reduces avoidable migration errors but does not guarantee search outcomes.

What should we check at release?

Agreed page content, links, forms, measurement and migration behavior, with an owner for each check.

Where does the migration guidance come from?

The article links official Google SEO and site-move documentation.

Choose one useful next step.

Bring the question, source and current context. Keep the first scope as specific as the evidence allows.

Review website design work Contact Aaron on LinkedIn