A website in Albanian, Italian and English: how to do it well (and why machine translation hurts)
A site “in three languages” with a Google Translate button is not in three languages: it is in one language with two versions Google does not rank and the client does not read.
Why three languages in Albania
Albanian for the local market and Kosovo. Italian for tourists, property buyers, patients, Italian companies, the diaspora in Italy: the first foreign market. English for everyone else: Poles, Germans, Scandinavians, British, investors. For businesses with foreign clients, every language added well is a new market with little competition.
What “written for the market” means
The Italian page “Hotel a Saranda” is not a translation of “Hotel në Sarandë”. It speaks to the Italian: how to get there from Bari, why Sarandë versus Corfu, prices compared with Puglia, Italian spoken at the hotel, the food. The keywords are what the Italian searches for, not translations of the Albanian ones. Google ranks it because it is real content; the client reads it because it speaks to them.
Why machine translation hurts
Google recognises machine-translated text and does not rank it: to Google it is low-quality duplicate content. Clients recognise it from the errors and lose trust: a hotel with broken Italian looks careless. And the wrong keywords do not appear for real searches. The translation button is worse than no language at all.
URL structure
One folder per language: /it/ and /en/ with Albanian at the root, or the reverse depending on the main market. Every page has its version: /sherbimet/seo/, /it/sherbimet/seo/, /en/sherbimet/seo/. Folder names can stay in Albanian or be translated; what matters is stability and redirects if they change. Never parameters (?lang=it): Google does not treat them as separate pages.
Hreflang
Every page declares its versions in the other languages with hreflang tags, so Google shows Italians the Italian version and not the Albanian one. Without hreflang, Google confuses the versions, considers them duplicates and ranks none. It is the technical detail most Albanian multilingual sites lack, and it decides half the result.
Titles, descriptions, images
Every version has its title and description in its own language, written for that market’s searches. Image alt texts in the language. File names can stay the same. Menu, buttons, error messages, thank-you page: everything in the version’s language. One Albanian detail on the Italian page spoils the experience.
Forms and replies
The Italian form sends an email showing the client’s language. The reply must be in Italian, within 24 hours, from someone who speaks it. The site promises three languages; the business must keep them: one person for Italian, one for English, at least with ready texts. Without that, the multilingual site brings clients who leave disappointed.
The Google profile per language
Google Business Profile allows the description in several languages and shows reviews in the searcher’s language. Italian reviews are the ones that weigh for Italians: ask for them in Italian. Profile posts can alternate. Name, address and phone identical in all site versions.
Who writes
Albanian: someone who knows the business. Italian: an Italian or bilingual copywriter who knows the sector (not an Italian student). English: the same. The agency must say who writes each language. The cost of texts in three languages is the biggest part of a multilingual site, and the part that brings the result.
Costs
An added written language costs a good part of the base site: it is 20-30 pages of new text, not a module. For a business site, three written languages double the cost of one language and triple the markets. For tourism, real estate and medical businesses, the return is immediate: foreign clients pay more.
Maintenance in three languages
Every new page or change must be done in three versions: the new offer, the new price, the blog article. Whoever forgets leaves the Italian version with last summer’s offer. The content calendar marks the three versions. The blog can have different articles per language, by market.
The mistakes
The automatic translation button. A single English “for foreigners” page. No hreflang. Addresses with parameters. Word-for-word translations with Albanian keywords. An Albanian menu on the Italian page. An Italian form with an Albanian reply. The Italian version left unupdated. Adding a language because “it costs little”: if it costs little, it is machine-translated.
Example: a real estate agency in Vlorë
Before: an Albanian site with a Google Translate button, zero enquiries from Italian Google. The work: 30 Italian pages written for Italians (areas, how to buy, costs, the agency), 30 English, hreflang, forms with language, an agent replying in Italian, Italian reviews. After six months: page one on Italian Google for area searches, 40 enquiries a month from Italy, half of foreign clients from the site.
Frequently asked questions
Is the Google Translate button enough?
No: Google does not rank it and clients lose trust. It is worse than no language.
Do I have to translate everything?
Service and area pages yes, written; the blog can vary by market.
What does an added language cost?
A good part of the base site: it is new text, not a button.
Who should reply to Italian forms?
Someone who speaks Italian, within 24 hours. Otherwise the site brings clients who leave.