Website development

PROJECT PLANNING GUIDE · Saudi Services AI

What should your Arabic and English website include?

A website quote is easier to compare when both sides are discussing the same pages, languages and customer journeys. Use this guide to organise the requirements before design and development begin.

Prepare your website brief

Define the action each page should support

Decide whether visitors should understand a service, request a quote, book a consultation or buy a product. Map those actions to the pages needed to support them. A service business may need a homepage, individual service pages, genuine work examples and a contact destination. A shop also needs product information, basket, checkout and order handling. Agree the actual journeys rather than starting with a large page count.

Build a language and content inventory

List every required page and identify its Arabic and English content owner. Include navigation, buttons, form labels, validation messages, confirmation screens and downloadable material. Agree who writes, translates and approves the copy. Review terminology, brand names, contact details and product identifiers. A language switch should lead to the corresponding page, so a customer reading a service does not have to start again at the homepage.

Design Arabic as a complete experience

Arabic pages need appropriate reading direction, typography and layouts. Test long headings, navigation, forms and mixed Arabic text with phone numbers or model codes. Keep content and actions readable on a phone. Google recommends indicating equivalent language versions; the implementation can include reciprocal language links and a sitemap listing the translated pages. Those signals support language relationships while the visible text still needs a proper translation.

Specify integrations and ownership

Name the systems the website needs to use, such as an approved enquiry destination, booking service, product inventory or payment provider. Agree account ownership and who supplies access. Include error and confirmation states in the scope, then test the entire journey before launch. Also define who owns the domain, source code and assets, and what instructions the business receives for updating content.

What changes the cost and delivery plan?

A bilingual brochure website and an online store have different requirements. Cost depends on the page templates, content production, translation review, custom design, integrations, migration and maintenance included. Compare proposals using a shared page list and deliverables. Separate one-time development from ongoing hosting, provider charges and support. Agree review milestones and dependencies rather than assuming a delivery date before the content and integration requirements are known.

Agree a launch acceptance checklist

Before approving launch, review every agreed page in both languages on mobile and desktop. Test links, forms, customer confirmations and integrations using the agreed method. Check the migration redirects if replacing an existing website, and confirm the language destinations and sitemap. Agree how faults will be reported and handled after handover. Keep a record of account ownership, delivered assets and the support period included in the proposal.

Bring these details to the project discussion

  • Business goal and customer actions
  • Page list with Arabic and English requirements
  • Approved logo, content and image assets
  • Required integrations and account owners
  • Existing URLs to preserve or redirect
  • Delivery milestones, acceptance checks and support scope