Digital & Marketing
Website & Software Localization
A site or app that reads as native to the target market — strings translated with their context, not cold in a spreadsheet.
from €0.12/word · minimum €40
Who this is for
SMEs, startups and e-commerce businesses localising a site or app into or out of Spanish/Catalan-market English, where literal string-by-string translation would break UX, tone or SEO.
- Marketing website copy and landing pages
- App and software UI strings
- Help centre / support documentation
- Checkout and transactional email copy
- Metadata and on-page SEO content
What's included
- Strings translated with surrounding context (screenshot, string key or live page), not in isolation
- Character-length awareness for UI elements that don't wrap (buttons, nav labels)
- Delivery in your export format (CSV, JSON, .po, or plain spreadsheet)
- A basic in-context QA pass once strings are re-imported, where access is provided
- SEO-aware phrasing on metadata and headings, not literal keyword-for-keyword translation
Configure your order
A €40.00 minimum applies to this service
Price shown excludes 21% IVA, added at checkout
PROCESS
- String export
You export your strings (CSV, JSON, .po or a spreadsheet) or share a staging link.
- In-context translation
The translator works with the surrounding screen or page visible, not the string alone.
- QA in situ
Once re-imported, strings are checked in the live layout where access allows, catching truncation or awkward line breaks.
- Re-import guidance
You get the translated file back in your original format, plus notes on any string that needed a different length or structure.
Quality & confidentiality
The most common localization failure isn't a wrong word — it's a technically correct translation that breaks the interface: text that overflows a button, a tone that reads corporate-cold in a market that expects warmth, or a literal string that makes no sense once it's next to an icon. We work with your actual export format and, where you can give us access, your actual screens — not a spreadsheet in isolation.
A real example
FAQ
Questions about this service
What export formats do you accept?
CSV, JSON, .po/.pot, XLIFF, or a plain spreadsheet — tell us your CMS or codebase and we'll confirm the smoothest format for both sides.
Can you work directly in our CMS?
If you can grant a translator-level or preview account, yes — this usually improves quality since strings are seen in their real layout. Tell us your platform when you order.
Do you handle right-to-left or non-Latin scripts?
Our core language pairs are Spanish/Catalan-market English and the other EU languages on our rate card; tell us your target language and we'll confirm coverage before you order.