Start by choosing a delivery model
Delivery is the architectural decision underneath the interface. It decides whether translations live in your CMS, a browser script, or a service between the visitor and your site. Each can be right; each moves work and control to a different place.
Translating proxy
A hosted service serves translated pages in front of your site, usually on a subdirectory or subdomain. It needs no rebuild and works on almost any platform. Ask how it caches your pages, what visitors see during an outage, and how forms, cookies and logged-in pages behave.
CMS plugin that copies content
Some WordPress plugins store each language as its own post or page. Translations live in your own database and you have full control per language, but every edit to the original has to be carried over to each copy, and the copies can drift out of date.
CMS plugin that translates the rendered page
Other plugins keep one post and translate the HTML WordPress renders, including theme and page-builder output. Edits to the original flow through, and menus, footers and widgets are covered without extra setup. LangRelay works this way.
Client-side script
A script replaces text in the browser after the page loads. It is quick to add, but search engines may only see your original language. Check what the raw HTML contains before you count on it for SEO. LangRelay’s script embed is in this category and makes no SEO claim.
Six questions to ask every tool
1. How does a translated page reach the visitor?
Follow the request. Is the translated HTML rendered by your CMS, served by a proxy, or swapped in by the browser? Check it works with your hosting, CDN, cache plugin, forms and consent banner, and who is responsible when it breaks.
2. What happens when the original page changes?
Launch day is the easy case. Edit a heading, delete a paragraph, publish a new page. Does the tool notice? Does it reuse what was already translated? Can you see what is new, out of date or waiting for review? Recurring changes, not the first translation, decide what a tool costs you in time.
3. Who checks a translation before it goes live?
Many tools publish machine translation the moment it exists. That is fast, and often fine, as long as something catches a page that came out wrong. If your brand, legal copy or product names matter, look for checks that hold a bad page back, a way to approve the pages that matter yourself, and AI that flags problems rather than hiding them.
4. Who controls multilingual SEO?
Translated body copy is not enough. Check per-language URLs, translated titles and descriptions, canonical tags, hreflang, translated slugs and sitemaps. View the page source yourself; a page that looks right in the browser does not prove search engines see it.
5. What do you keep if you leave?
Plugins that store translations in your database leave them behind when you cancel. Hosted services usually stop serving them. Ask what you can export, and what your translated pages show the day after your subscription ends.
6. How much can AI do for you?
Almost every tool now uses neural or AI translation. Fewer use AI for the work around it: reviewing translations, answering “what still needs doing?”, or making a change you describe in a sentence. And if you already work in Claude or ChatGPT, ask whether the tool can be reached from there.
Where LangRelay fits
LangRelay is built for WordPress sites that keep changing, and for the people who look after them. Its plugin translates the rendered page, so there are no duplicate posts and no string keys. You edit translations in a translation workspace and a visual editor. They go live as they are ready, free checks hold a page with untranslated text, the wrong language or a changed price, and legal pages, pricing pages and sweeping changes always wait for you. You can also choose to approve every page yourself. Relay reads your Site’s pages and translations, drafts the changes you ask for, and reviews any page you ask it to.
It is not the right choice for everyone yet. Outside WordPress, LangRelay’s script embed translates in the browser without SEO value, so a Shopify, Webflow or custom site that needs indexed translations is better served by a proxy for now. Translated slugs are set by hand, and the API and MCP access for your own assistant are on the way, not shipped.
Run a practical test
Give every tool on your shortlist the same small test. Pick a page that changes often, add one language, and:
- Publish the translated page on the URL you want to keep.
- Check its HTML, title, canonical, hreflang and sitemap entry.
- Edit the original and see how the tool notices and shows the change.
- Have the person who will review translations correct one and approve it.
- Export what you can and write down what happens if you cancel.
That hour tells you more than any table, this one included. If you want to run it on LangRelay, start on the free plan or book a demo and bring a page that changes regularly.
