FOR BUSINESS OWNERS
Improve or redesign your company website?
An outdated website does not always need to be rebuilt. Start with the problem it creates for your customers and your team, then choose the smallest sensible scope that solves it. This guide helps business owners across Saudi Arabia and the GCC compare focused improvements with a broader redesign.
Name the problem before choosing the project
Write down what visitors or staff struggle to do. A supplier might receive vague requests because product specifications are missing. A consultancy might get repeated questions about services its website never explains. A retailer might have accurate products but an awkward mobile contact route. These are different problems and may need different scopes.
Use customer questions, recent enquiries, staff feedback and available search or traffic data as evidence. A site’s age or a single low score is not enough to decide. If there are few enquiries, first establish whether relevant visitors reach the site at all.
Compare the scope before you commit
Use these distinctions to frame the review, not as an automatic score. Several symptoms can share one cause, and an isolated fault can still be urgent. Confirm the cause before choosing the work.
| Area to review | A focused improvement may fit | A broader review may fit |
|---|---|---|
| Content and offer | A few pages need current details, clearer wording or stronger approved examples; the overall structure still fits. | The business has changed substantially and its services, audiences or content no longer fit the website’s structure. |
| Mobile use and navigation | A specific menu, page layout or obstructive element causes a repeatable problem that can be fixed in the current setup. | Problems recur across key page types and prevent common customer tasks; review the shared layout and navigation together. |
| Enquiry journey | Contact details, a call to action or form delivery needs repair; the rest of the buying journey is clear. | Visitors cannot connect services, evidence and the right enquiry route across the site; the journey needs to be planned as a whole. |
| Arabic and English | An existing language version needs terminology, missing labels or a few right-to-left layout corrections. | Adding a complete language experience may require changes to the content structure, templates or enquiry flow; assess those requirements before choosing the build. |
| Editing and platform | The team needs access, training or a manageable configuration change, and the existing platform can support the requirement. | Required functions or maintainability cannot reasonably be supported in the current setup; investigate the options and transition effort. |
Try the route a real customer needs
On a phone, start from a service or product page rather than only the homepage. Can a visitor understand the offer, find relevant evidence and take the next step? Check text size, menus, downloads, links and anything covering the content. Repeat the useful routes in Arabic and English when you serve both audiences.
Test a form with a clearly labelled enquiry. Check required fields, errors, confirmation and delivery to the right mailbox. Test booking or checkout separately if your business uses it. A broken enquiry route deserves prompt attention even when a larger redesign is being planned.
Keep the parts that still serve the business
Inventory useful pages, photographs, product details, work examples, downloads, forms and connected systems. Check what is accurate, approved and still needed. Decide explicitly what to keep, edit, combine or retire. A hotel’s current location information or a distributor’s useful catalogue should not disappear because the visual design changes.
Keep a suitable domain and useful page addresses where possible. If an address must change, map its relevant replacement and plan a permanent redirect. Do not send every retired page to the homepage. If content is gone and has no relevant replacement, handle its removal explicitly. Ask the team to check internal links, language links and the sitemap against the final structure.
Plan a controlled release
Review a working preview before changing the public site. Agree the final pages, content approver, publication steps, responsible people and a recovery option. Confirm that domain, hosting, business email and other connected accounts remain accessible to the business. A website update should include checking the effect on existing email and integrations.
Test mobile pages, navigation, forms and any changed addresses before launch, then check the published result. Avoid bundling a new domain, platform change and visual redesign into one switch without a clear need. Search visibility can fluctuate after significant changes; careful preparation reduces avoidable problems but does not guarantee unchanged rankings.
Define what a useful improvement would look like
Agree an observable goal: customers can find the right service, staff can update content, or a mobile enquiry reaches the right team. Record the current situation before making changes, then review comparable periods and customer feedback. Separate relevant business enquiries from spam, job requests and tests; a delivered message is not automatically a qualified opportunity.
Search visibility, aggregate traffic and actual enquiry records answer different questions. Verify any measurement you choose separately from form delivery. A new design alone cannot guarantee traffic, enquiries or sales, and low visitor numbers may not support a reliable before-and-after comparison yet.
BEFORE THE FIRST CONVERSATION
Prepare enough to explain the need
Start with the situation you want to improve. The scope can follow the evidence.
Your website and priority problem
Share the address and one or two specific tasks that are difficult for customers or your team.
Evidence and useful content
Bring relevant customer questions, approved material and any existing search, traffic or enquiry records you can share.
Access and dependencies
Identify who controls the domain, hosting, content system, email and integrations. Do not send passwords in an enquiry.
Responsibilities and timing
Name the content approver, important business dates and any budget range. Exact technical specifications are not needed for an initial conversation.