Docs
Brand And Locales
Use brand guidance, human corrections, locale reports, and approvals to release translated experiences deliberately instead of implicitly.
The dashboard is a signed-in workspace. If you are new, create an account first. If you already have access, continue into the app and pick up the same guide there.
Brand guidance
Build a strong brand profile
Brand configuration is where the product learns how your site should sound. It should feel more like a copy brief than a technical settings page.
Inputs that shape quality
Product summary
A concise explanation of what the site offers and what matters most about how it is presented.
Tone
Short, decisive descriptors like calm, precise, premium, direct, or welcoming. A short list is better than a contradictory one.
Audience
Who the site is really speaking to. Audience awareness is often the difference between acceptable translation and convincing translation.
Protected terms
Brand names, product names, legal phrases, and language that should not drift or be casually reinterpreted.
Style directives
Explicit rules such as preserve meaning before flourish, keep claims conservative, or avoid over-localizing product vocabulary.
Evidence snippets
Source examples that demonstrate the voice and framing you want the product to preserve in future translations.
Best practices
Write the profile like an editorial brief
The profile should read like guidance a copywriter could use, not a form with miscellaneous facts.
Protect only what truly matters
Too many protected terms make output rigid. Reserve them for the phrases and entities that carry real brand or legal importance.
Store corrections when they are durable
If a correction improves repeated language or a high-stakes phrase, it should live in the product so future output benefits from it.
Keep memory scoped to the site
Quality decisions should stay anchored to the site that produced them so a correction for one brand does not bleed into another.
How to review the profile
Would a native reader believe this is our brand?
The bar is not mere comprehension. The language should still feel like your company, your positioning, and your customer relationship.
Did we preserve the terms that matter?
Look for brand names, product language, legal phrases, and category-defining wording that should stay stable.
Is the release strong enough for its intended exposure?
A locale that is acceptable for runtime-only user testing may still not be strong enough for crawlable SEO or broad market launch.
Corrections
Use human corrections deliberately
Human corrections are the strongest way to encode durable quality decisions when a phrase or claim matters enough to preserve.
Add corrections when the same phrase is likely to recur, when the product vocabulary is distinctive, or when a claim carries real business, legal, or brand risk. Corrections should feel reusable and auditable, not like temporary notes lost in review.
The product model expects these corrections to help future work inside the same site workspace. They are not meant to become a cross-site shortcut that ignores brand differences.
Release posture
Understand stages and locale states
Translation stages and locale states are separate ideas. Keeping them separate makes rollout much easier to reason about.
Translation stages
Holding
The earliest localized state. Use it as visible continuity and progress, not as the final expression of quality.
Rough
A usable state for human visitors when your policy allows it. Rough is valuable for people, but it is not the same thing as a search release.
Final
The stage meant for durable promotion. In SEO mode, validated final output is the only stage that should become crawlable.
Locale release states
Generated
Work exists for the locale. This means content was produced, not that it is approved or broadly launched.
Approved
An operator has said this locale is ready to launch under the current product policy.
Live for users
Real people may be shown localized content depending on delivery mode, current stage, and locale access policy.
Crawlable
Search engines may index the localized route. This requires stricter conditions than user-facing availability.
Reports
Move from report to approval
Locale reports exist so a launch can be reviewed and discussed. They make the release real enough for sign-off.
- Generate the locale report for one target market.
- Review the artifact as a launch candidate, not as a raw technical output.
- Confirm the brand profile is doing the right work and capture corrections where needed.
- Approve the locale when the intended release is clear.
- Let delivery mode determine whether the locale is merely live for users or also eligible to become crawlable.