Guide
Lovable Multilingual Site in WordPress: How To
A Lovable site with several languages is usually a set of page routes, one per language, plus hreflang tags. That structure converts to WordPress as ordinary pages with the same slugs, and the page language and hreflang come across. What does not come across is a language switcher built from React state, so you rebuild it as a navigation menu or hand it to a translation plugin. This guide shows both routes and tells you which to pick.
How Lovable usually builds multiple languages
Lovable apps are React and TypeScript. There is no built-in translation system, so multilingual sites end up in one of two shapes.
The first shape is routes per language. You get /about and /de/about as separate pages, each with its own text. In a newer TanStack Start app these are files under src/routes, each with its own head() holding the title, description and often hreflang links. In an older React + Vite app they are files in src/pages wired up in src/App.tsx.
The second shape is one set of pages plus a dictionary. A single route reads strings from an object keyed by language, and a button in the header switches the key. Nothing changes in the URL, or the language lives in a query string.
The first shape moves to WordPress almost unchanged. The second shape does not, because the switch is React state. Before you convert, open your project and work out which one you have. It decides everything that follows.
What the converter carries over
Our Lovable to WordPress converter reads the ZIP or the GitHub repository and writes a block theme. For a multilingual site, these parts come across.
Each page route becomes a page with the same slug, so /de/about stays /de/about. The page language is kept, and hreflang tags are kept. Per-page titles and descriptions from a TanStack Start head() are written into Yoast, Rank Math or SEOPress. Redirects in public/_redirects are kept too, which matters if you already redirect visitors by country.
Older React + Vite apps have no per-page meta to read, so titles and descriptions are not carried over. You write them in your SEO plugin after install. The full list is on supported features.
- Language pages — one WordPress page per route, slugs unchanged, including the language prefix.
- Page language and hreflang — carried into the theme so crawlers still see the relationship between versions.
- Per-page meta — title and description from a TanStack Start
head(), written to your SEO plugin. - Redirects — rules from
public/_redirectsare kept. - A dictionary-driven switcher — not converted; custom React state and event handlers do not survive export.
Route A: keep one page per language
If your Lovable site already has a page per language, the simplest WordPress setup is to keep exactly that. No translation plugin, no extra moving parts. You have a German tree and an English tree, and they are plain pages.
The switcher is then a link, not a script. Put it in the header template part in the Site Editor, as a small navigation menu with one item per language. It points at the home page of each tree, or at the matching page if you are willing to keep the links by hand.
This is the right choice for a handful of pages in two or three languages. It gets tedious once you have a blog in every language, because nothing links a translation to its original automatically.
- Convert and install the theme. Appearance → Themes → Add New → Upload Theme → Activate. Pages are created on activation.
- Check the tree. Pages → All Pages. Confirm each language prefix is there and the slugs match the old URLs.
- Set the front page. Settings → Reading → "Your homepage displays" → A static page, and pick your main-language home.
- Build the switcher. Appearance → Editor → Patterns → header template part. Add a navigation block with one link per language.
- Check hreflang. View source on two matching pages. Each should point at the other and at itself.
- Open indexing. Settings → Reading, uncheck "Discourage search engines from indexing this site" when you launch.
Route B: hand the languages to a translation plugin
If you have a dictionary-driven site, or you plan to add many pages, use a WordPress translation plugin instead. Install it after the theme is active, then let it manage the language relationships.
The pattern is the same whatever plugin you choose. You declare the languages, you assign each existing page to a language, and you link translations to each other. The plugin then outputs hreflang itself and renders a switcher block or widget you can drop into the header.
Two things to watch. First, if the plugin generates hreflang, remove the hreflang that came from the theme so you do not ship two sets. Second, decide on the URL format before you import anything: subdirectories like /de/, a subdomain or a separate domain. Changing it later means redirects.
We do not recommend a specific plugin here. Compare the options in the plugin directory at wordpress.org against your page count and budget.
What you rebuild by hand
Some multilingual details are React behaviour, so they stop at the export. Plan for them.
A language switcher that reads a state variable is gone. So is automatic detection from the browser language, which is usually an event handler or an API call. If you want country or language detection, do it at the host or CDN level with a redirect rule, not in the theme.
Text that lives in a dictionary object, rather than in a page, is not page content. The converter writes what a page renders, in the state it renders by default. If your German strings never render in the build, they are not in the theme. Copy them across by hand, or add the German routes in Lovable first and convert after.
Right-to-left languages need one more step beyond translation. We cover that in Lovable RTL website in WordPress.
- Browser language detection — rebuild as a host redirect or a plugin feature, not in the theme.
- Dictionary strings that never render — copy manually, or add real routes in Lovable before converting.
- Currency and date formatting — WordPress formats dates under Settings → General; currency is a WooCommerce setting.
- Translated menus — each language tree needs its own navigation, in the header template part or via the plugin.
Check the result before you switch the domain
Test every language version, not just the main one. A missing translation is easy to miss when you only ever open the home page.
The review screen in the converter shows the converted site next to the original inside WordPress Playground, in the browser. Walk through the language pages there before you download the theme. If a page is wrong, two free AI-fix attempts come with every account, and the fix agent can read the source project and edit the theme.
After install, do a short pass on the live site. Keep "Discourage search engines from indexing this site" checked while you work, and uncheck it on launch day. For the rest of the move, our complete conversion guide has the full sequence.
- Open each language home page and click through the main navigation in that language.
- Compare slugs with the old site, one language at a time. Fix any that drifted, under the page's URL setting.
- View source and read the hreflang block on at least one page per language. Each version should list every other version.
- Confirm the
langattribute on thehtmltag matches the page's language. - Test the switcher from every language, not only from the default one.
FAQ
Does the converter translate my Lovable site into other languages?
No. It converts the content that already exists in your project. If your Lovable site has German pages, you get German pages in WordPress. If it has only English, you add the other languages afterwards in WordPress.
Are hreflang tags kept when I convert a Lovable site to WordPress?
Yes. Page language and hreflang are carried into the generated block theme. If you later install a translation plugin that outputs its own hreflang, remove the theme copies so the page does not ship two sets.
Why is my language switcher missing after conversion?
A switcher built from React state and a click handler is custom JavaScript, and custom state and event handlers are not converted. Rebuild it as a small navigation menu in the header template part, or use the switcher block from a WordPress translation plugin.
Should I use subdirectories or a separate domain for each language?
Subdirectories are the simplest path if your Lovable routes already use them, because the slugs carry over unchanged and no redirects are needed. A separate domain only makes sense when each market is run as its own site. Decide before you import, since changing it later means redirect work.
Will my per-language page titles and descriptions come across?
They do if your app uses TanStack Start routes with a head, which newer Lovable apps do. Those values are written into Yoast, Rank Math or SEOPress. Older React and Vite apps have no per-page meta to read, so you write titles and descriptions in the SEO plugin yourself.