great That was the promise of every automatic website translation plugin, and in 2026 it no longer works. AI search does not reward fifty copies of the same page. It rewards two or three languages done properly, with real local content, on servers your customers can reach. This page explains why, and what to do instead.
I believed the promise too, and started with hirudo.clinic. What followed was a broken robots.txt and a site Google could not read. Nobody had warned me. The story stays on this page because it explains, faster than any manual, what automatic website translation really involves.
After the story comes what I do for clients today. I install and tune multilingual WordPress sites in the two or three languages that bring customers, from $1,000. There is a separate route for anyone who needs to be seen inside Russia or across the Gulf.
Website Translation and Its Underwater Stones: What They Don’t Advertise
I thought translating my website would be easy, just as the plugins advertise. I chose TranslatePress, the plugin the Astra theme recommends, and expected a smooth ride.
A few days later I ran hirudo.clinic through Google PageSpeed Insights and hit the first underwater stone.
What I Did to Fix It
I fixed robots.txt by hand so the translation rules could no longer break it. I edited .htaccess to stop the automatic redirects. Then I cleared the cache and ran the SEO checks again to undo the damage.
If you use TranslatePress with the Astra theme, check your site now. You may be losing search visibility without realising it.
Has anyone else run into hidden problems like this? I would be glad to compare notes.
Why Not Just Fix Automatic Website Translation Yourself?
Every automatic website translation plugin has a page of advanced settings. They have names like “Fix missing dynamic content”, “Filter Gettext wrapping” and “Disable dynamic translation”. The descriptions are one line each. They say nothing about what happens to the rest of your site when you switch them on.
Some of them stop stray code such as #!trpst#trp-gettext from appearing in your titles and metadata. One of them will quietly break AJAX-loaded content. Which is which depends on your theme, your caching plugin and how your pages are built.
The Settings Are Not the Whole Story
None of those settings fixes the robots.txt problem I described above. It sits in the way the plugin rewrites URLs. The fix lives in robots.txt and .htaccess, outside WordPress. Change the wrong line there and you can take the whole site offline, or send Google to pages that do not exist.
The choice of URL structure is just as delicate. Whether the default language sits in a subdirectory decides how every address on the site looks. Change your mind later and you have to redirect every page.
What Usually Goes Wrong With Automatic Website Translation
Most of the sites I look at were translated by their owners in an afternoon. They looked fine in the browser. The trouble shows up weeks later in Search Console: pages dropped from the index, duplicate titles, a sitemap full of addresses Google cannot open, and a PageSpeed score through the floor because every language loads the translation script twice.
The list of languages is another trap. The plugins offer fifty or more, and it is tempting to switch them all on. Every language you add multiplies the pages Google has to crawl, the size of your sitemap and the load on your server. Most of those pages will never be read. It is far better to tune the two or three languages your real customers use, such as Russian, Arabic or English. Do those properly instead of publishing fifty half-working copies of the site.
None of this is visible from the front of the site. That is why the plugins can advertise a smooth ride. It is visible from the server and from Google’s side, and that is where I do the tuning.
Why I Do Not Recommend Translating Into Many Languages
Ten years ago a site in fifteen languages looked impressive and did little harm. In the age of AI search it is a liability, for three reasons.
Search engines now punish it
Since 2024 the main search engine has had a rule against scaled content abuse. Automatic website translation into many languages with little added value is one of the patterns it names. Sites that pushed the same thin text into twenty, thirty or fifty languages were among the biggest losers of the 2026 updates. Many of them lost half their traffic within weeks.
AI search keeps one version
The AI answer engines do not read your French, German and Spanish pages as separate pages. They boil the meaning down and notice that all fifteen say the same thing. Then they keep one version, usually the English one. A translated page with no local prices, delivery terms, legal wording or reviews adds nothing new. So it never appears, even when it is indexed and every hreflang tag is correct.
Every language is another site to maintain
Every language you add is another copy of every page. Each copy needs checking after every plugin update, theme update and price change. Fifty languages means fifty chances of a broken page. You will not notice, because you cannot read it.
So my advice is the opposite of what the plugins sell. Choose the two or three languages your real customers speak. Give each one a proper native-speaker version with local substance. Host it where those customers can reach it. Leave the other forty-seven switched off. The packages below are built around exactly that.
Use a subdirectory for the default language
| Setting | Options | What it does |
|---|---|---|
| Use a subdirectory for the default language | No / Yes | Select Yes if you want to add the subdirectory in the URL for the default language. By selecting Yes, the default language seen by website visitors will become the first one in the “All Languages” list. |
Need Your Website Translated and Set Up Properly? Installation and Tuning from $1,000
After going through all of this, I now do it for clients. I install and tune automatic website translation on WordPress sites. The translated pages display correctly, and Google, robots.txt and the sitemap keep working. Prices start from $1,000 per website for the first language.
Why It Takes Three Days, Not Twenty Minutes
Installing the plugin takes about twenty minutes. Anyone can do that part. That is also how people end up with a broken multilingual website. So the three days are not the installation. Instead, they cover everything you must check afterwards. That work happens on the server and on Google’s side, where nothing shows from the front of the site.
The first day goes on decisions you cannot reverse. Your default language can sit in a subdirectory. That one choice changes every address on the site. Change your mind a month later, and every page then needs a redirect. So we set the URL structure first. We also protect robots.txt and .htaccess from the plugin’s rewrites. Then we confirm the sitemap still opens.
Day two covers what translation plugins leave behind. Page titles and meta descriptions come first. Then menu items, buttons, contact forms and cookie notices. Anything the page loads after it draws needs checking too. Those are the words your customers read and Google indexes. Yet they quietly stay in English while the body text changes language.
Proof fills the third day. Someone who speaks each language opens it and reads it. We validate the hreflang tags and resubmit the sitemap. We also re-test the site for speed, because a second language can easily double your loading time. Finally, you receive a short report. It lists every check we ran and everything we found.
You are not paying for a plugin. You are paying for someone to look at the parts you cannot see — before Google does.
We work from Central London. Our verified Google Business Profile, client reviews and latest updates are on Google Maps.
Advanced Stage: Launching Your Website in the Russian or Arabic Market, from $3,000
Russia: hosting, Yandex and the data rules
A Russian version of your site is only half the job. Since 2024 Russian providers have been cutting connections to sites behind foreign content-delivery networks. The Russian regulator openly advises against them. Mobile-internet shutdowns became routine in 2026. During a shutdown only a short approved list of Russian services stays reachable. A site on a foreign server may open one day and not the next. Your translated pages, however good, stay invisible to the people you wrote them for.
The advanced stage deals with this. I host a copy of the site with a Russian provider, or serve it through a Russian content-delivery network, on a .ru domain. Yandex reads that domain as a sign that the site belongs to Russia. Yandex, not Google, handles more than six in ten Russian searches, and it ranks differently. It cares less about links and more about whether visitors stay, scroll and come back. It also shows different results in Moscow and in Vladivostok.
So I register the site in Yandex Webmaster with a primary region and install Yandex Metrica. A native speaker writes the Russian text around what Russians actually type into a search box, not a word-for-word copy of your English keywords.
Does the site collect names, phone numbers or addresses from Russian customers? Then Russian law requires you to keep the main copy of that data on servers inside Russia. Fines for ignoring this start at one million roubles. I explain what this means for your forms and booking system and set them up accordingly.
The Arabic-speaking Gulf: dialect, right-to-left and local trust
The same service exists for the Arabic-speaking market, and the traps there are different. Gulf customers search in their everyday dialect, not in the formal Arabic a translation engine produces. A page can rank first for a word nobody types. The layout has to run right to left with the dir attribute set. It needs Arabic fonts that people can actually read on a phone, local currency and local phone formats. Each Gulf state needs its own hreflang tag. Arabic URL slugs break when people share them by email or WhatsApp, unless you handle them properly.
I cover this from London and Dubai with a native-speaker writer and our UAE team at whatox.com, who handle Arabic SEO and web services in the UAE.
This is a bigger project than a plugin installation. The price depends on the size of your site and what it sells, so I quote on request, from $3,000. If the Russian or Arabic market is your goal, say so in your first email. I will then quote for the whole route rather than for the translation alone.
Questions People Ask About Automatic Website Translation
For showing a page in another language, yes. For ranking, only if it is tuned: hreflang tags in place, titles and meta descriptions translated, robots.txt and the sitemap left intact by the plugin, and the key pages read through by a native speaker. Without that, the translated pages are either indexed as thin duplicates or not indexed at all.
My setup starts from $1,000 for the first language. That covers choosing and installing the plugin, configuring the language and URL structure, checking robots.txt, .htaccess, sitemap and caching, a native-speaker review of the key pages and a PageSpeed and Search Console check before handover. SEO translation of titles, descriptions and menus, and every further language, are quoted separately by the number of pages.
It depends on your theme, your hosting, whether you want automatic or human translation and how many pages you have. Each has its own traps; TranslatePress, for example, can quietly redirect robots.txt. I choose after looking at the site, not before.
Being seen inside Russia
Since 2024 Russian providers have been dropping connections to sites served through foreign content-delivery networks. Mobile-internet shutdowns leave only an approved list of Russian services reachable. Foreign domains have also been removed from the national DNS. To be seen inside Russia a site needs Russian hosting or a Russian CDN, usually a .ru domain, and a proper presence in Yandex. I offer this as a separate stage from $3,000.
How many languages, and what about Arabic
No. Search engines now treat mass machine translation with little added value as scaled content abuse, AI search collapses identical pages in different languages into one version, and every extra language is another copy of the site to maintain. Two or three languages that real customers use, done properly, bring more than fifty done badly.
Yes. Arabic needs keyword research in the dialect Gulf customers actually type, a right-to-left layout with readable Arabic fonts, local currency and phone formats, and separate hreflang tags for the UAE, Saudi Arabia and the other Gulf states. I handle it together with our UAE team at <a href=”https://whatox.com/arabic-seo/”>whatox.com</a>.
The $1,000 package covers the installation and tuning of the first language. Anything beyond that is a separate job. That includes SEO translation of titles, meta descriptions and menus, further languages, large catalogues or booking systems, sites on unusual themes or page builders, ongoing maintenance after plugin updates, and a full human translation instead of a review. It also includes the launch of your site in the Russian or Arabic market described above (from $3,000).
This work is more complex, and the price depends on how the site is built and how many pages it has. So I quote it on request. Send your website address and the languages you need to london@russian-english.com. I will reply with a fixed price for the setup and, if you need it, an estimate for the further work.