A translation plugin is not an international-patient funnel

A translation plugin does a real job, and the good ones do it well. It reads the text on your existing site and serves it in other languages. The better ones handle the technical layer too: correct hreflang, a language subdirectory or subdomain, a switcher in the corner. If all you need is your current pages read in German or Italian, a plugin like Weglot or WPML is a reasonable answer.

Then watch what happens next. A German patient reads your translated implant page. She has a question, so she fills in your contact form. That's where the plugin's job ends and yours starts. The inquiry lands in your inbox in German, and someone has to read it, sort it from the dozen others that came in that day, answer it in a language she trusts, quote her, book her, and remind her. None of that is translation. All of it is the funnel.

Where a plugin stops

A plugin translates a website. That's the whole scope, and it's an honest one: it doesn't turn a foreign-language inquiry into a booked appointment. Here's the work that sits on the other side of the translated page, and none of it is something a translation layer was built to do.

• It doesn't route or auto-categorise the leads that come back. A treatment question, a price question, and a "when can you see me" all land in one inbox, in a language you may not read fluently, unsorted.
• It doesn't produce a treatment plan the patient can read. Quote an implant or an All-on-4 case and the estimate goes out in your language, as a plain email, not as a document she can take home and decide over.
• It doesn't book the visit. There's no calendar she can open, no held slot, no confirmation.
• It doesn't send the reminders that keep a booked patient from drifting away between the inquiry and the flight.
• It doesn't read her message back to you in your own language, or send your reply out in hers. You're left with a translated inbox and a dictionary.
• It doesn't give you a second pair of eyes on the language. Most plugins translate automatically and stop there, so an awkward phrase on a page about surgery stays awkward until a patient notices it.

Translation is the first step, not the last

This is a scope point, not a quality complaint. A good plugin translates accurately. The trouble is that translating the page is a small slice of what an international patient costs you in attention, and it's the only slice a plugin covers. The distance between a German reader on your site and that patient in your chair isn't language. It's everything after the language: the sorted inbox, the plan she can read, the calendar, the reminders, the reply that reaches you already in your own words. One full-arch case pays for the service many times over, and every one of those steps is what actually lands it.

So a translated website and an international-patient funnel are two different things. One is a page in another language. The other is the whole path from a foreign inquiry to a confirmed appointment, built as software, on a separate subdomain, with your existing site left exactly as it is.

We built DentalPolyglot to be the second thing. It mirrors your site to its own subdomain (clinic.dentalpolyglot.com), writes each language as its own idiom rather than string by string, and ships the funnel behind it: the auto-categorised inbox, the multilingual treatment-plan PDF, the booking calendar, the automatic reminders, and in-language replies both ways. The Expand tier adds a human review pass on the translation, and Concierge adds a professional native translator per language. Your original site is never touched, there's no script to install on it, and a new site goes live within a day.

If a plugin is all your practice needs today, use one. It's the honest answer for a clinic that only wants its pages read in another language. But if the reason you're translating at all is to turn more of those high-value cases into booked visits, translation is where the work starts, not where it ends. See how it works for the full path, or the plugin comparison for a side-by-side.