Multilingual SEO: how to organise a Greek and English website

Sources checked: 13 September 2026. Technical references use official Google Search Central documentation. The business example below is hypothetical.

1. Define who the second language needs to serve

A hotel in Greece, a company looking for international partners and an online shop offering overseas delivery have different requirements. Before translating the first page, establish who will read it, what they need to learn and which action they can actually complete.

An English version does not automatically create a presence in every country. It may serve English speakers in Greece or partners across several markets. Language and geographic targeting are separate decisions, as explained in Google’s guide to multilingual and multi-regional websites.

Write a concrete objective: “The English version helps trade partners understand our products and enquire about working with us.” That is a more useful requirement than adding an EN option to the menu. Firstidea’s multilingual website and eCommerce service explains how architecture, content and functionality fit together in this type of project.

2. Build a map of equivalent pages

Before choosing a plugin, create a table containing the Greek page, its English counterpart, its purpose and its review status. Assign an owner for future updates. This separates a completed translation from a page that has merely been created in the CMS.

For a hypothetical furniture business, an initial map might look like this:

Visitor need	Greek URL	English URL	What to check
Find dining tables	/epipla/trapezia/	/en/furniture/dining-tables/	Equivalent category and accurate description
Compare a product	/proion/trapezi-alfa/	/en/product/alfa-dining-table/	Same product, dimensions and options
Understand delivery	/paradoseis/	/en/delivery/	Actual delivery areas and conditions
Enquire about a trade account	/synergasies/	/en/trade-enquiries/	Appropriate form and recipient

These paths are illustrative. The important part is the relationship: an English product page must describe the same product, rather than simply resemble the Greek page visually.

3. Use a stable, understandable URL structure

For a small team managing one brand, an /en/ directory is often a practical maintenance choice. Separate domains or subdomains may suit different operational requirements. Consider the existing site, intended markets and management costs before choosing.

Each language version needs a distinct URL. Google recommends this approach over changing the content of one address solely through cookies or browser settings. Guidance on language versions.

If the current URLs work, avoid changing them just to make the two structures look symmetrical. Assess the consequences first. When restructuring is necessary, follow the process in our website redesign and SEO migration guide.

4. Canonical URLs and hreflang answer different questions

A canonical identifies the preferred address among duplicate or very similar URLs. It is a signal to Google, rather than an instruction that determines Google’s choice. Fully translated pages are not duplicates simply because they communicate the same meaning in different languages. Understanding canonicalization.

For the straightforward Greek and English pair in our example, each version should identify its own final URL as canonical. Avoid assigning Greek canonical destinations to every English page. The aim is a consistent preferred address within each language. Guidance on specifying a canonical URL.

Hreflang connects language or regional variants. A simple Greek and English pair uses el and en. Each version includes itself and its counterpart, using full URLs and reciprocal references. Hreflang documentation.

5. Give technical signals a consistent management process

Hreflang can be implemented through HTML, HTTP headers or an XML sitemap. Google treats these methods as equivalent; implementing all three provides no additional search benefit. Methods for declaring language variants.

Agree which tools manage canonical URLs, translations and the sitemap. Keep one verified page pair as a reference, then repeat the check across different page types. Testing the homepage does not establish whether products, categories and articles work correctly.

For WordPress, inspect the final output produced by the theme, SEO plugin and translation tool together. A completed setting in the administration screen does not prove that the public HTML or sitemap contains the intended value.

6. Translate the intent and the entire journey

A Greek phrase describing “professional furniture” could refer to office equipment, hospitality furniture or a wholesale relationship. The English page needs to establish which of these needs it serves. Literal translation will not resolve an ambiguity already present in the source text.

Check the title, H1, description, main copy, captions, buttons, form fields and success or error messages. Read the page as someone who has never seen the Greek version. Can you understand what is offered, who it serves and what to do next?

A useful editorial brief records the audience’s question, the page’s answer, the supporting evidence and the next action. An English version may need different examples or additional context for a Greek service, while keeping the underlying business facts consistent.

7. Build a useful topic cluster in each language

An English service page needs relevant English guides and a clear route to an enquiry. If every detailed answer remains in Greek, visitors have to leave their chosen language just when they need more information.

For example, the journey “dining table category → size selection guide → suitable product → delivery information” can be organised within each version. Actual customer questions determine which content is needed and where each link belongs.

Use ordinary links with descriptive anchor text and relevant surrounding copy, following Google’s internal linking guidance. Every page does not need to link to every other page. For the specific requirements of catalogues, filters and products, see our technical SEO guide for eCommerce websites.

8. Test the language switcher as a visitor would

Open an internal page through a direct link and change language. Are you still viewing the same product or subject? Can you switch back? If every change takes you to the homepage, language selection interrupts the task.

When a translation is unavailable, design an explicit response: hide that unavailable language option for the particular page, or offer a clearly explained alternative route. Avoid presenting an unrelated page as a translation.

Avoid forcing a language change based on IP location. Google notes that content adapted to a request’s location or language preferences may not be crawled completely. How Google crawls locale-adaptive pages. Also test while signed out, in a clean session and on mobile, so your saved preferences do not conceal problems.

9. In eCommerce, the second language continues beyond the product page

The test ends when customers understand what they purchased and what happens next. Include the basket, checkout, delivery options, account area and order email. Check the same product selection in both languages, especially where sizes, colours or other variants are involved.

Keep language, currency and shipping destination as separate decisions. An English product description does not mean the product ships everywhere. Unclear delivery wording can create a false expectation even when the technical SEO settings are correct.

As a real example of distinct commerce journeys, Firstidea’s Lydia Creations project is a bilingual WooCommerce store serving B2C and B2B customers. Its relevance here is the breadth of the experience that needs to be organised, rather than any promise about rankings.

10. How does this organisation support GEO and AI search?

For Google’s AI features, foundational SEO practices remain relevant. The official guidance emphasises useful, original content and an accessible technical foundation. Google’s guide to generative AI search.

For bilingual editing, maintain a shared record of business facts: the company name, service scope, product specifications, service areas and approved sources. This helps the Greek and English versions avoid contradictory answers. It is a content consistency practice, rather than a proven mechanism for securing AI citations.

Broader AI access and the differences between crawlers are covered in Firstidea’s AI SEO and GEO guide. Having two languages does not guarantee that an AI service will reference the site.

11. Give the team a concrete launch checklist

Review both the information on the page and the action a visitor should complete. For every important page pair, record whether:

• The mapping covers the same subject, product or service.
• Both URLs open in the expected language without unwanted redirection.
• Pages intended for search have no forgotten noindex setting or access barrier.
• Canonical URLs, language variants and sitemap entries match the approved map.
• Internal links lead to the correct final addresses and appropriate language content.
• The language switcher, form or checkout completes the intended journey.
• Actual text fits and remains readable on mobile.
• An owner is responsible for reviewing the translation after the next change.

This is a practical project acceptance checklist. Passing technical checks establishes that the implementation behaves as designed; organic performance is assessed afterwards.

12. Measure each language version against its own objective

Record the launch date and monitor Greek and English landing pages separately. Combine search data, available analytics and the quality of enquiries received by the team. The English version may attract fewer visits while serving valuable trade contacts.

In the hypothetical furniture store, a useful question is whether visitors to the English trade page submit suitable enquiries. If they read the page but struggle with the form, the next action is to investigate the journey and its wording. Publishing more translated articles will not necessarily address that problem.

Also decide who is notified when a service, product or delivery policy changes. Multilingual content remains useful when the second version keeps pace with the business itself.

Frequently asked questions about multilingual SEO

Is an automatic translation button enough?

Check what it produces: separate accessible pages, complete text and functioning actions, or just a temporary change on screen? The requirement is a complete version that can be checked and maintained.

Is an English translation duplicate content?

A fully translated page is not a duplicate simply because it says the same thing in another language. Translating only the menu while leaving the main content unchanged is a different situation. Google: canonicalization.

Do we need to translate the entire blog?

Start with the pages and answers your chosen audience needs. A small, coherent set with a complete enquiry journey is a manageable starting point.

Which canonical should an English page use?

In an ordinary translated pair, the English page identifies its own final URL. Substantially identical content in the same language needs a separate consolidation decision. Google: specifying canonical URLs.

Is sitemap-only hreflang incorrect?

No. XML sitemaps are one supported method. Check that the implementation is complete and correctly maps the versions. Google: language variants.

Should EN always lead to the English homepage?

For an internal page with an available translation, use the equivalent page so the visitor can continue the same task.

Can we use AI to help translate the content?

Use it as a drafting aid, with terminology, factual and language checks before publication. Google notes that generating many pages without added value may breach its scaled content abuse policy. Guidance on generative AI content.

Can we add English without rebuilding the whole website?

Often, yes, after reviewing the existing platform, URLs, templates and management workflow. The required scope depends on the specific obstacles found.

Does a second language automatically increase sales or AI references?

No. It needs a relevant audience, useful information, a credible offer and a working visitor journey. Distinguish visits, enquiries, sales and AI references when measuring results.

What should we prepare for an initial review?

Your website URL, intended languages and markets, five important pages and the action visitors should complete. Include who approves and maintains each language version.

Plan the second language around a complete experience

If your English version exists but its pages do not connect properly, start by reviewing a few important pairs. Explore Firstidea’s SEO service for the relationship between technical foundations and content, or send us your site, intended languages and markets so the project scope and priorities can be defined.