We import a translation file you supply — typically a .po/.mo pair or a CSV matched to your translation plugin’s format — into your site’s translation system at scale. The translated text itself needs to come from you or your translator; we handle the correct technical import and verify it displays properly.
Translation import from supplied file
A prepared translation file imported into the correct fields — we don't translate.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- The translation file itself, in a format matching your translation plugin (commonly .po/.mo, or a CSV)
- Confirmation of which language this import applies to
- Confirmation of how to handle any strings the file doesn’t cover, if it’s a partial translation
This or something else?
| You have a finished or substantial translation file ready to import | This fix covers it |
| You need the translation itself done, not just imported — you don’t have translated text prepared yet | Outside this fix’s scope entirely — translation needs to come from you or a translation service, we implement what’s supplied |
| You only have a handful of specific missing strings, not a full file | Missing string translation repair, the smaller-scale version of this same principle |
| Your translation plugin itself is conflicting with another plugin, separate from the import | Translation plugin conflict resolution |
What we do
- Review the supplied file for correct format and completeness
- Confirm which language and which translation system fields it maps to
- Import the file into your site’s translation system
- Verify a representative sample of strings display correctly in context
- Flag any strings the file doesn’t cover, if it’s a partial translation
- Provide a written summary of what was imported
What is included
- Your supplied translation file imported into your site’s translation system
- Verified correct display of a representative sample in context
- Flags for any gaps if the file is a partial translation
- A written summary of the import
Not included
- Translating the content itself — this imports translation you’ve already had prepared
- Repairing individual missing strings one at a time, a separate, smaller-scale fix if that’s actually your situation
- Resolving an underlying translation plugin conflict, a separate, related fix if that’s also an issue
- Ongoing imports as you prepare further translation files
Questions about this fix
Can you translate my site if I send you the content in English?
No — this fix imports a translation file you already have prepared; we don't perform the translation itself, since accurate translation needs to come from you or a qualified translator, not from us guessing at the correct wording.
What file format does the translation need to be in?
Commonly .po/.mo files (the standard WordPress translation format) or a CSV matched to your specific translation plugin's expected structure — we'll confirm the right format for your setup before you prepare the file.
What happens if my file only covers part of the site?
We import what's provided and flag exactly which strings remain uncovered, rather than assuming the file is complete when it isn't.
Will this overwrite translations that are already in place?
We'd confirm your intent upfront — generally we'd expect a supplied file to represent the current, correct version you want live, but worth being explicit about how to handle any existing translations.
How large a translation file can this handle?
This scales well to a large, comprehensive translation file — a bigger file just takes proportionally more careful verification of the import.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.