A website can look newer without becoming more useful. Before commissioning a redesign, identify what visitors need to accomplish and what prevents them doing it now. For a service business, that may mean understanding the offer and sending a well-scoped enquiry. For a retailer, it may mean selecting the correct product and completing checkout. Those are different design problems.
Inventory the current content
List existing pages, downloads, forms and important links. Note which pages explain distinct services and which repeat the same information. Use available evidence to identify useful entry pages, but do not invent traffic figures if measurement is absent. Decide what to keep, revise, combine or retire before changing the navigation.
If a useful page address must change, plan an appropriate redirect to its replacement. Avoid sending every retired URL to the homepage regardless of meaning. Check the new internal links and sitemap against the pages that actually exist rather than copying the old structure without review.
Make each service understandable
A reader should quickly understand who the service suits, what it includes and how to request a quote. Use a clear heading, a concise explanation and practical supporting detail. Show nationwide delivery where it is genuinely offered while keeping the business address accurate. Do not manufacture branch offices or populate pages with repeated place names simply to appear broader.
Use real experience and approved evidence. When named client outcomes or testimonials have not been supplied, do not replace them with invented results. Helpful guidance, transparent package scope and a good briefing checklist are preferable to unsupported claims.
Keep the enquiry process accessible
The W3C Web Accessibility Initiative recommends clear labels, instructions, validation and notifications for forms. Ask only for information needed for the task. Explain errors in text, keep the user’s input where appropriate and show a clear success state. Test with keyboard navigation as well as a mouse or touch input.
Consider the information being collected. A sales enquiry does not need passwords, payment-card details or confidential client records. Describe the next step honestly: a submitted form may create an enquiry, but it does not automatically confirm a booking, payment or delivery date.
Specify content and operational ownership
Agree who supplies copy, imagery and approvals, and who maintains the site after launch. Separate hosting from maintenance and future development. Confirm what happens when staff need to change a service, update a package or correct an article. A content editor is useful only if the public pages actually use the content being edited.
Test the launch as a customer journey
Check the main service routes, pricing links, enquiry prefills, errors and confirmation states. Inspect important page titles, descriptions and canonical links, and ensure private pages are not presented as public search content. Check image loading and readable text on the actual layouts. A successful build alone does not demonstrate that the full enquiry journey works.
Compare quotes by scope
Ask each provider to specify page count, content preparation, integrations, accessibility checks, handover and ongoing costs. MBICT’s website package amounts are indicative, with final scope and tax treatment confirmed in writing. Basic hosting belongs only to the stated starter scope, with duration and limits agreed; it should not be assumed to accompany every package.
Explore custom web design across South Africa and the website cost guide. For search-specific planning, read the SEO and AI search guide before treating a visual redesign as an automatic ranking improvement.