Speak to the world in its own words.
served as HTML · indexable
glotto is a translation proxy.
It sits in front of your website and serves every page in the languages you pick, as ordinary HTML that search engines can index.
Nothing to install. You point a subdomain at it, or add one script tag if you can’t change DNS. We’re still building it, so for now there’s a waitlist.
We’ll email you once, when it’s ready.
how it will work
your site
with glotto · in japanese
example-shop.com is made up
- 01
Pick languages. Whatever the translation engine you choose supports. You can add or drop one later.
- 02
Connect your site. A CNAME for a subdomain like fr.your-site.com, a /fr/ path prefix, or a plugin for your platform.
- 03
Visitors arrive. The first request for a page is translated on the way through and cached. The next ones are served from the cache. Your server sees the same traffic it always did.
Requests flow from the visitor through the glotto edge, which translates and caches, to your origin, which stays untouched.
indexing
“Does Google index the translated pages?”
Yes. That’s the reason it’s a proxy.
- The translated text is in the HTML the server sends. A crawler doesn’t have to run JavaScript to see it.
- Each language has its own URLs,
fr.your-site.comor/fr/…, so every version can be linked to and ranked on its own. - hreflang links between the versions are added for you, so Google knows which page is which language.
- Translated pages are cached, so they load about as fast as the original.
- ChatGPT, Perplexity and Google’s AI overviews read the same HTML, so they can cite the translated pages too.
GET ja.example-shop.com
200 · text/html
<title>手作りのオーク家具</title>
<link rel="alternate" hreflang="en"
href="https://example-shop.com/" />The translation is already in the HTML.
can’t change DNS?
The proxy is the main product. If you can’t change DNS yet, there’s a script tag that translates in the browser instead.
It’s a reasonable way to try glotto on a live site, or to use it when DNS belongs to someone else. The trade-off is that the translation happens after the page loads, so search engines index the original language, not the translation. Switch to the CNAME when you want the translated pages indexed.
<script
src="https://js.glotto.io/v1.js"
data-glotto="YOUR_SITE_KEY"
defer
></script>what’s in it
dashboard
Edit any translation
If the machine gets a sentence wrong, change it in the dashboard. It stays changed.
glossary
Terms translated your way
Product names and terms you list are left as they are, or translated the way you say.
script
Covers client-rendered text
A small script, about 5 KB, translates text your frontend renders after the page loads.
engine
Machine translation or an LLM
Plain machine translation, or an LLM with notes on your tone. Chosen per language.
export
Yours to take with you
Download every translation as a file, whenever you like. Nothing is held back if you leave.
cache
Fast after the first visit
A page is translated once, then served from cache like a static file.
things you don’t have to do
- installing an SDK
- moving to an i18n framework
- extracting strings into translation keys
- sending spreadsheets to an agency
Translating a site shouldn’t mean rebuilding it.
Most translation tooling asks you to change your site first: extract the strings, adopt a framework, keep the keys in sync, and ship all of that before one page is translated. A proxy skips that part. Your site stays as it is and the translation happens on the way to the visitor. That’s the idea behind glotto.
status · updated when it changes
- next up: first pilot sites
- demo studio: coming soon
- waitlist: open
- launch: one email to the list
Get on the list.
Early access goes out to this list in sign-up order. One email when it’s ready, nothing else.