If you run a real estate or rental listing site on WPResidence or WPRentals, you may eventually need a multilingual setup. If you have already tried this with a generic translation plugin, you probably know the usual problem: the pages look translated, but property search, filters, custom fields, or structured listing data can stop working correctly.
That is why we built WPEstate Translate, a multilanguage plugin designed specifically around how WPResidence and WPRentals store and display property data.
This article explains what the plugin does, how it is different from a generic multilingual setup, and the configuration step that prevents the most common translation issues on real estate websites.
The actual problem with translating listing sites
Most multilingual plugins were originally built for blogs, pages, and standard website content. They translate posts, pages, menus, and widgets. That works well when your content is mostly text.
Real estate listings are different. A property has a title and description, but it also has a price, bedrooms, bathrooms, GPS coordinates, property ID, status, taxonomies, and custom fields used by the theme search system.
If a generic translation plugin treats those structured values like normal text, the translated listing may look correct on the surface, but the search filters, sorting, maps, and display logic may not work as expected.
For example, a translated property page may read correctly in Spanish or French, but filtering by price, bedrooms, or location may return wrong or empty results. This is the problem WPEstate Translate was built to avoid.
What the plugin does
The plugin is available inside your WordPress dashboard under the WPEstate Translate menu. It includes a Start Here page that shows the recommended setup order.
The order matters because translating listings before configuring taxonomy behavior and custom field rules can create issues that are harder to fix later.
1. Languages come first
First, you define which languages your site supports, set the default language, and decide which languages are visible.
This controls the URL structure, translation files, menu synchronization, and content translation workflow.
2. Theme and plugin strings come second
These are the small interface texts visitors see across the site: buttons, search placeholders, filter labels, form text, dashboard labels, and other theme/plugin strings.
The plugin scans the active theme and plugins, collects strings, and allows you to translate them per language. It then generates translation files so WordPress can load them correctly.
If you skip this step, you may end up with translated listings but untranslated interface text, such as search buttons or filter names still showing in the default language.
3. Taxonomy translation comes third
Property categories, statuses, types, cities, areas, and features are taxonomies. Many of them are also used in search filters.
The plugin lets you choose how each taxonomy should behave per language. You can translate terms per language, translate them and hide missing terms, or share terms across all languages.
The practical rule is simple: if a taxonomy appears in a search filter, translate it and hide missing terms. Otherwise, visitors may see filter options in another language that lead to no results.
4. Custom field rules come fourth
This is one of the most important steps.
The plugin shows the custom fields attached to your listings and lets you decide how each field should behave across translations.
Some fields should copy exactly across all languages, such as price, bedroom count, bathroom count, property ID, latitude, longitude, and other numeric or reference fields. These are not text fields. They are structured data used by the theme for search, maps, and display.
Other fields may need to be translated or edited per language, such as descriptions, custom headlines, or marketing text.
If structured fields are translated instead of copied, your translated listings may look correct visually, but the data behind them may no longer match what the theme expects.
5. Automatic translation comes fifth
After languages, strings, taxonomies, and custom field rules are configured, you can run automatic translation.
You choose the translation engine, add the API key, select the target languages and post types, and run the translation job.
The plugin creates translated drafts based on the rules already configured. The result should still be reviewed, but the structure is safer because the important property data is handled correctly.
6. Menu synchronization comes sixth
The plugin can copy a source menu structure to a target-language menu and map menu items to their translated versions.
If a translation does not exist yet, you can set a fallback so the menu does not create broken links.
7. Global settings come last
Finally, configure the global settings, including URL strategy, default language, and language switcher placement.
After changing URL settings, always flush your permalinks from Settings > Permalinks.
The one rule that prevents silent failures
If your translated listings look fine but search filters behave incorrectly, the cause is often the same: structured fields were treated like translatable text.
Before running a bulk translation, go to Custom Field Rules and make sure fields like price, property ID, coordinates, bedrooms, bathrooms, and other numeric/reference values are set to copy, not translate.
Translate the text that humans read. Copy the structured data that the theme uses for search, sorting, maps, and display.
That distinction is what separates a translated content site from a multilingual real estate site that still works correctly.
How to get it
WPEstate Translate is built specifically for WPResidence and WPRentals.
If you want to test it on your site, please contact us through the WPEstate support system or our Facebook page and request access.
The fastest way for us to improve the plugin is through real usage on real websites with real listings. If you test it, please share what is not clear, what does not work as expected, and what features would help your workflow.
How to test it
1. Download and install the plugin.
2. If your theme version is 5.4.1 or older, download the required wpr folder and upload it into the themes/wpresidence/ folder.
3. The child theme already includes many translation files. You can activate the child theme and the plugin will read the translation files already available there. Alternatively, you can copy only your language files into the wpresidence/languages folder.
4. Please send us feedback. Tell us what is not clear, what is not working well, and what you like. We will collect this feedback, fix reported bugs, and review suggestions for new features and improvements.
FAQ
What problem is the WPResidence/WPRentals multilanguage plugin designed to solve?
It is designed to prevent the common issue where a website looks translated, but the real estate functionality breaks behind the scenes.
Generic multilingual plugins may treat structured listing data, such as price, bedrooms, IDs, coordinates, and taxonomy filters, as ordinary text. This can affect filtering, sorting, maps, and numeric display.
WPEstate Translate is built around how WPResidence and WPRentals store and query property data, so translations can follow rules that keep listing data and search filters working correctly.
Where do I configure the plugin in WordPress, and what is the recommended setup order?
You configure the plugin from the WPEstate Translate menu in the WordPress dashboard.
The recommended setup order is: define languages, translate theme and plugin strings, configure taxonomy translation behavior, configure custom field rules, run automatic translation, synchronize menus, and then finalize global settings such as URL strategy, default language, and language switcher placement.
This order matters because translating listings before configuring taxonomy and custom field rules can create issues you may need to fix later.
How should I handle taxonomies so search filters work in every language?
Use the taxonomy translation settings to control how property categories, statuses, types, cities, areas, and features behave per language.
If a taxonomy appears in a search filter, the recommended approach is to translate it and hide missing terms. This helps prevent visitors from seeing filter options that return no results in the selected language.
What is the key custom field rule that prevents silent translation failures?
Before running any automatic or bulk translation, set structured fields to copy, not translate.
This includes fields such as price, bedroom count, bathroom count, property ID, latitude, longitude, and other numeric or reference values used by the theme.
Translate human-readable text like descriptions and headlines. Copy the structured data that the theme uses for search, maps, sorting, and display.
How can I get and test the plugin if I use WPResidence or WPRentals?
You can request access through the WPEstate support system or our Facebook page.
After installing the plugin, follow the setup order from the Start Here page. If you are using an older theme version, you may need to add the required compatibility folder as instructed. After changing URL settings, remember to flush permalinks.
