Give each language its own real URL
A bilingual site is easier to interpret when each language has its own stable, indexable page such as /ar/services and /en/services. Use a self-referencing canonical for each equivalent page, and link the translations with reciprocal hreflang annotations. Do not point every Arabic page to an English canonical.
Put useful text in the initial HTML
Search crawlers and AI retrieval systems need access to content. Server-render the main heading, explanatory paragraphs, service details and useful internal links. Do not hide everything behind click-only interactions or client-side data loading. Test the HTML response, not just what the browser displays after JavaScript executes.
Translate intent, not only labels
Arabic and English customers may use different search terminology for the same service. Write clear descriptions and direct answers in each language while preserving the same underlying facts. Never claim customer results, certifications or coverage areas that have not been verified.
Validate the technical signals after deployment
Confirm HTTPS canonical URLs, working language alternatives, sitemap inclusion, crawl permissions, meaningful headings and structured data that matches visible text. Google does not require special markup to qualify for AI Overviews; strong foundational SEO and helpful content remain central.