Bilingual sites and search visibility
Most bilingual Arabic sites are bilingual in name only: both versions share one URL toggled by a button, so Google indexes one language and the other disappears. I build each language as its own tree, with its own URLs, self-referencing canonicals, and reciprocal language links.
What the engagement includes
- A separate path per language, with permanent redirects from old URLs
- Reciprocal hreflang on every page, plus x-default
- Self-referencing canonicals, never pointing across languages
- Titles and descriptions written natively in each language, not translated
- Separate XML sitemaps per language
- Structured data that describes what the page actually shows
How the work runs
-
01
Diagnosis
How Google sees the site today: what is indexed, what is duplicated, what is missing.
-
02
Language structure
Choosing the URL shape and the redirect plan from old links without losing rankings.
-
03
Implementation
URLs, signals, and sitemaps shipped, then every page type tested in both languages.
-
04
Measurement
Search Console wired per language, with indexing watched through the first month.
Work delivered with this service
-
Badr Farhan Al-Ahmad Office
Badr Farhan Al-Ahmad Office
Common questions
Do I need a paid translation plugin?
Not necessarily. When the content is finite and written by you, the URL structure alone is enough, and it stays faster and cheaper long term.
Will my current rankings be affected?
Any URL change carries risk, which is why the work starts with a permanent redirect plan for every old link, and indexing is watched after launch.
Which language should be primary?
The one your buyer searches in. For a Gulf business selling locally, Arabic on the root and English as the branch.
Contact
Start by describing your project.
Write what you want built and when you need it. I reply within one business day with a straight answer and a clear next step.