How to Translate a Ghost Blog (No Plugin Exists)

Quick answer — Ghost has no plugins and no native multilingual mode, so the options are a translation layer in front of the site, routing tricks with collections, or running Ghost headless and handling languages in your own front end.

No plugins is a constraint and a mercy

Every WordPress multilingual discussion is really a discussion about plugins: which one, what it does to the database, how it conflicts. Ghost removes that conversation entirely because there is nothing to install.

What remains is three honest options, and they are easier to compare than WordPress's because none of them modifies the CMS.

Option one: a layer in front

The lowest-effort route. A translation layer receives the rendered page and serves it on a language-specific URL, and Ghost never knows it happened. Nothing in the admin changes, editors keep working exactly as they do, and setup takes hours rather than a sprint. website translation works this way and produces indexable URLs per language, which is the part that decides whether the work earns traffic.

Option two: collections and routes

Ghost's routes.yaml can map a URL prefix to a collection filtered by tag. Tag posts lang-fr, route /fr/ at that collection, and you have a language section inside one Ghost install.

It works and it is manual. Every post needs its translated twin created and tagged by hand, the two are not linked to each other in any way Ghost understands, and nothing tells you when the English version has been edited.

Reasonable for a site publishing a few posts a month. Not reasonable at volume.

Option three: headless

Ghost as a content API behind your own front end, with language handling in the application. Full control, and a considerably larger project than either of the above.

Choose this if you were going headless anyway. Do not choose it only to get languages.

What Ghost-specific content needs translating

Post content and excerpts, obviously. Also tag names and descriptions, which appear on archive pages. Author bios. The theme's own strings, which live in the theme's locale files. Newsletter templates and subscription copy, which sit outside the page entirely and are the ones readers actually notice.

SEO on a Ghost site

Ghost handles canonicals and sitemaps well, so the main thing to get right is that each language sits on its own path and declares reciprocal hreflang.

The built-in sitemap will not know about a translation layer's URLs unless it is configured to.

Keeping up with publishing

Ghost sites publish on a cadence. Whatever route you take, the translation has to trigger on publish rather than in a weekly batch, or the language versions run permanently behind. translation memory keeps recurring newsletter and footer copy free after the first pass.

Configuration details are on the Ghost CMS integration page.

Members and subscriptions

Ghost's membership features add another content surface: signup and signin pages, tier names and descriptions, the account portal and every transactional email around subscribing, upgrading and cancelling.

None of that lives in a post. All of it is read by the people who have already committed enough to pay, which makes it a strange thing to leave in English.

Structured data and social cards

Ghost emits Open Graph and structured data from post metadata. A translated post served through a layer needs those regenerated in the target language, or the social preview and the search snippet stay English while the page is not.

Where to start

If you publish weekly or more, use a layer. The routing approach only stays manageable at low volume, and most Ghost sites that try it abandon it within a few months.

FAQ

Does Ghost support multiple languages? Not natively, and there are no plugins. The realistic options are a translation layer in front of the site, routes.yaml collections filtered by tag, or running Ghost headless with languages handled in your own front end.

Can routes.yaml handle a multilingual Ghost site? Yes, by mapping a URL prefix to a tag-filtered collection. It is entirely manual — each translated post is created and tagged by hand, the pair is not linked, and nothing flags when the original changes.

What is the fastest way to translate a Ghost blog? A translation layer in front of the site. Ghost is unaware of it, editors keep working unchanged, setup takes hours, and it produces the indexable per-language URLs that decide whether the work earns traffic.

What gets missed on a Ghost site? Tag names and descriptions that appear on archive pages, author bios, the theme's own locale strings, and newsletter and subscription copy, which never passes through the page and is what readers notice first.