Running a publication

One site.
Every language you write.

Add the languages you publish in, then translate a post from its settings. Each translation is its own post, with its own address, its own search details and its own day to go live, linked to the others.

Create your site – free Start from your agent
Say it to your agent

Write the Spanish version of “Planting garlic in October” into its new Spanish draft.

  • update_publication
  • list_posts
  • get_post
  • replace_post

Two ways to do it.

By hand

In the admin

  1. As the owner or an admin, open Settings › General, add each language under Languages, and choose the default. Press Save.
  2. Open a post in the editor and open its settings drawer.
  3. Under Translations, press the button for a language, like + ES. A new draft opens in that language.
  4. Write the translation, give it its own slug, and publish it when it is ready.
  5. The default language keeps plain addresses, like /my-post. The others carry their code, like /es/my-post.

With your agent

In Claude, ChatGPT or your editor

Add Spanish to the languages we publish in.

Write the Spanish version of “Planting garlic in October” into its new Spanish draft.

List every post in Spanish, and tell me which are still drafts.

The tools it calls

  • update_publication
  • list_posts
  • get_post
  • replace_post

An agent writes and publishes posts in any language the site publishes in. It cannot yet link a new post to another as its translation: press the language's button in the drawer, give the draft a title, close the editor, and let the agent write the rest. While you have a post open, the agent's writes to it are refused with your name.

For example

  • A Korean-first food blog

    A cook in Seoul writes in Korean and adds English. Her Korean posts keep the plain addresses, and the English ones sit under /en.

  • A studio in two languages

    An architecture studio in Lisbon publishes each project in Portuguese and English. Each version names the other, and search engines get both.

  • Translate only what travels

    A local paper publishes every story in Dutch and translates only the guides for visitors. A language shows on the site once a post is out in it.

Questions, answered

Can PixelGlass publish one site in several languages?
Yes. Add the languages in Settings › General, then translate each post from its settings drawer. PixelGlass offers 45 languages, and each translation is its own post, linked to the others.
What do translated addresses look like on PixelGlass?
The default language keeps plain addresses, like /my-post. Every other language carries its code, like /es/my-post, and slugs can be written in that language.
Does PixelGlass tell search engines about my translations?
Yes. A page with translations links to each of them with hreflang. A page with no translation links to none.
Does each language get its own feed?
Yes. On PixelGlass each language has its own RSS and JSON feed, and the sitemap lists each translation beside the others.
Can I change a post's language?
While a post has never been published or scheduled, choose another language in its drawer. Once it is out, its language is fixed, because its address is public.
Is the admin translated too?
That is a separate choice. The PixelGlass admin speaks English and Korean, and each person picks their own.

Next, try

Every guide →

The features behind it

Every feature →

Every feature on every plan

Start your publication
today.

Plans from $9 a month. No platform fee on what your readers pay.

Create your site – free Start from your agent

14 days free. Have a site? Sign in