How to Translate a WordPress Site Without a Plugin: What Actually Works

You want to offer your website in another language. Before installing another plugin, it is reasonable to ask whether you can do the work with the WordPress tools you already use.

Yes, you can translate a WordPress site without a plugin. You can replace its existing content with a new language, publish translated pages and connect them manually, or maintain separate sites for each language. What WordPress does not provide out of the box is a complete workflow for connecting and managing those translations. WordPress multilingual documentation

For a small website, a manual approach may be enough. The important question is what happens after publication: when a service changes, a new page goes live, or a visitor switches languages halfway through browsing.

This guide explains the practical options, including a simple walkthrough for adding translated pages without a multilingual plugin.

First, decide whether you need one language or several

These are two different projects.

Replacing your website’s language means rewriting the existing content. For example, an English website becomes French-only. You do not need to connect English and French versions if you no longer intend to offer both.

Adding another language means keeping both versions available. Visitors need to find the right content, move between languages, and continue their journey without unexpectedly returning to the original language.

Neither is the same as changing Settings → General → Site Language. That setting controls WordPress’s default language; it is not a page-translation command. Available language packs can also affect built-in theme and plugin labels, but the text you wrote still needs translation. WordPress general settings

Throughout this guide, “without a plugin” means without adding a multilingual plugin. You can still use your existing editor, theme, and other site tools.

Choose the approach that matches your website

Your goal	Suitable approach	Main responsibility
Turn an existing site into a different, single language	Translate the current content in place	Review the whole visitor experience before launch
Offer a few important pages in two languages	Publish and manually connect translated pages	Keep links, shared navigation, and updates consistent
Run independent regional websites	Separate installations or WordPress Multisite	Maintain each site and coordinate shared information
Build a highly customized multilingual experience	Developer-built solution	Budget for development, testing, and ongoing support

Browser translation is another way for visitors to read your site, but it does not publish translated content on your behalf. We will cover that distinction below.

Option 1: Replace the current website language

If your website will serve only one language, you can translate its existing content directly.

Imagine you built a small business website in English but now want it entirely in French. You do not necessarily need a multilingual setup. You need a careful content conversion.

Before editing, make a backup and, where possible, work on a private staging version so visitors do not encounter a half-translated site.

Then work through the site in this order:

1. Translate the homepage and main service pages.
2. Update the navigation, header, footer, buttons, and contact details where appropriate.
3. Translate forms, confirmation messages, and other visitor-facing text using the tools that manage them.
4. Review image captions, alternative text, and downloadable documents.
5. Update page titles and any search descriptions you control.
6. Set the site’s default language and test the completed website.

There is no requirement to change every URL simply because you translated the text. If you do change existing addresses, plan redirects so visitors using old links can still reach the right page.

Once the conversion is complete, you maintain one language—not an original version and a set of translations. This is a perfectly reasonable option when you genuinely no longer need the old language.

Option 2: Add translated pages to your existing site

For a small brochure website, you can create a translated version of each important page and link the matching pages together.

This approach gets translated content online without setting up another WordPress installation. It does not, by itself, turn the rest of WordPress into a language-aware system.

Here is a practical example for an English site adding French.

Step 1: Start with a small, complete visitor journey

Choose the pages someone needs to understand your business and contact you. For a service website, that might be Home, Services, About, and Contact.

Translate that journey before tackling an archive of old blog posts. A visitor who can understand your offer but cannot use the contact form has not received a complete experience.

Keep a simple tracking sheet with four columns: original page, translated page, review status, and last checked date.

Step 2: Create the translated pages

In WordPress, go to Pages → Add New, add the translated title and content, and prepare the page with your usual editor.

If you use Elementor, the same principle applies: translate the page content, then review the layout for longer headings, different line breaks, and mobile spacing.

Choose clear page addresses. For example, your English Services page might use /services/, while its French counterpart uses /services-fr/.

You can also organize ordinary WordPress Pages beneath a parent page with a slug such as fr, producing addresses like /fr/services/. WordPress supports page hierarchy and editable slugs through its page settings. This organizes Pages; it does not automatically create language-specific blog archives, products, or search results. WordPress page settings

Step 3: Connect matching pages

On the English Services page, add a clearly labeled Français link to the French Services page. On the French page, add an English link back.

You can start with ordinary text links or buttons within the page. Keep the links in a consistent, easy-to-find position.

The useful detail is the destination: switching languages on a service page should take the visitor to that same service, not make them search again from the homepage.

If a translation is not available, make that clear instead of linking to an unrelated page.

Step 4: Check navigation and shared sections

This is where a simple page translation can become a larger job.

A translated page may still use the same header, footer, and navigation as the English site. Editing a shared menu can affect every page that uses it.

The WordPress Navigation block lets you add and edit navigation links. However, adding a French menu does not automatically make WordPress choose it for French pages. That behavior depends on your theme, template configuration, or additional development. WordPress Navigation block documentation

If your theme supports suitable templates, you may be able to assign a separate navigation layout to the translated pages. Otherwise, decide whether page-level links are sufficient or whether you need technical help.

Step 5: Test beyond the page text

Open the French version as a visitor and follow the whole journey:

• Can you move between the translated pages without being sent back to English?
• Does the mobile menu behave as expected?
• Are form labels, errors, and confirmation messages understandable?
• Does the language link lead to the equivalent page?
• Are shared banners and footer links appropriate?

Also check that the page’s language declaration matches its content. This helps screen readers use the correct pronunciation rules. A French URL alone does not configure it; a developer may need to handle this for a mixed-language site. W3C guidance on page language

Best fit: a limited set of pages, few languages, and infrequent updates. Treat this as a manually maintained setup, not a complete multilingual system.

Option 3: Maintain a separate site for each language

Separate sites can make sense when each audience needs genuinely different content. A French regional team may have its own services, promotions, and publishing schedule.

You can use separate WordPress installations, or WordPress Multisite, which runs a network of sites from a shared installation. Multisite can share themes and plugins while keeping site content separate. Setting it up changes your installation and requires planning and backups; ask your host or developer to follow the official setup guidance. WordPress Multisite setup guide

The publishing process then looks like this:

1. Prepare the language site and its navigation.
2. Add and review its content.
3. Link equivalent pages between the sites.
4. Assign responsibility for updates on each site.

Multisite does not translate your content or connect corresponding pages automatically. It provides the network; you still manage the language relationships.

This can be a sensible structure for independent regional operations. For one small business that wants the same website in two languages, it may introduce more administration than necessary.

Option 4: Commission a custom multilingual solution

A developer can build language selection, translation fields, navigation rules, and search behavior around your website’s particular requirements.

That is a legitimate option for a custom application or an organization with a development team. For a beginner looking to avoid another subscription, it is rarely a small DIY task.

The work also continues after launch. Someone must test new content types, theme changes, forms, and any integrations the site depends on.

If you choose this route, ask for a demonstration of the editing experience—not just the finished website. You should be able to see which translations are missing, what needs review, and how to publish an update safely.

Avoiding an off-the-shelf plugin does not remove the need for software maintenance. It changes who is responsible for it.

What about Google Translate or browser translation?

Browsers such as Chrome can translate pages for individual visitors. That can be helpful when someone arrives at a website in a language they do not read. Chrome translation help

However, this happens in the visitor’s browsing experience. It does not create a French page in your WordPress dashboard that you can review, publish, and maintain.

Use browser translation as a convenience, not as a substitute for your own multilingual publishing strategy. You cannot rely on every visitor to enable it, and you do not control every wording choice they see.

Using an external translation tool to prepare a draft is different: you can review that draft and publish it yourself using one of the manual methods above.

Can a no-plugin multilingual site appear in search results?

Yes. A translation plugin is not a prerequisite for translated pages to appear in Google.

Google recommends distinct URLs for each language version, clear language-specific content and navigation, and links that let visitors choose another language. It also recommends hreflang annotations to identify corresponding language versions. Relying only on browser settings or automatic language redirection can make versions harder to discover. Google’s multilingual website guidance

For your manual setup, check that:

• Each translated page has a working, publicly accessible URL.
• Its main content and navigation use the intended language.
• Page titles and search descriptions match the translated content.
• Language links connect the appropriate pages.
• Technical language annotations are implemented and maintained correctly.

You do not need to learn every technical detail to commission this work. But publishing translated paragraphs is not the same as completing the SEO setup, and no setup guarantees rankings.

The ongoing work: keeping every language accurate

Imagine you add a French version of your Services page. Everything looks good on launch day.

Two months later, you change the service package, revise the delivery time, and add a new enquiry button to the English page.

The French translation is still readable. The problem is that it now describes an offer you no longer provide.

This is the maintenance question to answer before choosing your approach: how will you notice that another language needs updating?

For a small site, a tracking sheet and a publishing checklist may be enough. Whenever you change a page, review its other language versions before marking the work complete.

For a growing website, the task extends beyond page paragraphs. Menus, forms, downloadable documents, promotional banners, and product information can all change independently.

A WooCommerce store adds another consideration: translating product descriptions does not automatically deliver a multilingual cart, checkout, or customer email experience. Test the complete purchase journey and confirm what your chosen setup supports.

There is no universal page count at which manual management stops working. Update frequency, number of languages, and team responsibility matter just as much.

When a translation workspace becomes useful

Manual management can remain a good fit for a small, stable website. If you are spending more time tracking translation work than reviewing the translations themselves, a dedicated workflow is worth considering.

LingoWP is one option. It brings translation work into a central WordPress workspace, where you can work manually, review translations, and identify supported content that needs attention after a source update.

AI translation is optional: the workflow can include manual translation, hosted AI, or your own supported provider key. If you use your own key, provider usage charges may still apply.

The practical benefit is visibility. Instead of remembering which language pages you checked, you have a place to organize the work and review what remains.

LingoWP is still a plugin, so it is not a no-plugin method. It is an alternative for readers whose priority is easier ongoing management. You can explore the workflow on the LingoWP website and check current compatibility for your site before choosing it.

Frequently asked questions

Can I translate a WordPress website without a plugin for free?

You can manually translate and publish content using WordPress’s existing editing tools without buying a multilingual plugin. Translation services, extra hosting, or development help may still cost money. Your own time is also part of the decision.

Can I add a WordPress language switcher without a plugin?

Yes. You can add links between language versions using text, buttons, or navigation links. A basic link list does not translate content or automatically select the equivalent page. You must maintain those relationships yourself.

Does changing Site Language translate my pages?

No. It changes the default WordPress language, not the content you wrote. Your pages, posts, and custom visitor-facing text still need translation.

Do I need WordPress Multisite for a bilingual website?

No. A small site can publish and connect translated pages within one installation. Multisite is an option when maintaining separate sites suits your organization; it is not a requirement for offering two languages.

Can I translate an Elementor website manually?

Yes. You can create translated pages with Elementor and link them together. Review shared templates, navigation, forms, and mobile layouts separately. Adding translated text does not automatically configure those parts for each language.

Choose the setup you can keep up to date

If you are replacing one language with another, translate the existing site and review it carefully. If you only need a handful of bilingual pages, manually connected translations may be enough. If your regional websites operate independently, separate sites can be appropriate.

When updates become frequent, choose a workflow that makes translation status easy to see and maintain.

The goal is not simply to publish another language once. It is to give visitors accurate information in that language every time they return.