Start with the problem the website needs to solve
A website can look dated and still have useful content, working integrations and pages that bring in relevant visitors. It can also look polished while making the offer difficult to understand. Before deciding to rebuild, separate three questions: what needs to change for customers, what needs to change for your team, and what the current platform can support.
A targeted improvement changes selected pages or interactions. A redesign changes the presentation and may reorganise the content. A rebuild replaces the implementation underneath some or all of the site. These can overlap, but they are different decisions. A new visual design does not automatically require a new platform or new URLs.
When targeted improvements may be enough
Keep the scope focused when the main difficulty is identifiable and the existing system supports the fix. Examples include an unclear service introduction, a contact button that is difficult to find, confusing product information or a form with avoidable friction.
- The offer and page structure are still broadly correct.
- Your team can update content without excessive workarounds.
- The important functions are supported and maintainable.
- You can name the pages or steps that need attention.
Start with those pages, record a baseline and check the affected journey after the change. The useful question is whether the problem was resolved, rather than whether enough of the site looks different.
When a redesign makes sense
A redesign is worth considering when several parts of the presentation no longer work together. The company may have added services, the identity may have changed, or visitors may need a different order of information before contacting you.
Here the work usually begins with the offer and content hierarchy. Decide what the homepage must explain, how services differ, where project evidence belongs and what the next step should be. Then design the layouts around those requirements.
In the Brandersky website project, the business already had a family history, craftsmanship and a range of stonework to show. The work connected those strengths to a clearer service structure and consultation path. That is a useful example of a presentation problem being addressed through both structure and design.
When rebuilding the website may be justified
A rebuild is a technical scope decision. Consider it when the current implementation cannot reasonably support the required content, functions or maintenance. That may involve a replacement theme, builder, content model or platform; it does not necessarily mean replacing everything.
- A required function cannot be supported reliably within the current setup.
- Routine edits depend on fragile workarounds or inaccessible custom code.
- The content model cannot represent the products, services or languages you need.
- Repeated technical faults point to a deeper implementation problem.
Ask for a concrete explanation of the limitation, the alternatives and what will be retained. Age alone is not enough to decide that a website needs rebuilding. Equally, keeping the current platform is not useful if maintaining it prevents the business from doing the work it needs.
Compare the three scopes before choosing
Targeted improvement
Best fit: a specific content or interaction problem. Keep: the wider structure and supported implementation. Define: the affected pages, the change and how to verify it.
Redesign
Best fit: a broader mismatch in the offer, identity or customer journey. Keep: useful content, established URLs and working functions where they still fit. Define: the new page hierarchy, layouts and content responsibilities.
Rebuild
Best fit: an implementation that cannot support the agreed requirements. Keep: valuable content, business data and search visibility wherever possible. Define: what is being replaced, what is migrated and how each important function will be checked.
Use the customer journey to decide what matters
For CoolSystems, browsing air-conditioning products had to connect with expert selection, installation and servicing. The website therefore uses a catalogue and a non-binding enquiry route. The useful design decision was to support a purchase that can require expert confirmation.
Your site may need a different path. A service business may need a clear brief and contact route. An online shop may need product comparison and checkout. Map that journey before choosing features or a platform.
We map that journey with you before choosing the design or platform. At Flamia, we turn it into a clear page structure and the right route to enquiry or purchase, then check those paths on desktop and mobile before launch.
What should stay during a redesign or rebuild?
Make an inventory of pages, useful content, downloads, forms and integrations. Identify which URLs receive relevant search traffic or have valuable links. Record how enquiries or purchases are measured. Decide what remains, what is combined, what is removed and what needs a replacement.
If URLs change, Google’s site-move guidance recommends mapping old addresses to relevant new destinations, implementing redirects, updating internal links and checking the new sitemap and indexing settings. Google also advises separating major changes where practical. Plan this work before launch and monitor the move afterwards.
When Flamia handles your redesign or rebuild, we include the necessary migration tasks in the agreed scope and take care of their implementation. We map changed URLs, set up redirects, update links and verify the sitemap and indexing settings. We check the live website after launch and monitor Search Console for migration issues, so you have a team responsible for the transition as well as the new design.
What to include in your first brief
- Your existing website and the main problem you want to solve.
- The audiences, services or products the site must support.
- The functions and integrations that need to keep working.
- The content and brand materials already available.
- Who will maintain the website after handover.
- Any fixed launch date or budget constraints.
You do not need to prescribe the technical solution. A useful brief gives the designer enough context to explain which scope fits and why. Before work begins, agree the deliverables, content responsibilities, migration tasks and checks required for launch.
Bring us the business context; we will work out the technical scope with you. We explain the recommended approach, what we will deliver, what we need from your team and how the launch will be checked. You get a clear plan and responsibilities before implementation starts.
Choose the scope around the evidence
Begin with a targeted improvement when the problem is narrow. Redesign when the presentation and journey need a shared new structure. Rebuild when the implementation cannot support that structure reliably. If the cause is still unclear, start with a review of the current site.
Explore Flamia’s website design and development, or tell us what your current website needs to do better.
