What to check when an Arabic page is indexed under the wrong URL
You find the Arabic page in search results, click it, and land on an English URL with an Arabic-looking title. Or the reverse. Annoying, and not immediately obvious why.
It could be a canonical pointing at the wrong page, a language annotation that doesn’t match, a redirect, or just a reporting mix-up. Before changing anything, pin down what “wrong URL” means in this case.
Multilingual SEO involves several signals that work together, and none should be added as decoration. Diagnose the exact URL, its content and the version Google selected. Then make the relationship between language equivalents clear and consistent.
Confirm the URL and the page
Copy the full URL from the search result. Does it load directly, redirect, or change after the page renders? Look at the visible language, title, canonical tag and response status. Search Console’s URL Inspection shows Google’s selected canonical and whether the page is indexed, though the data may lag behind a recent change.
Compare the result with the Arabic page you meant. Is it really an Arabic version, or an Arabic title wrapped around mostly English content? Does the URL represent a distinct page for the same audience and purpose? If the pages differ substantially, they may not be language equivalents, and you shouldn’t force them into a pair.
Inspect canonical signals first
A canonical tag names the preferred URL among duplicate or very similar pages. An Arabic page that canonicalises to an English page may be intentional for a true duplicate, but for genuine language alternatives it’s usually a warning. Check the rendered source, not only the CMS setting, and look for multiple tags or an app overriding the intended value.
Canonical signals are hints, not commands. Google can choose a different canonical based on all the evidence, including redirects, internal links, sitemaps and page similarity. Don’t keep changing tags without knowing which system emits them. When I’m handed a case like this, I ask first which plugin or theme file writes the canonical. Find the owner of the template or app that generates them.
Review language annotations and links
If the site uses hreflang, check that each URL references itself and its valid alternatives, and that the reciprocal references exist. Language and optional region codes must identify the version correctly. The target should return a working page that serves the declared language. A link to a generic homepage is no substitute for a missing product equivalent.
Check internal links, the language switcher and sitemap entries too. If navigation keeps pointing English users at the Arabic URL, Google gets mixed signals about which version belongs in which journey. The switcher should keep context when a real equivalent exists and explain what happens when it doesn’t.
Look for redirects and duplicate paths
Sites collect URL forms over time: uppercase and lowercase, trailing slash variants, parameters, legacy paths, translated slugs. Trace each one and see whether it redirects to the intended canonical. A chain of redirects, or a redirect to the wrong language, can make the symptom look like an indexing problem.
Use a small table: searched URL, final URL, page language, canonical, hreflang target, sitemap status and internal links. Compare the affected examples. If only one template is wrong, the fix belongs in the template. If only one product is affected, check its data and page-specific configuration before changing sitewide rules.
Avoid fixing the wrong layer
A result can show the wrong URL because the page is poorly titled, a redirect sends visitors elsewhere, or Search Console is showing a historical version. Separate what the user sees from what the crawler has processed, and record both. If the live page is right and the report is old, repeating the edit just creates new problems.
Automatic redirects based on location or browser language make pages hard to inspect and can stop people reaching the version they want. I’d offer a visible switcher and keep URLs stable.
Make a correction you can verify
Choose the fix the evidence supports: correcting the canonical, restoring a reciprocal hreflang reference, updating a redirect, fixing the switcher or consolidating duplicates. Don’t make several unrelated changes at once if you can isolate them. After deployment, recrawl the examples and inspect them in Search Console over time.
Google may keep showing a previously selected URL while it recrawls and reassesses. A short delay doesn’t prove the fix failed. Keep the change record and compare the same URLs later, noting anything else that changed.
Make language ownership explicit
For each page, someone should know which language version is primary for its audience, who reviews the translation and which URL is its equivalent. This matters most when local content differs instead of mirroring the English word for word. Document why a page isn’t a direct translation, so reviewers know whether to link it as an equivalent. The goal is to represent the real relationship, not make every pair look symmetrical.
Related reading
- Planning Arabic content with seasonality and local context
- Arabic page titles that describe the page without keyword stuffing
- What to test when an Arabic site changes its URL structure
If an Arabic URL is appearing where you expected English, or the other way round, start with that exact result and trace its signals. Which URL is Google choosing, and what evidence might have led it there?