The PR from globalize.now is the first time you see real output. If something looks off, here’s how to diagnose and fix it.
Need help? Chat with us at globalize.now — hit the chat icon on any page.
The translations are empty or contain key names instead of text
If your locale files contain "" or still show key names like "checkout.submit": "checkout.submit" instead of translated text, the translation job didn’t run or failed silently.
What to check:
-
Go to your globalize.now dashboard and look at the job that triggered this PR
-
If it shows an error, see the troubleshooting guide for unexpected translation jobs
-
If no job ran at all, confirm auto-translate is enabled in your project settings
The translations sound wrong or unnatural
AI translation quality varies by language pair and domain.
-
Wrong tone (too formal, too casual, wrong register): We can adjust the translation style for your project’s language pair. Chat with us at globalize.now with examples.
-
Idioms translated literally: Known limitation for some language pairs. Chat with us with specific examples.
-
Brand terms or product names translated incorrectly: You need a glossary of protected terms. Chat with us at globalize.now to add one.
The PR is missing strings from my app
If some strings are translated but others are still hardcoded, the conversion step missed them during setup.
Common reasons: Strings inside config objects (form labels, error messages, toast notifications); strings in files changed after setup ran; strings in deeply nested component patterns.
Fix: In your coding agent, run:
Convert my app
The agent re-scans for any strings it missed and adds them to your locale files without duplicating existing keys. Then push again to trigger a new translation job.
Wrong strings are being translated
If URL slugs, database field names, or internal identifiers are showing up as translated strings, the agent extracted the wrong content.
Open your en.json file and remove the keys that shouldn’t be there. Then tell your agent:
Do not translate strings in [path/to/file.ts]
The PR changes files I didn’t expect
Check what was changed — it’s usually locale files the agent placed in a non-standard location during setup. Review the diff, merge what’s correct, and move any files to the right location.
If something looks completely wrong, close the PR without merging. Your main branch is untouched. Chat with us at globalize.now with the PR link and we’ll review what happened.