Skip to content
العربيةLet’s talk

Practical guide

Arabic–English website launch: a practical acceptance checklist

Check Arabic and English content, RTL layouts, enquiry forms, language links and search settings before accepting a new company website.

Lava Solutions · · 4 minute read

Hand-drawn website layouts on paper, with blue, purple and green watercolor sections.
Illustrative stock photo. Photo: Hal Gatewood / Unsplash.

A bilingual company website is ready to launch when an Arabic-speaking visitor and an English-speaking visitor can understand the same offer, complete the intended task and reach the right team. Approving the homepage design alone leaves important questions unanswered: does the Arabic form work, does the language switch preserve the page, and can search engines reach both versions?

Use these checks as an acceptance plan for a new website or a major redesign. Agree the pages, devices, test cases and responsible reviewers before the final delivery meeting. This is a starting point for project acceptance, not a complete accessibility or security audit.

1. Approve a page-pair inventory

Create one row for each intended page pair: English URL, Arabic URL, purpose, content owner and review status. Start with services, industries, company information and contact. Include downloadable documents and confirmation messages if they are part of the journey.

Google recommends separate URLs for language versions. It determines a page’s language from visible content rather than the HTML language attribute. An Arabic navigation bar surrounding an English service description therefore does not make a useful Arabic counterpart.

Ask a reviewer fluent in Arabic to compare meaning, not sentence count. Service scope, exclusions, contact details and next steps should agree. Local examples and phrasing may differ where that improves understanding. Mark missing translations explicitly instead of presenting them as completed pages.

2. Test Arabic reading and mixed text

The W3C guidance on text direction distinguishes language from direction: an Arabic document needs an appropriate language declaration and right-to-left base direction. Setting lang="ar" does not itself set dir="rtl".

Review rendered pages on a phone and a desktop. Include a long Arabic heading, a multi-line button, a table, an email address and a product code. Look for clipped text, misplaced punctuation, poor image crops and horizontal movement that makes paragraphs difficult to read. Do not assume every icon, number or logo should be mirrored.

Fictional test example: place the product code AB-120, an English brand name and an Arabic sentence together in a test card. The reviewer should be able to identify and copy the code exactly. Record the browser and screen size when reporting a fault so the developer can reproduce it.

3. Follow the complete enquiry journey

Open a service page directly in each language, switch languages and submit an agreed test enquiry. Use a clearly marked test identity and a controlled destination. The language control should reach the genuine counterpart where one exists; if it does not, make the fallback destination clear.

The W3C form-label tutorial explains why controls need descriptive, associated labels. Test labels and instructions in both languages, then check the outcomes:

  • Required-field and invalid-email messages are understandable in the chosen language.
  • Arabic names and mixed-language messages survive submission without corrupted characters.
  • The confirmation explains what happened and the next step, without claiming a reply time the business has not agreed.
  • The receiving inbox or CRM contains the intended enquiry and identifies the responsible team.
  • Keyboard users can reach the language control, fields and submit button in a sensible order.

A success message proves only what the system has actually confirmed. Verify the receiving record before accepting the flow. Our enquiry-to-CRM workflow guide covers ownership and follow-up after that handoff.

4. Check the published search signals

Ask for the final page-check results, not a screenshot of a plugin’s green indicator. Google’s language-alternate guidance requires each version’s hreflang annotations to include itself and the other versions, using full URLs and reciprocal links. Only identify a real translated counterpart.

CheckAcceptance evidence
Page accessEach agreed public URL opens the intended complete page without a sign-in or unintended redirect.
Language metadataThe title and description describe that language’s page; language controls and alternate URLs reach matching content.
Canonical URLThe preferred address agrees with internal links and the sitemap; translated pages retain a canonical in their own language.
Indexing controlsCheck HTML and response headers for an unintended noindex rule, and review crawler access separately.
ReleaseThe tested content is on the production domain, with the deployment identifier and check date recorded.

Google’s canonical guidance recommends consistent preferred URLs and same-language canonicals when using language alternates. Its noindex documentation covers both HTML tags and HTTP headers. Removing a staging restriction is a launch check; it does not prove Google has indexed the page.

5. Close defects and assign ownership

Keep an acceptance log: URL, language, expected result, actual result, evidence, owner and retest status. Agree which failures block release. A broken Arabic enquiry form should not disappear into a general list of cosmetic improvements. Retest fixes in both languages because shared components can affect both.

After launch, use Search Console to monitor discovery and indexing separately from enquiries. Google explains that requesting a crawl does not guarantee inclusion in search results. Assign someone to maintain translations when services change, so both versions stay useful.

For a bilingual website project, review Lava’s website services and send the proposed page list and main customer task. These give the team a concrete starting point for scope and acceptance criteria.

Sources & further reading

A useful next step

Bring one real workflow.

Share the process you want to improve, the systems involved and the decision you need to make.

Talk to Lava ↗