Automatic Translation
Provider selection, commercial entitlement, batching and safety.
Automatic providers generate translations from the WordPress backend. In commercial v0.20.0 builds, provider generation is a premium licensed operation. They are not called by visitors when switching language.
Available provider modes
| Mode | Behavior |
|---|---|
| DeepL | Calls DeepL directly from WordPress |
| Auto | Tries DeepL first and falls back to Google where needed |
| Calls Google Cloud Translation directly | |
| Custom / self-hosted | Calls a configured compatible endpoint |
Provider settings
Go to Instant Languages → Settings → Automatic translation provider.
You can configure:
- provider
- automatic queue continuation
- publication workflow
- request timeout
- batch size
- provider credentials and provider-specific preferences
Server-side secrets
Provider API keys are stored in WordPress options and are not exposed to frontend language-switcher JavaScript. Saved key fields are intentionally not printed back into Settings HTML.
Automatic publishing
The recommended workflow is Auto-publish after structural safety checks. Successful and structurally safe machine output becomes Translated and is immediately public. Suspicious output remains Draft for review.
DeepL/Google/custom provider generation, queue processing and whole-site automation require an active Stardetha commercial entitlement or valid grace period. Existing stored translations remain available without destructive lockout.