Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Ghost does not automatically translate posts or pages when you change the publication language, add a language route, or tag content. You must create translated editorial content and decide how language versions are organized, linked, and surfaced to readers. Ghost recommends separate installs when each language has different content, and a translation service when the same content is published in multiple languages.
First, separate the three kinds of translation
“Translation” in Ghost can mean three different things, and only one concerns the words in your articles:
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Ghosts: A Graphic Novel | $7.11 | Buy on Amazon |
| 2 |
|
Ghost Afraid of the Dark | Halloween Picture Board Book for Toddlers with Glow-in-the-Dark Cover |... | $8.19 | Buy on Amazon |
| 3 |
|
The Pink Ghost | $9.95 | Buy on Amazon |
| 4 |
|
Ghost Goes Boo! An Interactive Book with 5 Sounds! (Five Funny Sounds!) | $8.97 | Buy on Amazon |
| 5 |
|
Ghost Book | $10.80 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
- Theme text: A theme can translate recurring labels and interface strings with Ghost’s
translatehelper and the publication language. This does not translate a post or page. Ghost names Tripoli, Galerie, and Basho as premium themes that include translation support. See Ghost’s theme translation documentation. - Ghost-generated interface text: Ghost’s publication-language setting is used by supported generated components, such as Portal, newsletters, search, and comments. In its November 5, 2024 announcement, Ghost said these components supported 60 languages, while noting that some translations might be incomplete. Coverage can change, so check the current interface in the language you plan to use. Ghost’s internationalization announcement.
- Editorial content: Posts and pages must be translated through your own editorial process or a translation service. Ghost’s theme translation helper is not a content translation system. Ghost’s translation guide.
Choose how to organize language versions
The right setup depends chiefly on whether your language editions publish different material or equivalent translations of the same material.
| Publishing model | Good fit | What you must plan |
|---|---|---|
| Separate Ghost install per language | Each language publishes different content. Ghost describes this as the easiest way to get started and its most sustainable long-term approach for that model. | Keep branding and navigation aligned as needed; coordinate newsletters, analytics, and maintenance across installs. |
| Translation service | The same material is published in multiple languages. Ghost names WeGlot and Transifex as examples. | Verify that the service supports your Ghost setup and desired publishing workflow. The cited Ghost documentation does not establish current integration depth, prices, or a preferred provider. |
| One Ghost install with language sections | You want language-tagged content within one publication and are prepared to manage routing and presentation. | Define language tags, URL patterns, translated slugs, equivalent versions, navigation, and how missing translations appear. |
| Custom frontend using Ghost’s Content API | You need custom language selection or relationships between entries in a separately built site. | Build and maintain the filtering, language selector, and mapping between translations. The API delivers content; it does not manage translations. |
Ghost’s recommendations for the first two models are in its multilingual publishing guide. Do not assume that the named services have a particular feature set or price without checking with the provider.
#1 Best Overall
Set up language sections in one install
Ghost’s dynamic-routing documentation shows how to set the base URL for the default language and add a route such as /de/ for posts tagged with the private tag #de. This organizes and routes German-tagged posts; it does not translate them or identify which post is the German equivalent of another post. Check the current syntax in Ghost’s routing documentation before deploying a configuration.
Before adding content, establish a consistent editorial convention. For each language, decide its tag, route prefix, slug style, and how editors will indicate that two posts are translations of one another. Then make the theme show readers how to reach available language versions. Routing and tagging alone do not create a language switcher or connect equivalent posts.
Connect translated posts and pages for readers
A translated post needs a clear path to its counterparts. Decide whether a reader who changes language should land on the equivalent post, the language section’s homepage, or a fallback page when no translation exists. Add those links through your theme, navigation, or a custom frontend; Ghost does not infer the relationship between separately created translations.
Pages require particular attention. Ghost pages use the same editor as posts and suit static material such as About, Contact, landing, and terms pages. Publishing a page gives it a URL, but does not automatically add it to site navigation, the homepage, or tag and author collections. Create translated pages and add their navigation links deliberately. Ghost’s page documentation.
Rank #3
If you send newsletters, decide how language audiences should receive them. Ghost’s translation guide recommends creating multiple newsletters for different language audiences. Also avoid hardcoding theme labels where possible; custom theme settings can let site owners supply translated labels. Ghost’s multilingual publishing guide.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Set the publication language without expecting it to translate content
Set the publication language in Ghost’s General settings. Ghost says this setting tells search engines what language the publication’s content is in and is also used for supported generated interface components. It does not create translated posts or pages, or connect language variants. Ghost’s publication-language help page.
Ghost’s November 5, 2024 announcement reported support for 60 languages across public-facing generated components, with popular languages fully translated at launch and some other strings potentially still in English. Treat that figure as the announcement’s status at that date, not a guarantee of complete coverage today. Check the actual components in your chosen language before relying on them. Ghost’s internationalization announcement.
Quick Recap
Best Value
What to decide before you publish
- Are language editions publishing different material, or matching translations? This determines whether separate installs or a translation-service workflow better matches Ghost’s recommendation.
- Who creates and updates translations when the original changes, and how will editors identify equivalent entries?
- What language-specific URL, slug, and tag conventions will you use?
- Where will readers find the language choice, and what happens when a translation is unavailable?
- How will translated static pages appear in navigation?
- Will newsletters be separated by language, and do supported Ghost-generated interface strings look complete in each target language?
- If using a service or custom frontend, what provider capabilities, costs, and maintenance obligations have you verified?
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
