Arabic, French or both: choosing the language of your website

The language of your site is decided by who you sell to, not by which one sounds more professional. If your buyers are consumers holding a phone, Arabic is the first edition. If your buyers are companies that send a written request for quotation and pay on an invoice, French usually is. The answer flips to both when a second audience is large enough to justify a permanent content cost — and it is a permanent cost, because code is translated once and content is written again every month.

Who is actually searching?

Start with evidence you already own. Search Console lists the queries that brought people to the site, in the script they were typed in. If the Arabic queries are there and the French ones are not, the market has answered. If there is no data yet, look at how enquiries arrive: a message written in Arabic on a phone is a different buyer from an email with a company header and a reference number.

The two audiences do not search the same way. A consumer types a product and a city into a phone. A buyer in an administration or a company types a service and a supplier category into a desktop, often in French, because that is the language of the paperwork they will have to produce. A diaspora customer may search in French while reading Arabic comfortably. One site cannot be tuned for all three, which is why the first edition picks the one that pays.

Why one address per language, never a toggle

A language switch that replaces the text in place leaves one address holding two languages. A crawler fetches that address once, sees whichever version the server chose to send, and indexes that. The other language exists for the visitor and not for the index — so it cannot be found by someone who does not already know your name.

Each language needs its own address, its own title, its own description, and its own content. The switch becomes a link between two addresses, not a script that rewrites the page. Google's guidance on making links crawlable is mostly about ordinary navigation, and the same principle applies here: if the other language is reachable only by JavaScript, it is reachable only by people.

What does hreflang actually claim?

It is a claim, not a mechanism. You tell the search engine: this address and that address are the same page in different languages; show the right one to the right reader. The claim has to be reciprocal — each page lists the other and itself — and it has to use a valid language tag. The W3C's explanation of language tags covers the format: a primary tag such as ar or fr, optionally with a region such as ar-DZ. A malformed tag is ignored, quietly, and nothing tells you.

Two mistakes recur. Pointing both language versions at the same address, which claims nothing. And setting hreflang while leaving the pages with the same title, the same description and near-identical text, which tells the engine the two pages are duplicates rather than translations.

What does a second edition really cost?

The code is the cheap part: a second menu, a second set of interface labels, a second set of address patterns. That is a small build, not a project.

The content is the expensive part and it never ends. Every service page is written twice. Every price change, every new photograph, every legal update, and every case study is done twice. Translation is not the same as writing: a French paragraph rendered word for word into Arabic reads like a machine wrote it, and readers in this market notice within a sentence. Someone has to write the Arabic as Arabic.

There is an operational cost too, and it is usually missed. A French page that leads to a WhatsApp number answered only in Arabic loses the lead at the last step. Whoever replies to messages has to be able to reply in the language of the page that produced them.

Is Arabic-first the right default here?

For most businesses selling to households in Algeria, yes. Arabic is the official language, French carries much of administration and business, and the buyer with a phone is reading Arabic. A site that opens in Arabic, with prices and delivery terms stated plainly, answers the question that buyer is asking.

Arabic-first also forces the right foundation early. Direction, fonts and layout are built for right-to-left from the first page, which is cheaper than retrofitting them onto a site designed left-to-right.

Your buyer	Start with
Households, on a phone	Arabic, French when there is someone to write it
Companies, tenders, invoices	French, Arabic for the public pages
Both, with staff for both	Both, one address each, same day
Buyers outside the country	English first, then the market's language

How do you decide, in order?

1. List the three questions buyers actually ask before they pay, and write them in both languages.
2. Check which language those questions arrive in today: messages, calls, the search queries you already rank for.
3. Choose one first edition. Write it properly rather than writing two badly.
4. Give that edition a language-specific address and a clean title.
5. Add the second edition when a named person is responsible for writing and maintaining it — not before.
6. Add hreflang only when both addresses exist and both are finished.

Where this goes wrong

• Translating the whole site with a tool. It is fast and readable, and it signals that the Arabic reader was an afterthought. The cost is trust, which does not show in analytics.
• A toggle with one address. The second language is invisible to search and to anyone who has not already found you.
• Hreflang on unfinished pages. A pair pointing at a page that says "coming soon" is a claim the engine can verify and discount.
• One writer for both languages. The result is one good edition and one that reads like a translation, and the weaker one is usually the Arabic.
• Adding the second language and abandoning it. A French page whose newest item is two years old is worse than no French page, because it is a statement about how you maintain things.
• Different facts in each language. If the Arabic page lists a delivery area the French page does not, the buyer who reads both stops trusting both.

What this advice does not cover

It does not settle which language your advertising, packaging or invoices should use — those follow regulation and habit, not search. It says nothing about Tamazight, about regional dialects in spoken content, or about the price of a professional translator, which varies with the subject. It also assumes the site has enough pages for a second edition to mean anything: five pages translated do not create a French market, they create a French brochure.

We build bilingual sites where each language has its own address, its own text and its own reason to exist.