A small business website redesign should begin with a problem you can describe. Perhaps visitors cannot find the right service, the quote form is difficult to use on a phone, or staff cannot update important information. A clearer brief helps you choose whether to improve a few pages or rebuild the site.
1. Define the customer journey and the business goal
Choose the main action the website needs to support: an enquiry, appointment, estimate request or purchase. Write down who the customer is, what they need to understand and what makes them hesitate. “Make it modern” is a design preference; “make our service area and estimate process clear on mobile” gives the project a testable purpose.
Keep the first scope manageable. A contractor may need stronger project information and a useful estimate form. A professional practice may need clear services, credentials and appointment options. The same page structure will not suit every business.
2. Record what is already useful
Create an inventory of existing pages, downloads, forms, phone numbers and connected tools. Note which pages bring relevant visits or enquiries when reliable data is available. Ask the people who answer customer questions which information is missing or out of date.
| Keep or review | Why it matters | What to record |
|---|---|---|
| Useful pages and URLs | Existing visitors and external links may depend on them | Current address, purpose and planned destination |
| Content and images | A redesign may reuse valuable assets | Accuracy, ownership and permission to publish |
| Forms and integrations | A visual change can interrupt enquiry delivery | Recipient, stored record, confirmation and fallback |
| Analytics definitions | Comparisons need consistent measures | Events, exclusions and any known gaps |
3. Protect page addresses when the structure changes
Keep useful addresses where practical. If a page must move, map its old URL to a relevant replacement and implement a suitable permanent redirect. Update internal links and the sitemap, then check the actual journeys. Avoid sending every removed page to the homepage regardless of relevance.
Google’s site-move guidance explains URL mapping, redirects and monitoring. Search visibility can fluctuate after changes; no redesign can promise to preserve every ranking.
4. Review the content before polishing the visuals
Make the main service, real coverage and next action easy to understand. Replace vague claims with evidence customers can inspect, such as genuine project details or current credentials. Use a short quote form that asks for enough information to respond without demanding unnecessary personal data.
Create a page outline before choosing animations or decorative effects. Review headings, body text, buttons and confirmation messages as one journey. Original imagery should support the explanation rather than imply work or results the business has not delivered.
5. Agree the launch checks and the owner
Test the site on an ordinary phone and with a keyboard. Review readable text, image size, link destinations and form errors. Send a clearly labelled test enquiry and confirm that the right person receives it. Check redirects, indexing settings and measurement after deployment.
Take a current backup and agree how to restore service if launch checks fail. Record who owns the domain, hosting, accounts, updates and content changes. A handover should explain how to maintain the site as well as how to edit a page.
Prepare a brief you can compare
Your brief should name the goal, audiences, pages, useful assets, integrations, responsibilities and acceptance checks. Separate initial build work from ongoing hosting, maintenance, licences and content support. Use the project-scope guide to prepare questions rather than compare headline prices alone.
Build Awesome’s website design and development service can help turn that brief into a practical scope. Use our KPI guide to choose measures, or request a review of your existing website.
