
Bilingual websites: setting up Greek and English SEO correctly
In Cyprus, your customers search in Greek, in English, and often in a mix of both. A bilingual website can win both audiences, but only if it is set up so search engines understand which page is which. Get it wrong and the two languages compete with each other, or one of them never ranks at all.
Why bilingual SEO is different
A second language is not just a translation layer on top of your site. For search engines, each language version is a separate set of pages that needs to be found, understood and shown to the right people. That means three things have to be right: the structure of your URLs, the signals that connect translations, and the content itself.
Step 1: Give each language its own URLs
Each language version of a page needs its own address. The common options are:
| Structure | Example | Notes |
|---|---|---|
| Subfolders | example.com.cy/en/ and example.com.cy/el/ | Simplest to manage, and authority is shared across languages. Usually the best choice. |
| Subdomains | en.example.com.cy and el.example.com.cy | Workable, but treated more like separate sites. |
| Separate domains | example.com and example.com.cy | Most work and cost. Only worth it for very different markets. |
| Language switched by cookie or script, same URL | example.com.cy for both | Avoid. Search engines may only ever see one language. |
For most Cyprus businesses, subfolders are the right answer. Decide which language sits at the root, or put both in folders, and keep it consistent.
Step 2: Connect translations with hreflang
Hreflang tags tell search engines that two pages are translations of each other, and which language each is in. Without them, Google has to guess, and it may show the English page to Greek searchers or treat the two as near-duplicates.
Each page should list itself and its translation, for example a tag for el pointing to the Greek page and one for en pointing to the English page, plus an x-default for visitors whose language does not match either. The tags must be reciprocal: if the Greek page points to the English one, the English page must point back.
Good multilingual plugins for WordPress, such as WPML or Weglot, handle this automatically, but check the page source after setup to make sure the tags are there and correct.
Step 3: Translate properly, and localise keywords
Machine translation has improved, but unedited it still produces phrasing that native speakers notice immediately, and that does not match how people actually search.
- Research keywords in each language separately. The Greek term people type is not always the literal translation of the English one. Sometimes Cypriots search in English even for local services, or use Greeklish.
- Translate meaning, not words. Headlines and calls to action especially need a native writer.
- Localise details: currency formats, phone number formats, place names in both Greek and Latin spelling.
- Translate everything on the page: titles, meta descriptions, image alt text, buttons and form labels, not just body text.
Step 4: Match the pages
Ideally every important page exists in both languages, so the language switcher takes visitors to the equivalent page rather than dumping them on the home page. If some content only exists in one language, that is fine; just do not link it as a translation.
Step 5: Handle Greeklish and mixed searches
Many people in Cyprus type Greek words with Latin letters, or mix languages in one search. You cannot create a page for every spelling, but you can:
- Mention common alternative spellings of your business and place names naturally.
- Make sure your Google Business Profile, address and brand name are consistent in both scripts.
- Use the language your customers actually use in reviews and FAQs.
Common mistakes
- One URL for both languages, switched by a cookie. Search engines usually see only the default.
- Missing or one-way hreflang tags.
- Automatic redirects based on browser language or location. They can stop search engines and travellers reaching the version they want. Suggest a language instead of forcing it.
- Half-translated pages, with English menus on Greek pages or vice versa.
- Translating keywords literally without checking what people search.
- Duplicate titles across both languages.
- Forgetting the sitemap: include both language versions.
Checklist
| Item | Check |
|---|---|
| Each language has its own URLs | Visit both and compare the address |
| hreflang tags present and reciprocal | View page source on both versions |
| Language switcher goes to the equivalent page | Click it on a deep page |
| Titles and descriptions translated | Check in Search Console or a crawler |
| Both versions in the sitemap | Open the XML sitemap |
| No forced redirects by language | Test from a browser set to the other language |
Is a second language worth it?
If your customers include both Greek speakers and English speakers, such as tourists, expats, international companies or overseas property buyers, usually yes. The cost is mainly translation and a little extra maintenance. The benefit is ranking for searches your competitors may be ignoring. If your audience is entirely one language, a polished single-language site beats a weak bilingual one.
Questions people ask
Which language should be the default?
The language most of your customers use. For a business serving mainly local customers, that is often Greek. For tourism, shipping, finance or property aimed at international buyers, it is often English. Either way, both versions should be equally complete and easy to reach.
Will two languages split my SEO strength?
Not if the structure is right. With subfolders on one domain, links and authority build up for the whole site, and hreflang tells search engines the pages are translations rather than competitors. Problems only appear when translations are duplicated without hreflang or hidden behind scripts.
Do I need different keywords in each language?
Yes. Research each language on its own. The phrase people type in Greek is often not the literal translation of the English term, and some services in Cyprus are searched mostly in English even by Greek speakers. Let the data decide, not the dictionary.
Can I add Russian, Hebrew or other languages later?
Yes, if the structure supports it from the start. Subfolders and hreflang scale to more languages easily. Only add a language when you can maintain it properly; a half-translated version does more harm than good.
Should my Google Business Profile be bilingual too?
Your profile has one main description, but you can reply to reviews in the language they were written in, and posts and services can mention both. Keep your business name and address consistent across both scripts.
How we can help
We build bilingual sites with the correct structure from the start through our website design service, and audit and fix existing ones as part of SEO: URL structure, hreflang, translated metadata and keyword research in both languages. For more common pitfalls, see 12 SEO mistakes small businesses in Cyprus make.