Five languages in-house · based in the EU
Multilingual website design, written natively for each market
For US companies entering Europe and for businesses that sell in more than one language. Built by a two-person studio in Gliwice, Poland, whose own site runs in five languages.
Each extra language costs $690 on top of the $2,900 website, so English plus one language is $3,590. Every version gets native copy, its own URLs, reciprocal hreflang and localized titles and formats. The launch date for all languages is fixed in your written scope before you pay the deposit.
Website translation vs localization
Translation changes the words. Localization changes what a buyer in that market needs to see: the search terms they use, prices and formats, legal pages, trust signals and the call to action. We do the second, and we never publish raw machine translation.
Machine translation can help with a first draft. Every page is then rewritten for its market and checked by a native reader before it goes live. A German buyer searches with different words than a literal translation of your English headline would use.
Numbers, currencies, dates, addresses and phone formats change per version too: 1.234,50 € in Germany, 1 234,50 zł in Poland, $1,234.50 in the US. Getting these right is a small detail that tells a reader the page was made for them.
Entering Europe from the US: Germany and Poland
FastLanding is a two-person studio in Gliwice, Poland (EU). We have no US office and work with US clients remotely. Justyna takes calls in German and Polish as well as English, which makes Germany and Poland the two markets where we can help beyond the website itself.
Germany: one German version (hreflang "de") usually serves Germany, Austria and Switzerland, rather than three near-identical country copies. German business websites generally need an Impressum (legal notice), and German buyers tend to read the details: specifications, terms, delivery and contact. We build the pages; your lawyer confirms the legal wording.
Poland: we write Polish natively, so the Polish version reads as if it was made in Poland, because it was.
GDPR-ready forms and consent: every form asks only for what you need, says who receives the data and links a privacy notice in the page language. Analytics and marketing tags load only after consent, and rejecting is as easy as accepting. We are not lawyers: your privacy policy and data processing agreements still need legal review.
Real multilingual sites we built
| Website | Languages | What the language versions do |
|---|---|---|
| hello-home.es | PL · EN · ES | A licensed real estate agency on the Costa Blanca serving Polish buyers: listings, a buying guide and mortgage help. |
| casaflamingo07.com | PL · EN · DE · ES | A holiday villa with a private pool in Ciudad Quesada: gallery, local attractions and date availability. |
| fastlanding.io | PL · EN · DE · ZH · AR | Our own site, each language written for its market, including right-to-left Arabic. |
We do not publish traffic or revenue figures for these projects. The sites are live, so you can check the language switchers, URLs and hreflang yourself.
hreflang setup, done the way Google documents it
hreflang tells search engines which language version to show to whom. Google's localized versions guide (updated September 21, 2026) says each version must list itself and every other version, with x-default for everyone else.
Google's guidance on multi-regional sites advises against redirecting visitors by guessed language, which is why we use a switcher.
- Separate URLs per language, such as /de/ and /pl/, never one URL that swaps text with cookies or scripts
- Reciprocal hreflang on every page: each version lists itself and all others, plus x-default
- No automatic redirects by IP address or browser language; a visible language switcher instead
- Titles, descriptions, URL slugs and structured data written in each language, not left in English
- One version per real market need, not near-duplicate copies per country
- After launch, a check of every language version in Search Console and Bing Webmaster Tools
Arabic and right-to-left, done right
Right-to-left is more than flipping the layout. Done badly, Arabic readers see mirrored logos, broken punctuation and prices that read in the wrong order.
Our own Arabic pages follow the same rules: the arrows flip and every price stays one isolated run.
- dir="rtl" and lang="ar" on the page, with layout built on logical CSS properties so spacing mirrors correctly
- Arrows and direction icons mirrored; logos, media controls and charts left as they are
- Numbers, prices, brand names and URLs isolated so mixed Arabic and Latin text keeps the right order
- An Arabic typeface with proper letter joining and generous line height, not a Latin font fallback
- Western digits by default for prices and phone numbers, or Arabic-Indic digits if your market prefers them
- Copy in Modern Standard Arabic, which reads correctly across the Gulf and the Levant; Justyna takes calls in Levantine Arabic or English
Pricing
In USD. The written scope lists every language, page and the launch date before you pay.
-
Focused website sprint
$2,900 one-time, USD · 50% to start, 50% after deployment
Included
- Custom design, hand-coded
- One language; pages and scope confirmed in writing
- Technical SEO, sitemap and structured data
- Launch date fixed in the written scope
-
Each extra language
$690 per language, one-time, USD
Included
- Copy written for that market, never raw machine translation
- Separate URLs, reciprocal hreflang and x-default
- Localized titles, descriptions, structured data and formats
- Right-to-left layout included for Arabic
-
Ongoing care
from $249 per month, USD, optional
Included
- Support after launch for every language version
- Technical upkeep and small content changes
- Exact scope stated in the written proposal
- No recurring plan is added without your approval
Example: English plus German and Polish is $2,900 + $690 + $690 = $4,280. Payment is 50% to start and 50% after deployment.
How a multilingual build runs
-
Markets first
We agree which markets you sell to, which languages they need and whether any country needs its own version. Most do not.
-
Structure and URLs
We plan the page tree, the URL slugs per language and the hreflang map before any copy is written.
-
Primary language
We build and approve the main version, usually English, so the structure is settled before other languages start.
-
Native copy per market
Each language is written for its market and checked by a native reader. If you have a local team, they approve it too.
-
Launch and checks
All versions go live with hreflang, sitemaps and localized metadata. We then check them in Search Console and Bing Webmaster Tools.
Multilingual website questions
How much does a multilingual website cost?
What is the difference between website translation and localization?
Do you use machine translation?
What is hreflang, and do I need it?
Which languages do you work in?
Will my site be GDPR compliant?
Where are you based?
Plan your languages with Justyna
Tell us which markets you are entering. Justyna talks it through in English, German, Polish, Chinese or Arabic, and you get a written scope and price.