Skip to main content

​
Why Translate with Gradial

​
Work Where Your Authors Already Work

Traditional translation workflows pull content out of your CMS, run it through separate systems, and require manual re-integration. This creates delays, version control issues, and context loss. With Gradial, translation happens inside AEM. Authors and localization teams work in the same environment they use for everything else. No exports, no file handoffs, no waiting for round-trips.

​
Get 80% of Your Content Done Without Leaving Your Workflow

Most translation needs don’t require specialized linguists or complex review cycles. Product descriptions, landing pages, blog posts, metadata—this content can be translated directly by the agent while your team stays focused on higher-value work. Reserve your external translation resources and human review for the 20% that truly needs it: regulated content, legal documents, and high-stakes campaigns. Let Gradial handle the rest.

​
Agent-Based Translation Benefits

Because Gradial uses an agent-based approach, translation isn’t just mechanical word conversion:
  • Rules are applied automatically — Your brand glossaries, terminology standards, and style guidelines are enforced during translation, not checked afterward
  • Context is preserved — The agent understands the page structure, component types, and content relationships in AEM
  • Iteration is instant — Need to adjust the translation? Update your task and run it again, just like any other content change

​
How to Translate Content

​
Creating a Translation Task

  1. Create a new task in your workspace
  2. Reference the source page URL you want to translate
  3. Specify the target language in your request (e.g., “Translate this page to Spanish” or “Create the French version of this page”)
  4. Run the task
Gradial translates the content and applies any relevant rules, including brand glossaries you’ve configured.

​
Specifying Regional Variants

For languages with regional differences, specify the variant in your request:
  • “Translate to Canadian French” (not France French)
  • “Translate to Swiss German” (not Germany German)
  • “Translate to Mexican Spanish” (not Spain Spanish)
  • “Translate to Brazilian Portuguese” (not Portugal Portuguese)
Gradial adapts vocabulary, spelling, and expressions for the specified region.

​
Translation Modes

​
Direct Translation (Default)

By default, Gradial performs direct translation—converting your content to the target language while preserving the original meaning, tone, and structure. This is appropriate for most content where you want the translated version to match the source.

​
Content Strategy Rewrite

If you need content adapted for a different market rather than directly translated, specify this in your task: “Translate this page to German, but adapt the messaging for the German market rather than translating directly.” Use content strategy rewrite when cultural references, market positioning, or competitive context differs significantly between regions.

​
Brand Glossaries

Glossaries ensure consistent terminology across all translations. Common glossary entries include product names, feature names, branded terms, and industry-specific vocabulary.

​
Adding a Glossary

Glossaries are managed as rules in the Rules Manager:
  1. Navigate to Rules
  2. Click Create Rule Manually
  3. Add your terminology with source terms and approved translations
  4. Assign the rule to the translation workflow
Example glossary rule content:
Source TermTranslationNotes
DashboardDashboardKeep in English
Quick StartSchnellstartGerman
Customer PortalPortail clientFrench
Once configured, Gradial automatically applies your glossary to all translations.

​
Bulk Metadata Translation

Metadata fields like page titles, meta descriptions, and image alt-text are often overlooked in traditional translation workflows—they’re buried in CMS fields and easy to miss when content is exported for translation. With Gradial, you can translate these fields in bulk without leaving AEM:
  1. Create a task specifying the pages or section to translate
  2. Indicate you want to translate metadata/SEO fields
  3. Specify the target language
This ensures your localized pages are fully optimized for search without manual field-by-field work or separate metadata translation projects.

​
Human Review for Sensitive Content

Gradial handles the bulk of translation work, but we recommend adding human review for:
  • Regulated content — Financial, healthcare, legal, or pharmaceutical materials
  • Legal documents — Terms of service, privacy policies, contracts
  • Safety-critical content — Warnings, medical instructions, emergency procedures
For these content types, use Gradial to generate the initial translation, then route to qualified human reviewers before publication.

​
Best Practices

Set up glossaries before scaling. Consistent terminology is easier to establish upfront than to fix across existing translations. Start with quality source content. Clear, well-written source content produces better translations. Specify regional variants explicitly. Don’t assume “French” means the right variant for your market—be specific. Use bulk operations for metadata. Translate SEO fields in batches rather than page-by-page.