Your English and Arabic pages are both live, but the wrong language sometimes appears in Google Search. Start with a pair of equivalent pages and check whether their language annotations point to each other and to the URLs you actually want indexed. An annotation can help Google select an appropriate version. It does not dictate every result.
Pick one page pair with the same purpose
Start with an important page such as a delivery policy or a product detail page. Open both URLs without being logged in. Confirm they load directly, display the intended language and give visitors a way to switch to the equivalent page. A product detail page and an Arabic category page serve different purposes, even if both mention the product.
Check both directions and the canonical
In the delivered HTML head, or in your chosen sitemap or HTTP-header implementation, look for the full alternate URLs. A UAE-specific pair can use ar-AE and en-AE where both pages are intended for that market. Both versions should list the same pair, including themselves. If the Arabic page omits the return link to the English page, Google can ignore that relationship. Google’s localized page documentation explains return links, language codes and the optional x-default fallback.
Check the canonical on each page alongside the alternates. For two distinct, indexable translations, each would ordinarily identify its own URL as canonical. If the Arabic page points to the English one as canonical, ask why before changing the annotations. Also check whether either URL redirects, returns an error or carries a noindex directive. Link to the final intended URL in the chosen implementation.
Fix the template, then sample beyond the homepage
Try a product page, a service page and one recently moved URL. If several Arabic pages point back to the English homepage, the translation template may be falling back to a default URL when an equivalent page is missing. Fix that rule and omit the missing counterpart until it is available. After release, check the live output and use Search Console’s URL Inspection to investigate representative URLs. Allow time for recrawling and avoid judging the change from one search on one device.
For site planning, see the Arabic–English website guide. ITZ’s website development service can review how a CMS generates alternates and canonicals. Share a page pair that shows the issue.
Request a bilingual page audit
Provide two equivalent URLs, the markets they serve and one example of the result you observed. Use the form to discuss which language pairs, templates and redirects ITZ should review. Request a Bilingual Page Audit
