ConveyThis launched as a drop-in widget for WordPress and has since grown to 125 languages. Technically it remains JavaScript-first: the widget translates the page in the browser after load, and SEO subdirectories are added on top. Linguify inverts that: the edge server returns fully translated HTML on the first byte, no JavaScript needed for search engines to read every language. Same language count, different bet on where translation should happen.
you're on a shared host where DNS/CNAME changes are hard, you're OK with Google occasionally prioritising your source-language version in search, and you want the simplest possible widget install.
you want /es/, /fr/, /de/ to rank as independent pages in Google's international results from day one, or you want to choose the translation engine per language.
Side-by-side
| ConveyThis | Linguify | |
|---|---|---|
| Translation layer | ConveyThis: Client-side widget (JS) | Linguify: Edge server-side rendering |
| What Googlebot sees | ConveyThis: Source language on first request | Linguify: Translated HTML on first request |
| AI translation engine | ConveyThis: Fixed | Linguify: 6 providers, selectable per site |
| Free plan | ConveyThis: Yes, limited | Linguify: Permanent, 2,000 words |
| Business tier | ConveyThis: ~$14/mo · 50,000 words | Linguify: $16/mo · 50,000 words |
| Visual editor | ConveyThis: Yes | Linguify: Yes |
| Works with SPAs | ConveyThis: Yes | Linguify: Yes (widget mode) |
Why edge rendering beats client-side widgets for SEO
A client-side widget translates the page after it loads. Googlebot downloads the HTML, indexes the source language, and only runs JavaScript on a subset of pages. Your translated /es/, /fr/, /de/ URLs might get indexed — but the content inside often stays in your source language in Google's index. Linguify renders the translated HTML on the edge server before sending. Googlebot reads the translated content on the first byte. That difference is usually the deciding factor when international organic traffic matters.
Six AI engines vs one
ConveyThis picks the translation engine for you. Linguify lets you pick between Google Translation LLM, Gemini, Claude, GPT, DeepL and Google NMT, per site or per language. The practical effect: you can A/B different engines on a real page, pick the one that sounds most like your brand, and switch later without re-translating from scratch (translation memory is preserved).
Widget mode for SPAs is still available
If you're running a React or Vue app where edge rendering isn't possible, Linguify ships a drop-in JavaScript widget just like ConveyThis — same MutationObserver pattern, same localStorage cache. Most marketing sites, blogs and docs should use edge mode for SEO; SPAs should use widget mode.
Migrating from ConveyThis
Export your existing ConveyThis translations as JSON and import them into Linguify. The edge starts serving the imported translations immediately; switching your DNS from ConveyThis's CNAME to edge.linguify.site takes the client-side widget out of the loop. Budget 30 minutes total.