WordPress redesign: update your services, design and editing tools

We begin by reviewing your actual services, customers and current website, then compare relevant competitors and useful design references. The aim is to identify what the offer should explain better and which working parts should remain. A competitor's theme, plugin or page count is not a reason to reproduce its website.

Keyword research follows these decisions. For a salon offering the services, “hair colour consultation [city]” and “balayage appointment [city]” are possible intentions to investigate. Search information, customer questions and existing page performance help prioritise the content. We distinguish the need for a clearer service page from the need for another tool or integration.

The outcome guides the revised navigation, photographs, service descriptions and links to your booking or enquiry system. We also identify URLs and useful content to preserve. Success is assessed through agreed customer actions and commercial records where available. The proposal defines the research, editing and implementation scope rather than assuming every WordPress page needs rebuilding.

Before replacing a website, list the tasks it makes difficult. Perhaps staff cannot update services, visitors struggle to find the right offer, or an enquiry form is unreliable. These are different problems. A visual refresh may address one, while a performance fix or a change to a single page may address another. A full redesign becomes useful when the structure and tools no longer fit how the business operates.

Swipe across the table to see every column.

Use this list as a starting brief. It helps distinguish an essential change from an attractive addition, and gives the project a practical test of success before anyone chooses colours or layouts.

A fictional training provider has popular course pages, downloadable programmes and an enquiry form connected to an external system. During a redesign, two courses are combined and an older course is discontinued. The important work is deciding what each visitor should find when following an old link.

Make a decision for each important address

A retained course can keep its address while its content changes. The two combined courses may lead to one genuinely equivalent page, with the relationship recorded. A discontinued course without a replacement should not automatically send visitors to the homepage. The project needs an explicit decision about the useful information, if any, that should remain available.

The migration register should also include linked documents and the external form destination. A page can look correct while its programme download is outdated or its enquiry enters the wrong workflow. This example is illustrative, not a Gloria case study. It shows why moving pages and preserving a working business journey are related but separate tasks.

The starting condition affects the scope: custom features, unsupported components, inconsistent content and changing customer data all need attention. The standard redesign offer displayed on this page has defined boundaries. Moving an active shop, a membership system or complex booking data requires an assessment of those functions rather than an assumption based on page count.

Prepare a list of essential URLs, integrations, licences and people who edit the site. Identify data that continues changing while the new version is prepared. A copy made earlier may not include later orders or updates, so the transition plan must state what needs synchronising and who approves the changeover. You continue to buy and renew your own domain; hosting remains a separate decision.

• Open representative old links and confirm that each reaches the intended answer.
• Check key information, downloads and contact details against the approved content.
• Send test enquiries and verify receipt in the correct mailbox or external system.
• Agree the backup, approval and response arrangements for a blocking issue during launch.

Keep a record of checks and unresolved items. After launch, review the affected journeys and technical signals separately from normal fluctuations in visits. A redesign can be carefully managed without promising that traffic will never change.