What is the best way to translate a website into multiple languages?

Option A — Google Sheets Extension (fastest for marketing & CMS content)

Best for: pages, blog posts, product copy exported to CSV/Sheets.
Here is how to install and how to use Lara Translate Extension. 

1. Open a blank Google Sheets 
2. Install Extension following the "how to install" guide.

3. Prepare your sheet: Column A = source text (EN), optional ID/slug column.

   • Set languages according to the "how to use" guide.

4. Insert source content: Select cells.

5. Use the formula within the Extension.

6. Export back to CMS: Download CSV/TSV or use your CMS importer.

Why choose this: zero dev work, quick iterations, easy QA in one place.

Option B — Document Translation for web files (.json, .po, .html, etc.)

Best for: UI strings & static sites stored as files.
Here are the supported formats for document translation.

1. Collect source files: messages.json, .po, .yml, .resx, .html, etc.

2. In Lara web app, Translate document → upload files (one file at the time).

3. Set language source and target languages, pick Style, attach Glossary, enable Translation Memory.

4. Translate and download localized files.

5. Upload the files in your website's repository.

Why choose this: preserves structure/placeholders, fits Git workflows.

Option C — API automation (scales with your product)

Best for: dynamic apps, CI/CD, or large multilingual catalogs.
Here you can find all API documentation.

1. Get API credentials from Lara Translate.

2. Check documentation (es-ES, fr-FR…) in your app.

3. Send strings/documents to Lara via API; include glossary IDs and style in payload.

4. Pull translations on build/deploy; store in your i18n system.

5. Upload the files in your website repository (if applicable).

Why choose this: fully automated, consistent, and repeatable across updates.

When to use which?

• Sheets → marketers/PMs localizing CMS content fast.

• Docs (.json/.html) → engineering or content ops with file-based sources.

• API → product teams needing continuous localization in CI/CD.

This article is about:

• How to translate a website into multiple languages using Lara (Sheets add-on, file-based, or API).

• Choosing the right workflow for your team: Google Sheets, .json/.html document translation, or API automation.

• Ensuring quality with Styles, Glossaries, and Translation Memory (if applicable) for consistent, brand-safe localization.