Planning a website redesign? Decide these things before the first mockup.

Define the decision the website supports

Choose the primary action for each important page. A service prospect might request a consultation, a moving customer might ask for an estimate and a client might sign in for support. These actions should follow from the information on the page rather than compete for equal attention everywhere.

Write the main journey in plain language: who arrives, what they need to understand and what they should do next. This gives the designer and developer a shared purpose. It also makes feedback more useful than deciding whether a layout simply feels modern.

Inventory the content that already matters

Review the current service pages, useful resources, customer-facing documents and pages that receive relevant attention. Decide what remains, what needs improvement and what can be removed. Keep URL changes deliberate and include redirect planning where appropriate.

Do not assume a new site should start from an empty content folder. An established business may have useful information hidden inside an awkward structure. The redesign can make that information easier to find while replacing vague or outdated material with clearer explanations.

Plan the content before polishing the layout

Identify the service definitions, project information, images and approvals needed for the site. If a page depends on a client quote or a result, confirm permission and the underlying facts before building the design around it. If the team cannot supply the information, change the content plan rather than filling the gap with an invented claim.

A content review also exposes missing decisions. Who owns the contact inbox? What happens after an inquiry? Which services are available remotely? Answering those questions early prevents attractive pages from making inconsistent promises.

Make mobile use part of the design

A responsive layout is more than fitting a desktop page into a narrow column. Review navigation, reading order, tap targets, forms, sticky elements and the way a user returns to the main journey. A decorative animation should not hide information or make a phone harder to use.

Performance belongs in the same conversation. Core Web Vitals describe loading, responsiveness and visual stability. We assess those concerns alongside readable text, sensible images and interaction testing. A single test score does not replace checking the actual tasks people need to complete.

Define the launch and handover

Before launch, agree who controls the domain, hosting, business accounts and ongoing support. Test contact routes and any account or payment journey in the appropriate environment. Keep a record of the previous configuration so a rollout problem has a clear recovery path.

After launch, someone must own content updates, technical care and the review of actual inquiries. Your proposal should distinguish the initial build from those ongoing responsibilities. This makes the new site an operational asset rather than a project everyone considers finished when the homepage is approved.

Choose a partner for the whole journey

Run It Right combines website design and development with search, automation and ongoing technical consulting. We can help define the right rebuild or identify a smaller improvement when the foundation is still useful. Start with what the business needs the website to accomplish.

• Primary customer tasks and calls to action.
• Content inventory and ownership.
• URL changes and migration responsibilities.
• Mobile, form and performance checks.
• Launch access, recovery plan and ongoing care.