Multilingual website without plugins: doing it right

A multilingual website is no longer just for large corporations. A manufacturer sells into Germany, a clinic serves patients who speak another language, a training company runs courses in English. The trouble is that adding languages to an existing site often ends in a tangle of plugins, duplicated pages and URLs that neither editors nor Google can make sense of. This guide shows how to plan language versions in terms of structure, SEO and day-to-day editing.

Key takeaways

• Each language version of a page should have its own stable URL rather than switching language with a cookie or a script.
• Hreflang annotations tell Google which pages are equivalents in other languages, and they must point to each other.
• You need to translate slugs, meta tags, image alt text, menus, forms and the cookie banner, not just body copy.
• Machine or AI translation speeds things up, but sales and legal pages should be reviewed by someone fluent in the language.
• Automatically redirecting visitors by IP location hampers indexing and frustrates users.

Decisions to make before you translate anything

Before anyone translates a single sentence, settle three things:

• Languages or markets? A German-language version is not the same as a version for Germany, Austria and Switzerland if prices, availability or contact details differ. Most businesses only need language versions.
• Full or partial translation? Not every page needs to exist in every language. Ten polished pages in English beat fifty careless translations.
• Who maintains each language? Every change to pricing or services has to reach all languages. Without a named owner, versions drift apart fast.

If you sell abroad, see also how we approach websites for manufacturers selling into several markets.

URL structure for a multilingual website

URL structure is the way a page address indicates its language. You have three main options:

For most businesses, subdirectories are the best choice. Avoid parameters such as ?lang=de and cookie-only language switching, because Google then sees one address serving different content.

Translate slugs too. An address like /de/services/ on the German version looks careless and wastes a chance to put a keyword in the URL. It should be /de/leistungen/.

What to translate beyond the page copy

The most common mistake on multilingual websites is translated paragraphs inside an untranslated frame. Check this list:

• the meta title and meta description of every page,
• image alt text and captions,
• menus, footer and breadcrumbs,
• form labels, error messages and submission confirmations,
• the cookie banner and privacy policy,
• call-to-action buttons and downloadable PDFs,
• date, currency and phone number formats.

Hreflang and sitemaps: showing Google your language versions

Hreflang is an attribute in the page code or sitemap that tells search engines "this page has an equivalent in another language at this address". It is what makes a German user see the German version in search results rather than the English one. The rules are simple but easy to break:

• references must be reciprocal: the English version points to the German one and vice versa,
• each version also references itself,
• language codes must be valid, e.g. en, de, pl or en-GB,
• add x-default for a language selector page or default version,
• hreflang URLs must be canonical and return 200, not a redirect.

Each language version of a multilingual website should also have its own sitemap entry. After launch, check in Google Search Console that every language is being indexed.

Translation: human, AI or both

AI-assisted translation is now good enough that "AI translates, a human reviews" is a sensible workflow. An order of work that holds up well:

1. Prepare a short glossary: names of services, products and terms that must not be translated freely.
2. Translate content automatically, either whole pages or individual fields.
3. Send your highest-value pages for review: home page, services, pricing, contact and legal documents.
4. Rework meta tags around the phrases people actually search for in each language, not literal translations.
5. Agree an update rule: a change to the primary language goes into every language on the same day.

Why a multilingual website without plugins is easier to maintain

In systems where multilingual support is added through a plugin, translation is often implemented as separate copies of each page linked together. That works while the structure is simple. During a redesign, however, every copy has to be edited separately, and conflicts between the language plugin, the SEO plugin and the theme can break hreflang or the sitemap after a routine update. Multilingual support built into the CMS stores the value of every field in every language in one place, so you change the layout once.

Launching a multilingual website step by step

1. Pick the pages to translate. Start with the pages that sell: home, services, contact and your best case studies.
2. Define URL structure and slugs for each language before the first translated page is created.
3. Research keywords in each language. A German customer may search for your service using a different word than a literal translation suggests.
4. Translate content and the page frame using the checklist from the previous section.
5. Check technical SEO: hreflang, sitemap, meta tags and canonical URLs in every language.
6. Test the customer journey: submit the form in each language and make sure someone replies in that same language.
7. Monitor indexing in Google Search Console for the first few weeks after launch.

Common multilingual website mistakes

• Redirecting by IP. Googlebot crawls mostly from US addresses and may never see your other language versions. Show a discreet language suggestion instead of forcing a redirect.
• Flags instead of language names. A flag stands for a country, not a language. Write "English", "Deutsch", "Polski".
• Mixed languages on one page. An English heading above a German form undermines trust and confuses language detection.
• No equivalent page. The language switcher sends users to the home page instead of the same page in the other language.

Frequently asked questions

How do I build a multilingual website without plugins?

You build a multilingual website without plugins by using a CMS with native language support, one that stores field content per language and gives each version its own URL. You then need no translation add-ons, and the system itself handles sitemaps and meta tags.

Does a multilingual website need separate domains?

No, a multilingual website does not need separate domains, and subdirectories such as /en/ and /de/ work best in most cases. Country domains make sense when you run a distinct operation in that market and want a strong local signal.

Is AI translation good enough for a business website?

AI translation is good enough as a starting point, but key sales pages and legal documents should be reviewed by a fluent human. Automated translation handles grammar well but struggles more with industry terminology and brand voice.

Does Google treat language versions as duplicate content?

No, translated versions of a page are not treated as duplicate content as long as each has its own URL and correctly annotated hreflang equivalents. Problems arise only when identical, untranslated text sits at several different addresses.

How many languages should a business website have?

A business website should have as many languages as you can keep up to date and support in customer communication. An outdated language version, or a form nobody answers in that language, does more harm than having no version at all.

Multilingual websites in LessCMS

In LessCMS, multilingual support is built in, with no add-ons:

• Every field holds a value per language, and each language version gets its own URL and its own sitemap entry. You enable languages per project and add a language switcher widget in the editor.
• Meta titles and descriptions are set per page, entry and language, optionally with AI help.
• AI translation covers a whole page, a single field or an entire collection, into several languages at once. You see the token cost before confirming, and nothing publishes itself, so there is time for review.

Ready to launch a second language without plugins? See LessCMS plans and sign up without a card.