Skip to content
LingravelixMultilingual websites, planned properly

Services

Services for multilingual websites

Lingravelix offers eight services for organisations that need a website in more than one language, from designing a new multilingual site to fixing the hreflang on an existing one. Each has a starting price in Swiss francs on the pricing page, and each is quoted in writing before work begins. Translation is not among them: we build the place where your translators' words go.

Choosing where to start

The right service depends on where your site is today.

Where to start, by situation
Your situationWhere to start
Planning a new site in two or more languagesMultilingual website design
Existing site, readers struggle to find or switch languagesLanguage navigation
Existing multilingual site, search results show the wrong languageHreflang set-up
WordPress site that needs another language, or a plugin that is not workingMultilingual WordPress
Translations are slow, inconsistent or get lost on the wayTranslation workflow
Arabic or Hebrew version neededRight-to-left layout
Dates, prices or forms look wrong in some languagesLocale formats
Selling online in more than one languageMultilingual shops

If none of these fits, or several do, the language structure review on the pricing page is a fixed-scope first step: a written assessment of how your current site handles its languages, with a list of what to change in order of importance.

What all eight have in common

A map before any build

Every project starts by writing down which pages exist in which language, at which addresses, and who maintains each version. That record drives the switcher, the hreflang annotations and the sitemaps, so building it once keeps all three consistent.

Primary sources for technical choices

Where a decision rests on how search engines or browsers behave, we work from the published documentation: Google Search Central for hreflang and site structure 1, the W3C Internationalization pages for language tags and text direction 2, and WCAG 2.2 for accessibility requirements such as declaring the language of each page 3. The guides on this site cite those sources, so you can check the reasoning yourself.

Testing in every language

Templates are reviewed with the longest likely text, not the English draft, and every language is checked on real pages before launch. Approval of the language itself comes from fluent readers you appoint.

No translation, no reselling

We do not translate, we do not resell plugins or translation services, and we take no commission from translators, agencies or software makers. Recommendations about platforms and plugins come with written reasons, so you can weigh them yourself.

What we do not do

  • Translation or certified translation. Your translators, your agency or your bilingual staff provide the words.
  • Legal advice. Where Swiss rules on prices, data protection or e-commerce shape a design, we work from official summaries and flag questions for your adviser.
  • Ranking promises. Hreflang and good structure help search engines match readers to the right version; nobody can promise a position in search results.

Working in English

Lingravelix works in English. Your project documents, quotes and reports are written in English, and the language-specific parts of the site are reviewed by the fluent readers you appoint for each language.

Prices

Each service page gives a starting point, and the pricing page collects them in one table with what each includes. All prices are in Swiss francs, plus VAT where applicable, with the treatment stated on each quote.

Sources

  1. Localized versions of a page (hreflang) Google Search Central, primary source
  2. Which language tag is right for me? W3C Internationalization Activity, primary source
  3. WCAG 2.2 explainer for 3.1.1 (page language) W3C WAI, primary source

Not sure which service fits?

Describe your site and its languages. Our email answer says whether one of the eight services matches.

Ask which fits