Website redesign guide

Website redesign guide: compare fixes, improvements and a full rebuild

Your services have changed, mobile pages are awkward or updates have become difficult. Should you improve a few pages or rebuild the website? This guide helps compare the options, migration work and criteria for accepting the result.

Discuss your project

Our starting point

Review competitors, customer searches and useful existing pages before redesigning

A redesign should begin with your business priorities and the strengths of the current website. We review competing offers and useful reference sites to understand what customers can already compare: service detail, supporting evidence, practical information and the steps towards an enquiry or purchase. Existing pages that help customers or attract relevant visits deserve particular attention.

Keyword research then checks how the intended audience describes each need. “Bathroom renovation quote [city]” and “bathroom renovation ideas” illustrate different intentions for an appropriate business. They are research hypotheses, not measured opportunities. Their purpose is to clarify which information belongs on a service page, a guide or a project example.

This work supports an agreed page plan, content priorities and decisions about existing URLs. The measurement plan compares useful enquiries or sales with a suitable starting period, while acknowledging other influences. Research depth, data access and the scope of the resulting changes are defined in the proposal.

Test the route from a service page to an enquiry and its confirmation

Can someone understand the service, check whether it suits them and send an enquiry? Do they receive a useful confirmation? Try the same journey on mobile and ask the people who handle enquiries where customers tend to get stuck.

Your own editing experience matters too. If a routine change requires rebuilding a page, that constraint belongs in the brief.

Compare page loading and mobile usability before deciding what to change

Compare important pages under defined conditions. PageSpeed Insights can help investigate loading performance, alongside real-world use and the site’s constraints.

Older reports may still mention Google Mobile-Friendly Test. That service has been retired. Mobile checks should examine the current layout and interactions rather than rely on an old pass or fail result.

Choose between fixing a problem, improving pages and rebuilding the website

Fix: Address a broken form, missing information or a problem limited to a few pages.
Improve: Rework content, navigation or templates where the technical foundation still serves the business.
Redesign: Rebuild the structure and page system when the existing limitations prevent the required improvement.

Compare the total cost, migration effort and future maintenance, not just the visual change.

Coordinate SEO, design, user experience and maintenance work

The French resources Consultation SEO, Refonte WordPress, Audit UX and Maintenance site cover the linked subjects of search, WordPress redesign, user experience and maintenance.

Your project does not necessarily need four separate services. The proposal should select the work that solves the actual problem. See also our WordPress redesign approach.

Inventory the content, URLs, forms and integrations to preserve

List the pages, content, images, forms and integrations. Identify the pages that bring enquiries and any commitments attached to publications or links.

Then define the recovery point, test environment and acceptance checks. The budget should distinguish design, writing, implementation, features, third-party costs and maintenance.

Pour décider

A worked example: improve the enquiry journey or rebuild?

Imagine a fictional consultancy with useful articles and three service pages. Its design is old, but the main complaint is that visitors cannot tell which service fits them. The contact form asks for a long project specification before a first conversation. A complete rebuild is one option; clearer service pages and a simpler enquiry journey are another.

Start by separating the problems. If the platform still supports reliable editing, clear navigation and the required form, a targeted improvement may address the immediate need. If each change breaks layouts, essential software cannot be maintained or the required customer journey cannot be implemented reliably, rebuilding may be justified. The decision depends on observable constraints, not the age of the design alone.

Swipe across the table to see every column.

A decision framework for the illustrative consultancy
Option	Work to define	What would make it suitable
Targeted correction	Clarify service scope, simplify navigation and repair the contact journey.	The foundations still support the required use and future updates.
Template and content improvement	Rework shared page layouts, service content and editing fields.	Problems repeat across pages but do not require replacing the whole platform.
Complete redesign	New structure, implementation and a migration plan for useful content and functions.	The existing foundations prevent the agreed improvements or cannot be reasonably maintained.

Ask for the retained assets, omitted work and acceptance checks for each option. The least expensive proposal may leave the main problem unresolved; the most extensive proposal may add work that does not improve the customer journey.

Pour décider

Prepare a migration register before changing URLs.

A practical register lists the old URL, its purpose, the proposed destination, the decision and the person who validates it. Add pages used by advertising, customer emails or printed materials, not only pages discovered by browsing the menu. Available search and analytics data can help identify important pages, but lack of recorded traffic does not automatically make a page disposable.

Swipe across the table to see every column.

An illustrative migration register
Current item	Decision to record	Verification
Useful service page with the same purpose	Keep the address when possible.	The content, main links and customer action still work.
Two overlapping service pages	Merge only if the destination answers both needs coherently.	Relevant content survives and old URLs reach the agreed destination directly.
Service no longer offered	Explain the chosen removal or genuine alternative.	Do not redirect to an unrelated page simply to hide an error.
Form connected to a business tool	Document fields, routing and confirmation.	A controlled test reaches the intended workflow without exposing customer data.

Plan a recovery point and identify who can restore the previous version if a release fails. That is separate from the redirect plan. Backups, access, third-party dependencies and the release window must be understood before replacing the live site.

Pour décider

Test mobile enquiries, editing access and any ordering functions before acceptance

Choose representative journeys rather than checking only the homepage. On a phone, find a service, read what is included, use the contact route and review the confirmation. If the site includes an administration area, ask the future editor to complete a routine change with the provided instructions. For a store, include payment, delivery and order communication in the agreed test scope.

Record each finding with the page, device, action and expected outcome. “The site feels wrong” is difficult to act on; “the service choice is lost when I open the booking tool” points to a decision. Agree which issues prevent release and which are separate requests. This makes the validation useful to both the business and the person implementing the changes.

At handover, confirm the accounts you control, the materials you receive, the renewal responsibilities and the scope of any ongoing support. You purchase and renew the domain through your own account. Hosting, software subscriptions and maintenance are separate choices. A new visual design does not automatically include ongoing SEO work or unlimited future changes. The project proposal should make those boundaries clear.

Questions about SEO, domains, page addresses and platform changes

Will a redesign automatically improve SEO?

No. It needs to preserve useful content and address specific problems. URLs, metadata and links are part of the migration work.

Can we keep the domain and page addresses?

Yes. Keeping them is the starting point. Any change should have a clear reason and an explicit migration plan.

Does a redesign require a different platform?

A redesign can retain the platform if it still meets your needs. We compare possible improvements with the cost of moving content, functions and editing workflows to another solution.

WordPress is one of Gloria’s implementation options. Moving to it should address a specific need; other platforms and integrations are assessed before any commitment to deliver the work.

Discuss the reasons for your redesign and what you want to retain

Tell us what is prompting the redesign and what you want to retain.

Discuss your project

A practical example

Example redesign brief: the problem, proposed changes and launch checks

This illustrative brief connects the business problem, the proposed changes and the checks needed before launch. It helps you compare proposals on the work that matters.

People discussing a project around notes and a laptop — Fictional planning example. The actual brief and acceptance criteria are agreed for each project.