The English page is ready, but the contact button still sends visitors to the Persian form. Installing a plugin isn't enough to make WordPress multilingual. You also have to connect equivalent pages, menus, forms and URLs. Start on a test copy. Before going live, walk through the full user journey in both languages.
What should you check before making WordPress multilingual?
Start by pinning down three things: the site's components, your technical access and the scope of translation. The first question I usually ask is this: what exactly does an English-speaking visitor need to do without running into Persian text? The answer shows you the real size of the job.
Throughout this guide we'll use a hypothetical company site. It has a home page, a services page, a contact page, a few blog posts and a consultation request form. The goal is to add English to WordPress. We're leaving out the shop, payments and memberships, because each of those needs its own testing path.
Record the name and version of your theme, page builder, form builder and active plugins.
List pages, posts, categories and custom content types, such as portfolio items.
Check your access to the WordPress admin, hosting, files and database.
Identify forms, automated messages and connections to external systems.
Decide who is responsible for translating, approving content and maintaining the English version.
Keep three concepts separate. Admin language is the language of the dashboard tools. Content language is the language of the page the visitor reads. Text direction decides whether the layout runs right-to-left or left-to-right.
So switching the dashboard to English doesn't create an English page. Changing text direction doesn't necessarily fix column order or icon placement either. Define the translation scope by the user journey, not just by page count.
How do you make WordPress bilingual?
Take a backup first and build a test environment. Then install a language management plugin, set your primary and secondary languages and link each page to its translation. Configure menus, forms and URLs. Before going live, test language switching and the mobile view.
Before you start, write down acceptance criteria. In our example, a visitor should be able to go from the English home page to services and then to the English form. The success message and the confirmation email should stay in the same language too.
Managing languages is not the same thing as translating text. The plugin records which English page is the equivalent of which Persian page. Don't assume it produces translations for you. English copy has to be written and reviewed on its own.
First, prepare a safe environment and set the language of existing content.
Then build one Persian–English page pair.
Next, move on to shared components like menus and forms.
Once that sample passes testing, repeat the same approach for the remaining pages.
That's why this WordPress multilingual tutorial doesn't start by translating every page. One complete sample exposes the flaws in your method sooner than dozens of half-finished translations.
Taking a backup and building a test environment
Your backup has to cover both the database and the files. The database holds your content and many of your settings. The files include images, themes, plugins and file-based configuration.
Having a backup file doesn't prove you can restore it. Keep one copy outside your main hosting account. Then test the restore on a separate copy, never on the live site.
A test environment, often called staging, is a copy kept apart from the main site where you make your changes. Protect it with a password or an access restriction. In WordPress's Reading settings, also turn on the option that discourages indexing. That option asks search engines not to add the pages to their index.
That request doesn't replace access protection. A test copy may also still send real emails or pass data to another system. Rein in external connections before your first test.
Route outgoing email to an inbox you control.
Disable payments, SMS and automatic data transfers to external systems.
After restoring, open the admin login, the home page and a few images.
Record when the backup was taken, where it's stored and who is responsible for restoring it.
If you're choosing a tool, the article good plugins for site backup and security helps you work through your backup requirements. When you make WordPress multilingual, a backup is only useful if you know how to restore it.
Recording versions and preparing the plugin installation
This guide makes WordPress multilingual with Polylang. We picked it to keep the steps consistent, not to rank it above other tools. Before installing, check that it works with your site's components.
To be clear, this text isn't a report from a real test run, and it doesn't claim to cover a tested version. The steps below are general guidance. Exact option names can differ depending on the version and the dashboard language. Only record a step as successful after you've run it yourself.
Create an environment record. Note the versions of WordPress, Polylang, your theme and your form builder, along with the test date. For each feature, also note its dependency and a link to the relevant documentation.
Required feature | Check before you start |
|---|---|
Pages and categories in both languages | Support in the installed version and how translations are linked |
Menu and language switcher | Compatibility with your theme type and navigation location |
English form | A standalone form or a compatible integration with your form builder |
Image information | Media settings and how language-specific information is kept separate |
Compare the official language settings documentation with the version you've installed. Don't assume that what's written for the current version also applies to an older one.
If you want to make WordPress multilingual for free, first check what the free version offers for pages, categories and menus. Don't assume your form builder or custom theme will work with it at no extra cost. Translating and maintaining content still takes time and resources. Take screenshots of the steps only from your own actual run.
Installing the plugin and setting the default language
In the test environment, go to Plugins, then Add New Plugin. Search for Polylang in the official repository and check the plugin details. After installing and activating it, open the Languages section or the setup wizard.
Add Persian for the existing content and English as the second language. Make Persian the default. The default language is the baseline for the site's language settings. It is not the browser language or the language of your admin account.
Before you assign Persian to all your older content in bulk, open a few examples. The site may already contain an English page or imported content. Assigning one language to everything hides that difference.
Check one old page, one post and one category.
Find content with no language assigned and give it the correct one.
Set the language of existing categories and tags as well.
In the editor for a sample page, find the option to add an English translation.
Then check the public Persian and English views. Persian should run right-to-left and English left-to-right. Check icon placement, button spacing and column order one at a time. Choosing a language doesn't guarantee your theme handles it properly.
This stage of making WordPress multilingual is done when two things are true. The language of all existing content is known, and you can create a linked translation. Take screenshots of the real settings and the sample page. If either condition isn't met, don't move on to bulk translation yet.
Setting URLs and linking equivalent pages
Choose your URL pattern before you create lots of translations. For our hypothetical site, we keep the Persian URLs as they are and put English under the /en/ path. First check that your installed setup supports this pattern.
For example, the Persian page could stay at /services/ and the English translation could sit at /en/services/. These are only examples, not instructions to change your current URLs. Set the language URL options so Persian paths don't change unless they have to.
On a live site, start by listing the existing URLs. If a URL changes, it needs a permanent redirect, also called a 301 redirect. A 301 sends visitors and search engines from the old address to the new one.
Two pages aren't linked just because their titles are similar. In the page's language and translation panel, select the English equivalent or create it from there. Then check the link from both sides.
The second version of a site is complete when visitors never need the first language to keep going.
Check the page output for hreflang as well. This tag tells search engines which language versions are equivalents. The canonical tag marks a page's main or preferred URL. The English version shouldn't name the Persian page as its canonical without good reason.
When you review the work, rely on the actual page output, not just on settings being switched on. Every declared URL should load and point to the right equivalent. For details, see Google's guide to telling it about localized versions.
Translating pages, posts and categories
Open the Persian services page and use the add-translation control to create a linked English version. If an English page already exists, select it as the equivalent instead. Creating it again leads to duplicate content and confusion.
Enter the English title and body. Also review the slug, which is the readable part of the page URL. If your theme displays excerpts, translate them separately. The title and description that appear in search results need review too.
Save the page and open its public view.
Link the contact button to the English contact page.
In the language settings, check the relationship between the Persian and English pages.
Record the URL and publication status of both versions.
For a sample post, first create the English category and link it to its Persian equivalent. Then assign the English category to the translated post. Open the category archive page as well, which lists every post in that category.
The home page and the posts page each need their own check. Make sure WordPress's Reading settings match how those pages are linked as translations. Each language's main URL should show the correct home page, not some unrelated default page.
In the page builder, check buttons and shared sections one by one. Copying a layout can bring Persian links and text along with it. Take real screenshots of both the editor and the public view of that page. Together they show whether the settings produce the right output.
Translating menus, forms, messages and image information
To translate a WordPress menu, build a separate menu for each language and assign it to that language's location. In classic themes, you'll usually find this under Appearance, then Menus. Location names depend on your theme.
A block theme, on the other hand, may handle navigation in the Site Editor. In that case, check where the menu actually lives and whether the language switcher works with it. An English menu in the dashboard isn't enough. Open the public header and footer to confirm.
An English form is more than a set of translated labels. How you build it depends on your form builder. You can create a standalone English form or translate the existing one through a compatible integration. If you build a separate form, every later change has to be made in both forms.
Translate field labels, help text and dropdown options.
Check the error messages for an empty field and an invalid email address.
Set the success message and the page visitors land on after submitting.
Review the subject and body of the confirmation email.
Confirm the submission arrives in the inbox or destination system.
Make a separate list of your theme's short texts and widgets. Some text lives in theme settings, and some in the page builder or the string translations section. A string is a short piece of interface text, like “Search”. Not all of these can be translated from the same screen.
For images, write alt text in the language of the page. Alt text describes the image for accessibility tools such as screen readers. Check the media title and visible caption too. How media information is split by language depends on your settings and installed version.
So when you make WordPress multilingual, write down how media is actually handled. Don't guess. Take screenshots of the English menu and form using dummy data. Keep in mind that a success message doesn't prove the email was delivered.
Setting up language switching and untranslated pages
Put the language switcher somewhere visitors can find it on mobile too. Show each language's name, such as “فارسی” and “English”. Don't rely on flags alone, because a language and a country aren't always the same thing.
For example, switching language on the Persian services page should open the English services page. If visitors land on the home page instead, check the translation link or the switcher settings. Test the round trip at least once, there and back.
Decide in advance what happens on a page with no translation. One option is to hide the switcher link for the missing language. Another is to send visitors somewhere else and explain why, which may take extra configuration or development.
Document how your chosen approach actually behaves. Showing a Persian page under an English URL without telling the visitor is not an acceptable fix. It's better to make a missing translation obvious than to let the switcher promise something that isn't there.
If browser language detection is on, test both arriving directly and choosing a language manually. A visitor who picks a language shouldn't get stuck in a loop of automatic switching. My advice is to leave automatic redirection off until the basic tests pass.
A cache stores a saved copy of each page so it loads faster. After you make WordPress multilingual, make sure the cache isn't serving one language's version to visitors of the other. To review layout and switcher accessibility, see also multilingual website design tips.
Testing mobile, forms and URLs in each language
Start testing with a real user journey: home, services, contact and form submission. Then open each page by typing its URL directly. Clicking around in the admin preview doesn't show what an ordinary visitor experiences.
The table below is a test template, not a success report. In your handover file, add columns for the result, the evidence and who is responsible for fixing each issue. Only mark a test as passed or failed after you've run it.
Area | Test method | Acceptance criteria |
|---|---|---|
Pages and home | Open both languages directly | Content and home page match the language |
Menu and switcher | Switch from the services page in both directions | Lands on the equivalent page |
Form | Submit an incomplete form, then a valid one | Correct messages and delivery to a controlled destination |
URLs | Check old paths and the English version | No page errors or irrelevant redirects |
Mobile | Open the menu and complete the form | Readable and usable with nothing overflowing the screen |
Cache | Repeat visits while logged out | The correct language persists on later visits |
On mobile, check long English headings, the dropdown menu and where the switcher sits. Check the text direction of the email and phone fields too. Then tab through links and fields with the keyboard. You should always be able to see which element is selected.
Next, repeat the tests logged out of the admin, with caching turned on. Submit the form with dummy data and confirm it arrives at the controlled destination. Don't publish emails, test data or screenshots that contain personal information.
Signing off the work has to rest on evidence. For each issue, record the page URL, a screenshot of the error and the steps to reproduce it. “It worked on my machine” isn't good enough for handover.
Controlled release and rolling back from errors
Before going live, take a fresh backup and compare the main site with the test environment. New posts or form submissions may have come in on the live site while you were testing. That data mustn't be lost when you move your changes over.
Don't overwrite the live database with the test database. Doing so can wipe out new submissions or content edits. Plan how you'll move settings and translations across while keeping the new data safe.
After going live, clear the cache and retest the main paths in both languages. Make sure the test environment's access restriction or indexing block hasn't carried over to the main site. Meanwhile, the test environment itself should stay protected.
If the main form breaks, stop the release.
Widespread URL errors or an unreachable Persian site mean you need to roll back.
Record when the error happened, the last change made and the visible symptoms.
Before restoring, save any new data that arrived after going live.
The way back is part of the change, not something to figure out after things break.
Deactivating the plugin isn't a full rollback. URLs, settings and translation data may stay in place or start behaving differently. Restore from a backup whose restore process you've already tested.
For planning the migration and handover, the article adding a language to your site: execution steps and a reliable handover covers the details this guide leaves out. When you make WordPress multilingual, testing doesn't stop at launch. The production site needs its own independent check.
When should you hand the work to a design team?
If the user journey involves payments, user accounts, external integrations or a custom theme, get a technical assessment before you start. Page count alone is a poor guide. A single form connected to a sales system can be more complex than many content pages.
If your current URLs bring in search traffic, take extra care when changing the site structure. Ask the team how the old URLs will be preserved and who will sign off on post-launch testing.
For handover, put together a short package. It should list the languages, the pages, the version of each component and the sections that are still untranslated. Add the failed tests with their URLs and error screenshots. Keep passwords out of this file and hand over access through a secure channel.
Make responsibilities after launch clear as well. Who tells the translator when the Persian copy changes? Set a consistent policy for posts that don't have translations. Name who approves content and who reviews the forms on a regular schedule.
If the technical scope still isn't clear, Niasa's multilingual website design services page can help you work out what the project needs to cover.
Your next step is to list your pages and the paths where errors would cost you most. Start with the services page and trace its journey all the way to a received request. Then build one complete page pair in the test environment and use what you learn to plan the rest.
فهرست صفحات و مسیرهای حساس سایت را آماده کنید تا درباره اجرای زبان دوم با تیم نیاسا گفتوگو کنیم.
Frequently asked
4Can you make WordPress multilingual for free?
For a simple site, you can take a route that doesn't require buying a license, as long as the features you need exist in the version you install. You still need time for translation, quality control and maintenance, and complex integrations should be checked separately.
Does adding English to WordPress translate the text automatically?
Defining a second language isn't the same as translating text. Even if your chosen setup offers machine translation, technical terms, buttons and form messages still need human review.
Do we need to translate every page at once?
No. You can start with one complete journey, such as a service page through to the contact form. What matters is deciding what happens on untranslated pages and how the language switcher behaves.
Why does the English menu still have Persian links?
The right menu may not be assigned to the second language's location, or a custom link may still point to the Persian URL. First check where each item actually goes, then test the display again with the cache cleared.





