Documentation
Translation.
Generate pages in any language, or translate existing pages while preserving layout and styling.
How It Works
Schema-preserving translation.
Translation in Gallop isn't a full re-generation. The Copy Agent translates text content while the Layout and Style agents preserve structure and visual design exactly.
Modes
Two ways to translate.
Generate in language
Include the target language in your original prompt. The Copy Agent writes natively in that language from the start — no translation step needed. Produces the most natural‑sounding content.
"Build a landing page for a
bakery in Paris. Write all
content in French."Translate existing
After generating a page in any language, use Rider AI or the API to produce a translated copy. Layout and styling are preserved exactly. You get a separate WordPress page per language.
// Via Rider AI:
"Translate this page to German.
Keep the layout the same."
// Via API:
POST /v1/translate
{ "pageId": "...",
"target": "de" }Languages
40+ languages supported.
Gallop supports all major world languages. Quality is highest for widely-spoken languages with extensive training data.
Tier 1 — Full support
English, Spanish, French, German, Portuguese, Italian, Dutch, Polish, Swedish, Norwegian, Danish, Finnish. Highest quality with nuanced tone control.
Tier 2 — Strong support
Japanese, Korean, Chinese (Simplified & Traditional), Russian, Ukrainian, Turkish, Arabic, Hindi, Thai, Vietnamese, Indonesian, Malay.
Tier 3 — Standard support
Czech, Romanian, Hungarian, Greek, Hebrew, Bengali, Tamil, Tagalog, Swahili, and 20+ more. Content is accurate but tone nuance may be limited.
RTL languages
Arabic, Hebrew, Urdu, and Persian are fully supported. Stride CSS includes automatic RTL layout handling — text alignment, flex direction, and margin direction are reversed.
Accuracy
Schema-constrained output.
Translation hallucination — where a model adds, removes, or restructures content during translation — is Gallop's main concern. The schema validation system prevents this entirely.
- Element count match: The translated page must have the same number of elements as the source.
- Type preservation: A heading stays a heading. A button stays a button. Element types cannot change.
- Class immutability: Stride CSS classes are never modified during translation. Styling stays identical.
- Nesting integrity: The parent-child hierarchy must match exactly. No structural drift.
- Text-only changes: Only string content inside
props.contentfields is modified.
// Source (English)
{
"type": "heading",
"props": {
"level": 2,
"content": "Our Services"
},
"classes": ["heading-lg"]
}
// Translated (Spanish)
{
"type": "heading",
"props": {
"level": 2,
"content": "Nuestros Servicios"
},
"classes": ["heading-lg"]
}
// ✓ Same type, level, classes
// ✓ Only content changedEarly Access
Go global.
Get early access when we ship.