Bilingual websites, done right
In Greece, a website in two languages isn't a nice extra. It's the minimum. But there's a big difference between a site that has two languages and a site that speaks both.
Translate the meaning, not the words
"Κοντά στη θάλασσα" and "steps from the sea" sell the same thing in two different ways. Word-for-word translation misses that. Each language has its own way of being warm, of being persuasive, of sounding like a real business rather than a brochure.
Good bilingual copy is written for the person reading it. A Greek family from Athens and a British couple from Manchester want slightly different things, and they respond to different words.
Auto-translate plugins show
Automatic translation has improved a lot, but it still produces phrases no person would say. Guests notice those phrases instantly, and it quietly hurts trust in the business, often right at the moment they're deciding whether to book or buy.
Machine translation can be a starting point. It should never be the finished text.
Each language gets its own pages
Technically, every language should have its own real pages with their own addresses, like /el/ and /en/. That way Google can show the Greek page to Greek searches and the English page to everyone else. Sites that switch language with a button but keep one address often only get found in one language.
Each page should also tell Google which version is which, so they don't compete with each other. It's invisible to visitors, but it makes a real difference.
Keep both languages up to date
A common problem: the English page has this year's prices, and the Greek one still shows last year's. Whenever you change something, change it everywhere.
Your Greek matters too
Many sites aimed at foreign visitors treat the Greek version as an afterthought. But Greek searches are often less competitive, and Greek visitors are a big and loyal market. Give them a proper page too.
