Translations
Any article you write in Asky can become a set of language versions that live alongside the original. Asky translates the whole piece, not just the body: the title, the meta description, your CMS fields, and the internal links, so each language arrives as a finished, publishable draft rather than a rough machine translation.
Translations are available on Scale and above.
Accessing Translations
Go to Content in the sidebar, open a draft, and click Translations in the editor toolbar.
The menu lists the original and every language you have made from it. New translation starts another one. Any draft with a title and a body can be translated, and it does not need to be published first.
| Status | Meaning |
|---|---|
| Queued | The translation is waiting to start |
| Translating | Asky is working on it now |
| Failed | Something went wrong. Hover to see why, then click Retry |
A finished translation shows no progress label. Once you send it to your CMS the row shows its publishing status instead, using the same statuses as Content.
Creating a Translation
Pick a Target Language
Choose the language to translate into. Languages you have already translated this article into are listed but greyed out, marked Already translated. The article’s own language is not in the list at all.
Set the Tone
For the languages marked in the table below, choose a Formality. For an English target you get English spelling instead. Every other language shows no control here. Both are pre-filled from your brand defaults.
Choose Which Custom Fields to Include
Optional. If the draft has CMS fields mapped, open Custom fields to see which of them will be translated, and clear any that should stay in the source language.
Review the Links
Asky lists every internal link in the article next to the URL it will point to in the new language. Edit any target, skip a row to keep the original link, or leave the suggestions as they are.
Start the Translation
Click Start translation. Asky opens the new draft straight away and fills it in while you keep working. It usually takes a minute or two, and you get a notification when it is ready, so you can close the tab.
What Gets Translated
| Part of the Draft | What Happens |
|---|---|
| Title | Translated. The URL slug is regenerated from the translated title |
| Meta description | Translated |
| Body | Translated, with formatting, images, tables, and links kept in place |
| Mapped CMS text and rich-text fields | Translated. You can leave any of them out |
| Alt text on mapped CMS image fields | Translated. The image itself is untouched |
| Numbers, dates, references, and other non-text CMS fields | Copied across unchanged |
| Author, featured image, topic, and content type | Copied from the original |
| Content inside code blocks | Excluded from translation |
Everything is translated together as one document rather than field by field, so terminology stays consistent between the headline, the body, and your CMS fields. The result then goes through a second editing pass that reads it against the original and fixes what machine translation usually gets wrong: idioms taken literally, phrasing that is correct but not what a native speaker would write, and link text that reads awkwardly in the new language. Your brand name is carried through as context, so product and brand names are not translated into something else.
Asky checks the edited version against the plain translation before saving it to ensure your translation is correct and not adding or leaving out anything from the original.
Internal Links
An article that links to your own pages should link to the right language version of those pages. Asky finds the internal links in the draft, looks for the translated version of each one on your site, and shows you the whole list before anything runs.
- Edit any target URL to point somewhere else
- Skip a row to leave that link exactly as it is
- Reset an edited row back to the suggested URL
Links Asky cannot find a translated version for are flagged with a warning and keep their original URL. If the list is empty, or most rows are unresolved, run a scan from Pages so Asky has an up-to-date picture of your site.
External links are never rewritten, and link rewriting applies to the article body rather than to custom CMS fields.
Editing a Translation
A finished translation is an ordinary draft. Open it from the Translations menu and edit the title, meta description, slug, body, and CMS fields exactly as you would the original. Content edits are independent: changing the original afterwards does not change a translation, and the other way round.
The one setting that is shared is the CMS collection. Changing it on any language applies it to every language in the family, and Asky warns you before it does.
Translations always branch off the original article, so a translation cannot itself be translated. Start every language from the source draft.
Publishing Translations
When a draft has translations, the publish button opens Review & publish translations instead of the single-draft flow. Every language gets a row, and every ready row defaults to Save as draft. Switch a row to Publish now, or Re-publish if it is already live, or Skip, then confirm. Rows that are still translating cannot be published until they finish, and rows that failed have to be retried first.
Webflow
Webflow keeps every language as a locale variant of one CMS item, so Asky maps each language onto one of your site locales. The match is usually automatic. Where it is not, pick the locale from the dropdown on that row and Asky remembers the choice for next time. Use Refresh locales after adding a locale in Webflow.
The primary-language article has to reach Webflow first. Webflow creates the item in its primary locale, and every translation is added as a variant of that item. Set the primary-language row to Publish now or Save as draft in the same run, or publish it on its own first.
Two situations need a decision from you:
- The language matches no Webflow locale. The row publishes as its own separate CMS item, flagged as unlinked. Add the locale in Webflow, click Refresh locales, and publish again if you want the languages joined.
- The locale exists in Webflow but not on the item Asky already published. Webflow’s API cannot add a locale to an item that already exists, so open that item in the Webflow Designer, add the locale there, and publish again. Choosing Publish unlinked on the row is the alternative: it publishes as a separate item instead.
See Webflow for connecting and configuring the integration.
WordPress
WordPress.com and self-hosted WordPress have no native link between language versions, so each language publishes as a separate post and Asky says so in the dialog. Use a WordPress multilingual plugin if you need the posts joined.
Sanity
Sanity keeps each language as a separate document and links them for you, so Studio’s language switcher works. See Sanity for the details, including what happens on projects that use field-level localization instead.
When a Translation Fails
A failed translation stays in the Translations menu, marked Failed, with the reason on hover. Click Retry there, or Retry translation on the draft itself. If a translation shows no progress for about fifteen minutes, a Restart translation button appears on the draft.
A retry re-runs the same language, but it does not carry over the link rewrites you edited by hand, and formality and English spelling fall back to your brand defaults. If you set any of those by hand, delete the failed language and start it again from the dialog instead of retrying.
Deleting Translations
Deleting a translation removes only that language, and frees it so you can translate the article into it again.
Deleting the original does not delete its translations. They stay in your library as separate articles, unless you tick Delete all language versions in the delete dialog and type DELETE to confirm.
Deleting never removes anything from your CMS. Anything already published stays live, and a fresh translation of the same language publishes as a new item rather than replacing the old one.
Translate Pages From Your Site
Pages already live on your site can be translated too, whether or not Asky wrote them. Asky reads the page, keeps it as a read-only original, and makes one translation per language. Headings, paragraphs, lists, tables, buttons, captions and image descriptions are translated where they sit. Code is copied exactly as it is, and links point to your translated pages where they exist. Anything that cannot be pasted, such as a form, a video or content hidden on the page, is listed for you to handle.
Pick the Pages
In Workflows, click New workflow and choose Translate content. You can also open the Translated Content tab in Content and click Translate Content. Tick up to 20 pages from your site, or paste the address of any public page. Pages you translated before show the languages they already have.
Pick the Languages
Choose up to 8 languages, with your markets’ languages listed first. Formality and English spelling work as they do for an article. If any of the pages already has one of the languages, Replace existing translations appears. Leave it off to keep those translations as they are.
Start
Click Translate. Each page shows up in Workflows while it is read and translated, and you get a notification when its translations are ready to review. A page is never translated into the language it is already in.
Copy to Your Site
These translations are not published from Asky. Open one and review it like any draft, then open Copy to your site:
- Copy Article copies the whole article, its tables, buttons and images back in place, as formatted text, HTML, plain text or Markdown.
- Compare with Original opens the translation beside the original page, so you can review it and finish it in one place before you paste.
In Compare with Original:
- Page details: the title, the slug, the meta description, and any other CMS field that was translated, each beside the original with its own copy button, and a warning when a field is longer than your CMS allows;
- Article: the article block by block beside the original, with its tables, buttons and images back in place. Hover any part to copy just that part, for page builders where each block lives in its own widget;
- everything on the translated side can be edited right there: click the text and type, the same way you edit a refreshed page. The words inside tables, buttons and images open in their own editor;
- anything left out, such as forms and embeds, is marked where it sits on the page, plus links that still point to pages in the original language.
Paste it into the matching language version of the page in your CMS, then click Mark as Published. Copy in the editor toolbar copies the same assembled article.
The Original
The original is read-only: it is the text every translation of that page is made from. When the page changes on your site, open the original and click Read the page again. Translations you already made keep the text they were made from, and new translations use the fresh read.
Credits
Each translation uses 40 credits, given back if it cannot be finished. Reading a page is free. One request can start up to 60 translations.
Limitations
| Aspect | Limitation |
|---|---|
| One per language | An article has one translation per language. To redo a finished one, delete it and translate again |
| Pages from your site | Translations are copied into your CMS by hand. Asky does not publish them |
| Translating a translation | Not supported. Every language branches off the original |
| Link rewriting | Applies to the article body, not to custom CMS fields |
| Webflow ordering | The primary-language article must reach Webflow before any translation |
Next Steps
- Write the article you want to translate in Creating Content
- Set your default tone and spelling in Brand Profile
- Connect a CMS: Webflow, WordPress or Sanity