Skip to content

Optional analytics, session recording and advertising stay off unless you accept. You can reject them and use Transglot. Change your choice anytime in Cookie preferences. Cookie Policy

All integrations
spec sheet · docs & support

Ghost and Transglot, bring your publication into translation.

Choose Ghost in your project’s CMS settings, add your credentials, and select the content and languages to sync. Translate and review in one project, then publish to your mapped target languages.

Import into Transglot
Direction
Import into Transglot
Plan
Starter and up
Scope
posts and pages: title and plaintext
Authentication
the URL of your own Ghost site and an Admin API key
Get started
Connect from your project’s CMS settings.
docs & support
the workflow

Connect your content. Review every language.

Connect once, choose your content and languages, then translate and review in the same project. The steps below show how it works in your tool.

  1. Connect Ghost

    Choose Ghost in the project’s CMS settings. Add the URL of your own Ghost site and an Admin API key.

    connect
  2. Choose the content and locale mapping

    Select the types and fields you want to localize. The connector reads posts and pages: title and plaintext. Map the source and target locales to your project.

    map
  3. Sync and review the translations

    Start Sync from CMS to bring the selected source into your project. Translate and review the resulting keys alongside the rest of your project content.

    review
  4. Deliver through your project

    Pull the translated locale files through the API or CLI, or use the project’s CDN bundle. Ghost remains an import-only source.

    deliver
Read translated locale files through the Transglot API, CLI or CDN. Publishing changes back to Ghost is not part of this connector.
what moves

What you can translate and deliver.

Posts and pages come in as title and plain text over the Admin API. It stays one way because a Ghost post is monolingual and has no per locale slot, so a publish would land on top of the author's own copy.
What you can translate and deliver.
SurfaceWhat to expect
Source and scope

posts and pages: title and plaintext

Translated output

Read translated locale files through the Transglot API, CLI or CDN. Publishing changes back to Ghost is not part of this connector.

Keep in mind

Import only. Your original Ghost content is read, and this connector does not write translations back.

get connected

A few steps to your first connection.

Follow your tool’s setup below: add the connection, choose what to sync, and try it with a small set of content. Your team can keep working in the tools they already use.

What you need

the URL of your own Ghost site and an Admin API key.

  • A Transglot project with its source and target locales configured.
  • Save credentials in the connection settings so your team can work without copying secrets between files.
  • Hosted API access requires a paid Transglot plan. AI translation uses your workspace’s word allowance.
  1. Create a Transglot project with the source and target locales you need.

  2. Open the project’s CMS settings and choose Ghost.

  3. Provide the URL of your own Ghost site and an Admin API key.

  4. Save the connection, select the supported content, map locales, then run Sync from CMS.

same project, more possibilities

Connect the rest of your workflow.

Your translations stay in one project as they move between tools.

works with what you already run

41 connectors, already built.

bring your workflow

Your content, ready for every locale.

Connect your tools, translate with your team, and publish reviewed content.