g-lingo · languages
g lingo
One post per language, translated where you already write
No second interface. Each language is an ordinary post joined to the original in a translation group, so templates, queries and third-party plugins keep working on translations.
10
Languages
45%
Coverage
/de/
Clean prefixes
1
Source changed
01 — Content × language
One matrix answers what is still missing.
Translated, needs update and missing — per item, per language. Editing an original marks its translations stale instead of letting them drift quietly out of date.
Translated
green dot
Needs update
amber
Missing
dashed
02 — Translate where you write
The panel sits in the normal page editor.
See which languages are ready, open one to edit, or create a missing translation without leaving the page. Fields, meta and slugs follow the rules set in Translatable Content.
03 — Part of the design
The switcher is yours to draw.
Here it is a terminal dropdown. Correct hreflang on every page and a multilingual sitemap declared in robots.txt come with it.
compared with what you use now
topic
wpml / polylang
g lingo
Storage model
Custom tables and string maps
One ordinary post per language
Editing
A separate translation editor
The block editor you already use
URLs
Prefix for every language
Original at root, /de/ /fr/ for the rest
SEO
Plugin-dependent hreflang
hreflang plus multilingual sitemap
Third-party plugins
Often need bridges
A translation is just a post
questions
g lingo · straight answers
Can I license it for a site you did not build?
No. The kit is not licensed outside the projects we deliver at byfriday.co.
Do I have to translate everything at once?
No. Coverage is tracked per item and untranslated content falls back to the original.
Is machine translation involved?
Only as a draft you then edit — it never publishes on its own.
next
g cpt