Localize your Lovable app, automatically
globalize.now adds real i18n to your Lovable app and keeps every language in sync on each push. Add one skill inside Lovable, then translations land as a PR.
The lovable-i18n skill installs Lingui v6, PO catalogs at src/locales/[locale]/messages.po, Trans macros, a language switcher, and a GitHub Action. It detects Vite SPA and TanStack Start stacks. After you connect the repo to globalize.now, every push opens a translation PR with updated catalogs. Committed locale files beat runtime widgets: no after-load translation, no layout shift, and per-locale pages that search engines can index.
50+ languages · RTL included · €5 starting credit · no card required
Prerequisites
- A Lovable project with UI you want to translate
- GitHub account with Lovable project sync enabled
- A Git repository connected from Lovable (use the + menu, then GitHub, then Connect project)
- A globalize.now account to connect the repo for translation sync
How to set up globalize.now with Lovable
Connect your Lovable project to GitHub
In Lovable, open the + menu in the chat input, choose GitHub, then Connect project. Sync your app to a real repository so PO catalogs and Lingui config live in version control.
Add the lovable-i18n skill to your workspace
Open Skills in your Lovable workspace, then Add, then Import from GitHub. Paste the skill URL below and confirm. Adding a skill via Open Skills is free and does not use credits. You only need to do this once per workspace.
https://github.com/globalize-now/globalize-skills/tree/main/skills/lovable-i18nPrompt Lovable to set up i18n
Paste this into the Lovable chat. The skill detects your stack, installs Lingui, scaffolds PO catalogs, wraps strings in Trans macros, and adds a language switcher.
Set up i18n for my project using the lovable-i18n skillReview and merge to your default branch
Lovable syncs the i18n scaffold to GitHub. Review the diff for Lingui config, PO catalogs, and component changes, then merge to your default branch.
Connect the repo to globalize.now
Sign in at globalize.now, connect the repository, authorize the GitHub app, select your Lovable repo and default branch, and pick target languages.
Keep building in Lovable
On every push, globalize.now diffs new strings, translates them, and opens a PR with updated PO catalogs. Merge the PR. No manual extraction between releases.
Common issues
Translations break after every Lovable update
Resolution: Each Lovable prompt can add hardcoded strings. Wire sync into your Git push cycle so PO catalogs stay current. globalize.now catches new literals on push and returns a translation PR before the gap widens.
Should I use Weglot, Lovalingo, or another runtime widget?
Resolution: Runtime widgets translate after the page loads, which causes a flash of English, layout shift, and weaker SEO. The lovable-i18n skill commits PO catalogs and Lingui so translated markup ships from your repo.
Frequently asked questions
What does the lovable-i18n skill install?
Lingui v6 with PO catalogs at src/locales/[locale]/messages.po, Trans macros for string extraction, a language switcher, and a GitHub Action. The skill detects Vite SPA or TanStack Start and scaffolds the stack your Lovable app uses.
Why not Weglot or Lovalingo for a Lovable app?
Runtime auto-translate tools inject JavaScript that translates content after load. That produces a flash of untranslated text, hurts Core Web Vitals, and leaves one English page that gets translated in the browser. Committed PO catalogs and per-locale routing produce stable, indexable pages.
Can I keep building in Lovable after setup?
Yes. Add the skill once per workspace, run the setup prompt, connect the repo to globalize.now, then keep prompting Lovable as normal. Every push triggers a diff, new strings get translated, and a PR lands with updated PO catalogs.
How many languages does globalize.now support for Lovable apps?
50+ languages including RTL locales such as Arabic and Hebrew. Pick targets when you connect the repo. globalize.now fills gaps in your PO catalogs on each push and returns a mergeable PR.
Does this work if I build the same repo in Cursor or Claude Code?
Yes. Run npx skills add globalize-now/globalize-skills in the connected repo for the same skill bundle outside Lovable. The Lovable workspace import uses the lovable-i18n subpath; the open skills CLI installs the full bundle for Cursor and Claude Code.
Will translated Lovable pages show up in Google?
Only if translations exist in the served markup, not injected client-side after load. Lingui with PO catalogs and proper locale routing gives search engines crawlable pages per language. Runtime widgets usually do not.
Get started with Lovable i18n
Create a globalize.now account to connect your repo, or view the skill on GitHub:
https://github.com/globalize-now/globalize-skills/tree/main/skills/lovable-i18n