You're set up! here's how to verify it worked

The setup is done. Here's what success looks like and how to confirm everything is working before you call it done.

What your repo should look like now

After Convert my app completes, your repo should contain:

New files added:

/messages          (or /locales — depends on your i18n library)
  en.json          ← your source strings, all extracted
  es.json          ← placeholder file, empty until translated
  de.json
  fr.json

Modified files:

• Your component files — hardcoded strings replaced with t("checkout.submit") calls

• Root layout or app entry point — i18n provider wrapped

• i18n library config file — new, auto-generated

If you don't see locale files in your repo, the conversion step didn't complete. See the setup stalled troubleshooting article and re-run.

Check that the conversion looks right

Open a few component files and confirm the strings were extracted. Look for:

• t("some.key") calls replacing what used to be inline text

• Consistent key naming (e.g. checkout.submit_button, not a mix of styles)

• The en.json file contains real readable strings, not garbled output

If you see hardcoded strings still in the file, the agent missed them. Run Convert my app again — it will pick up what was missed without duplicating work.

Test the language switcher locally

1. Run your dev server: npm run dev (or your usual command)

2. Open the app in your browser

3. Switch languages using the switcher

4. Confirm UI text changes — it won't be translated yet (just the keys), but switching shouldn't break the app

If the switcher isn't visible, ask your agent: Add a simple language switcher to my app

If switching languages crashes the app, chat with us at globalize.now — it usually means the i18n provider wasn't wrapped correctly during setup.

Trigger your first translation push

git add .
git commit -m "test: trigger first globalize.now translation"
git push

Within 2–5 minutes you should see a new pull request from globalize.now with translated locale files. Open the PR and check that the locale files contain actual translated text and the languages you selected are all present.

If no PR appears after 10 minutes, check your globalize.now dashboard for the job status.

Merge and you're done

Review the translation PR, merge it, and your app is now serving real translated content. From this point on, every push you make automatically triggers the translation pipeline. No further manual steps.