# How to Translate a WordPress Site: 3 Ways Compared | Vitra.ai > Plugin, proxy or manual duplication. Each puts the translated content in a different place, and that decides your SEO and your maintenance forever. **Canonical URL**: https://www.vitra.ai/general/how-to-translate-a-wordpress-site **Source**: This is the Markdown rendering of https://www.vitra.ai/general/how-to-translate-a-wordpress-site, generated at build time from that page. --- 5 min read # How to Translate a WordPress Site: 3 Ways Compared Plugin, proxy or manual duplication. Each puts the translated content in a different place, and that decides your SEO and your maintenance forever. [Samhitha J Bhatt](https://www.vitra.ai/author/samhitha) Senior Product Manager , Vitra.ai Updated Aug 17, 2026 ![How to Translate a WordPress Site: 3 Ways Compared](https://www.vitra.ai/static/images/blog/how-to-translate-a-wordpress-site.jpg) Table of contents [The three routes, honestly compared](#the-three-routes-honestly-compared) [What a plugin actually costs](#what-a-plugin-actually-costs) [What a layer costs](#what-a-layer-costs) [The parts of WordPress people forget](#the-parts-of-wordpress-people-forget) [SEO is decided by the URL structure](#seo-is-decided-by-the-url-structure) [Keeping it current](#keeping-it-current) [The route through](#the-route-through) [WooCommerce is a separate decision](#woocommerce-is-a-separate-decision) [Where to start](#where-to-start) [FAQ](#faq) Contributors [Samhitha J Bhatt](https://www.vitra.ai/author/samhitha) Senior Product Manager Subscribe to our newsletter Subscribe > **Quick answer —** There are three routes: a multilingual plugin that stores translations in your database, a translation layer in front of the site, or duplicating the site per language. The choice decides where content lives, how URLs are structured and how much work every future edit costs. ## The three routes, honestly compared Approach Where translations live Best when **Multilingual plugin** Your WordPress database You want editorial control per language **Translation layer** In front of the site You want speed and no database change **Separate installs** A second WordPress Markets need genuinely different content None is universally right, and vendors who claim otherwise are selling one of them. ## What a plugin actually costs A multilingual plugin gives editors a translated post they can edit like any other, which is genuinely valuable when a market needs its own angle rather than a rendering of yours. The cost is that it becomes structural. It touches your post types, your taxonomies, your permalinks and often your theme, and removing it later is a migration rather than a deactivation. Plugin conflicts also multiply, because every other plugin that writes content now has to be multilingual-aware too. ## What a layer costs A layer sits in front and renders whatever WordPress assembles, whichever plugin produced it. Nothing changes in the database and setup is measured in hours. The limits are real. Content generated entirely client-side after page load can be missed, anything behind a login may not be covered by default, and transactional email never passes through the site at all — which is usually the first thing a customer notices. [website translation](https://www.vitra.ai/features/website-translation) works this way, and the URLs it produces are indexable, which the browser-widget translators are not. ## The parts of WordPress people forget Menus and widgets. Category and tag names. The theme's own hard-coded strings — "Read more", "Leave a comment" — which live in the theme's .po files rather than in the database. Plugin output. Form labels and their validation messages. Media alt text. A site can be ninety percent translated and still feel English because the furniture around the content was never touched. ## SEO is decided by the URL structure Whichever route you pick, each language needs its own crawlable URL, correct reciprocal [hreflang](https://www.vitra.ai/general/multilingual-sitemaps) and a self-referencing canonical. A translated page sharing the English URL is invisible to search, and that is the single most common reason a WordPress translation project shows no traffic lift. Subdirectory, subdomain or separate domain matters far less than picking one and being consistent. ## Keeping it current The failure mode after launch is drift: an English post is edited and the eight translations quietly go stale. Whatever route you choose, translation has to fire on the publish event rather than waiting for somebody to remember. [translation memory](https://www.vitra.ai/features/translation-memory) makes that affordable, because an edited paragraph is the only part that reaches a model — the rest returns from what has already been approved. ## The route through Decide plugin versus layer first, because everything else follows from it. Then fix the URL structure, then translate content, then the theme strings. Setup steps and supported configurations are on the [WordPress integration](https://www.vitra.ai/integration/wordpress) page. ## WooCommerce is a separate decision If the site sells, the store is a bigger translation surface than the blog. Product titles and descriptions, attribute names and their values, category pages, cart and checkout strings, order emails and the customer account area. Attribute values are the specific trap. Translating a variation value like "Large" breaks the variation matching unless every dependent reference is updated with it, so decide at the attribute level rather than product by product. ## Where to start Audit the theme and plugin strings before you commit to an approach. If most of your visible text is theme furniture rather than post content, a plugin alone will not finish the job. ## FAQ **What is the best way to translate a WordPress site?** There is no single answer. A multilingual plugin suits teams wanting editorial control per language, a translation layer suits teams wanting speed without touching the database, and separate installs suit markets needing genuinely different content. **Do I need a plugin to make WordPress multilingual?** No. A translation layer renders whatever WordPress assembles without any database change, which avoids the plugin becoming structural. The trade-off is less per-language editorial control and gaps around logged-in content and email. **Why does my translated WordPress site get no search traffic?** Usually because each language does not have its own crawlable URL. Search engines index URLs, so a translated page served from the English address with a cookie deciding language is invisible to them. **What gets missed when translating WordPress?** Menus, widgets, category and tag names, the theme's own hard-coded strings, plugin output, form validation messages and media alt text. A site can be ninety percent translated and still read as English. Our blog ## Lastest blog posts Tool and strategies modern teams need to help their companies grow. Automotive [Automotive Brochure Localization by Market](https://www.vitra.ai/automotive/automotive-brochure-localization) A car brochure is a spec grid, a legal footer and a photo library, all market-specific. What actually has to change, and why the layout decides the schedule. [Samhitha J Bhatt](https://www.vitra.ai/author/samhitha) Aug 18, 2026 Automotive [Automotive Campaign Localization Across Markets](https://www.vitra.ai/automotive/automotive-campaign-localization) Campaigns run through national companies and dealer networks, so one master becomes hundreds of files. Where the offer text and the disclaimers actually break. [Samhitha J Bhatt](https://www.vitra.ai/author/samhitha) Aug 18, 2026 Automotive [Car Service Manual Translation for Technicians](https://www.vitra.ai/automotive/automotive-service-manual-translation) A workshop manual is read mid-repair by someone with the car on a lift. What that demands of procedures, torque figures and fault codes, in every language. [Samhitha J Bhatt](https://www.vitra.ai/author/samhitha) Aug 18, 2026 [View all posts](https://www.vitra.ai/blog/page/1) --- ## Structured data ```json { "@context": "https://schema.org", "@type": "Article", "mainEntityOfPage": { "@type": "WebPage", "@id": "https://www.vitra.ai/general/how-to-translate-a-wordpress-site" }, "headline": "How to Translate a WordPress Site: 3 Ways Compared", "image": [ { "@type": "ImageObject", "url": "https://www.vitra.ai/static/images/blog/how-to-translate-a-wordpress-site.jpg" } ], "datePublished": "2026-08-17T00:00:00.000Z", "dateModified": "2026-08-17T00:00:00.000Z", "author": [ { "@type": "Person", "name": "Samhitha J Bhatt" } ], "publisher": { "@type": "Organization", "name": "Vitra.ai", "logo": { "@type": "ImageObject", "url": "https://www.vitra.ai/static/images/vitra-v-logo.png" } }, "description": "Plugin, proxy or manual duplication. Each puts the translated content in a different place, and that decides your SEO and your maintenance forever." } ``` ```json { "@context": "https://schema.org", "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.vitra.ai" }, { "@type": "ListItem", "position": 2, "name": "General", "item": "https://www.vitra.ai/general" }, { "@type": "ListItem", "position": 3, "name": "How to Translate a WordPress Site: 3 Ways Compared", "item": "https://www.vitra.ai/general/how-to-translate-a-wordpress-site" } ] } ``` ```json { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "What is the best way to translate a WordPress site?", "acceptedAnswer": { "@type": "Answer", "text": "There is no single answer. A multilingual plugin suits teams wanting editorial control per language, a translation layer suits teams wanting speed without touching the database, and separate installs suit markets needing genuinely different content." } }, { "@type": "Question", "name": "Do I need a plugin to make WordPress multilingual?", "acceptedAnswer": { "@type": "Answer", "text": "No. A translation layer renders whatever WordPress assembles without any database change, which avoids the plugin becoming structural. The trade-off is less per-language editorial control and gaps around logged-in content and email." } }, { "@type": "Question", "name": "Why does my translated WordPress site get no search traffic?", "acceptedAnswer": { "@type": "Answer", "text": "Usually because each language does not have its own crawlable URL. Search engines index URLs, so a translated page served from the English address with a cookie deciding language is invisible to them." } }, { "@type": "Question", "name": "What gets missed when translating WordPress?", "acceptedAnswer": { "@type": "Answer", "text": "Menus, widgets, category and tag names, the theme's own hard-coded strings, plugin output, form validation messages and media alt text. A site can be ninety percent translated and still read as English." } } ] } ```