Your app is built in English with Lovable, Bolt, Cursor or Replit. Now customers in the Netherlands or Germany ask for it in their own language. You paste "translate to Dutch" into the tool, and half the page changes. The rest stays English, dates look wrong, and Google still shows only one version. I checked the facts about Google, MDN, vue-i18n and i18next against their own docs in November 2026.
Short answer: decide which language and which parts first. Give every public page one URL per language, like /nl/pricing. Move all text into translation files with keys, and format dates, numbers and prices with the browser's Intl tools. Then tell Google about each version with hreflang tags and set lang on every page. Do not use a switch that only changes the text in place.
1. Decide first
Before you touch code, answer four questions.
- Which language? One extra language is far easier than three. Pick the language your real customers use.
- Which parts? Public pages (home, pricing, blog), the app screens behind the login, emails, legal pages (privacy, terms) and error messages. Each of these is a separate piece of work.
- Who checks the translations? Machine translation is fine for a first draft. A fluent person should read every text before it goes live, especially buttons, prices and legal text.
- Which URL shape? This one matters for search, so see the next part.
2. One URL per language
Google's guide Managing multi-regional and multilingual sites says: "Google recommends using different URLs for each language version of a page" rather than "cookies or browser settings to adjust the content language on the page."
So a button that swaps the text on the same URL is the wrong shape for public pages. A page with its own address is also much easier to link to and to check. The same page lists subdirectories (example.com/de/), subdomains (de.example.com) and country domains (example.de) as options. For a small app, a subdirectory is the simplest: one domain, one deployment, one set of analytics.
The page also says to avoid automatically redirecting users between language versions, and not to redirect based on what you think the user's language may be. Offer a visible language link instead. Do not force it.
Another warning from the same page: translating only the boilerplate text of your pages while keeping the bulk of your content in one language can create a bad user experience. A Dutch menu around English articles is exactly that.
3. Structure in code
Keep all visible text in translation files. Each text gets a key, and each language has a file with the same keys. The component asks for the key, not the sentence.
- Vue: vue-i18n describes
messagesas "the hierarchical object structure with each locale as the top property", and you call it in a template with$t('message.hello'). - React: react-i18next is "the React binding for i18next". Its examples pass a key to
t, liket('simpleContent').
Do not build sentences from pieces. Code like "You have " + count + " items" cannot be translated well, because word order differs per language. Use one full sentence with a placeholder in the file instead.
Plurals need the library, not an if. In vue-i18n you write the variants in one message with a pipe, like 'car | cars', and the number you pass picks the variant. In i18next plurals are separate keys such as key_one and key_other, chosen with a count option. Its docs warn that without count there is "no fallback to the 'key' value".
Format dates, numbers and money with Intl. Do not write them as text in the translation file. MDN says Intl.NumberFormat "enables language-sensitive number formatting". Its example formats 123456.789 as a euro amount for de-DE and gets "123.456,79 €". The English reader would expect a comma and a dot the other way around. Intl.DateTimeFormat does the same for dates: MDN shows one date as "12/19/2012" for en-US and "19/12/2012" for en-GB. A day and month the wrong way round is a real mistake in a booking or invoice screen. Time zones are the other half of that story: see dates and time zones.
Expect longer text. German and Dutch words are often longer than the English ones, so a label that fits a button in English can overflow it. Test the layout with the longest texts, on a phone, before you call it done. If a layout breaks, let the text wrap. Do not shrink the font.
4. Search per language
hreflang. Google's page Tell Google about localized versions of your page says: "There are three ways to indicate multiple language/locale versions of a page to Google." They are HTML tags, HTTP headers and the sitemap. Pick one and keep it consistent. Three rules from that page matter most:
- "Each language version must list itself as well as all other language versions."
- "If two pages don't both point to each other, the tags will be ignored." So the English page links to the Dutch one, and the Dutch page links back.
- "The reserved x-default value is used when no other language/region matches the user's browser setting." Point it at the version you want unknown visitors to see.
The value is a language code, optionally followed by a region code, separated by a dash, like nl or nl-NL. Per the page, "You can't specify the country code by itself."
The lang attribute. Set it on <html> for every page: en on the English pages and nl on the Dutch ones. MDN's page on the lang attribute says it is recommended "especially due to accessibility concerns", and that the aim is "to allow assistive technologies such as screen readers to invoke the correct pronunciation". A single-page app that sets lang="en" once in index.html will tell a screen reader that the Dutch text is English. This also fits the checks in the European Accessibility Act post.
Own title and description per language. A Dutch page with an English title is a half translation that shows up in the search results. Give each version its own title, meta description and a canonical that points to itself. Put every version in sitemap.xml.
The page must be in the HTML. All of this only works if crawlers receive the real text. Many AI-built apps send an almost empty page and draw the content with JavaScript. If that is your app, fix it first. See Google can't see your Lovable or Bolt app.
5. What goes wrong
- Half-translated pages. Text hardcoded in components never reaches the translation file. Buttons, placeholders, alt texts and page titles are the usual leftovers.
- Emails still in English. Emails are built somewhere else, often in a server function or in a provider's template. The user's language has to be stored with the account so those can pick it. If emails land in spam as well, see SPF, DKIM and DMARC for app emails.
- Error messages in English. Messages from your backend or from a login provider often come back as plain English text. Map the error codes to your own keys.
- Wrong formats. Dates and prices written by hand, or formatted with a fixed locale, show the wrong order or the wrong decimal sign.
- The language is lost. The user picks Dutch, logs in, and the app is English again. Or a refresh resets it. The language should come from the URL for public pages, and from a saved setting on the account after login.
- Legal pages missing. If you sell to EU customers, the privacy policy and terms should exist in the language your customers read. A translated app with an English-only privacy page is a gap. Have it checked by a person who knows the topic. The GDPR checklist for a small app covers what the privacy page needs to say.
- Links that drop the language. A link in the Dutch page that goes to
/pricingsends the visitor back to English. Every internal link needs the language prefix. - Search that only knows English. If your app has a search box, Dutch or German plurals and word forms may not match. See slow or missing search in your AI-built app for language settings in Postgres search.
What I do on my own sites
On my own sites I keep English at / and Dutch under /nl. Foreground (foreground.info) works that way: foreground.info/nl is the Dutch version.
How to ask your AI tool, or a developer
"Make it multilingual" is too vague, and the tool will rewrite things you did not ask about. Name the pages, the URLs and what must stay the same. Two examples:
- "Move every visible text on /, /pricing and /about into translation files with keys, using i18n. Keep the English text exactly as it is. Add Dutch under /nl, keep English at /. Add hreflang tags (with x-default), a lang attribute on the html element, and a separate title and meta description per language. Do not change the layout."
- "Format all dates, numbers and prices with the Intl API, using the current language. Do not build sentences by joining strings. Use the library's plural support. List any text you could not move into the files."
Machine translation can write the first Dutch draft. Have someone fluent read it before you publish. Then check the result yourself, as below.
How to check the result
- View source per language. Right-click, then View page source on
/nl/pricing. Is the Dutch text in the HTML? Islang="nl"on thehtmltag? Are the title and description Dutch? Are thehreflanglinks there, one for each version plus x-default? - Look for leftover English. Open a Dutch page, select all, and scan it. Check buttons, form hints, empty states and error messages, not only the headlines. You can also use
curlandgrepfor a few common English words on the Dutch URL. - Click through as a Dutch user. Sign up, log in, refresh, and reset a password. Does the language stay? Do the emails arrive in Dutch?
- Check a price and a date in each language.
- Try a long word on a phone-sized screen.
Checklist
- You chose the language, the parts to translate, and who checks the text.
- Each public page has its own URL per language, and every internal link keeps the language.
- No visible text is hardcoded in components.
- Plurals, dates, numbers and prices go through the i18n library and
Intl. - Each page has
lang, its own title and description, and a canonical to itself. hreflanglinks go both ways and include x-default.- All versions are in
sitemap.xml, and the text is in the HTML. - Emails, errors and legal pages exist in the new language.
- The language survives login and refresh.
- Layout holds with the longest texts, on a phone.
Going live soon? Also run the launch-ready checklist.
Want this fixed for you?
I finish and fix apps built with Lovable, Bolt, Cursor or Replit, including adding Dutch or German without breaking the app or its search results. I work in Dutch and English. Send me the details and I'll reply within 24 hours.