Running a real estate website that serves international clients means you’ll need solid translation capabilities. WPResidence was built with this in mind, offering multiple paths to get your property listings, agent profiles, and custom content speaking your visitors’ languages.
Let me walk you through everything you need to know about translating this theme, from the basics to advanced multilingual setups.
What’s Already Built In
WPResidence ships with translation files ready to go. The theme includes .po and .mo files stored in the main languages folder for several languages. If you’re using WPResidence Core, the companion plugin, it also has separate translation files.
Here’s something important: always set up a child theme before you start translating. When the parent theme updates, it can remove any custom translations you’ve added directly. A child theme keeps your work safe, with translations stored in wpresidence-child/languages where updates can’t touch them.
The theme also supports RTL languages out of the box. If you work with Arabic, Hebrew, or similar right-to-left languages, the layout flips correctly without extra configuration.
Getting Started with Loco Translate
For basic translation work, Loco Translate is a free plugin that gives you a clean interface for editing translation files directly in WordPress.
The workflow is straightforward:
- Navigate to Loco Translate in your WordPress dashboard.
- Select Themes, then WPResidence. For WPResidence Core, select Plugins and then wpresidence-core.
- Create a new language or edit an existing one.
- Translate the strings you need.
- Save your work.
Always back up your translation files before running theme updates. While child themes protect most customizations, it is better to be safe.
The Manual Translation Catch
Not everything lives in .po files, which can confuse many users.
Property detail labels, advanced search labels, and taxonomy terms such as property types, cities, areas, features, amenities, and status options need manual translation through the Theme Options panel. Standard translation tools may not recognize these strings.
When you’re translating categories, leave the slug field blank. WordPress will generate the slug automatically based on your translated title. This keeps the search functionality working across languages. If you set custom slugs that do not match correctly between languages, you can break the search filters.
WPML: The Full-Featured Option
WPML is officially supported and gives you complete translation control. It is a paid plugin, but it handles many WPResidence translation needs.
What WPML can translate:
- Pages and posts
- Property listings and custom post types
- Agent and agency profiles
- User dashboard elements
- Custom fields
The Translation Management module lets you select which properties need translation. You can translate manually or use AI-assisted automatic translation if you have credits.
String Translation Setup
Some theme elements do not exist as standard posts. Header text, footer content, and button labels may need the String Translation module. Go to WPML > String Translation and add translations for strings that did not convert automatically.
WPResidence includes special registration code so WPML can detect custom field labels and other theme-specific elements. Still, you may need to configure custom fields manually. Go to WPML > Settings > Custom Fields and mark each field as translate. Then open a property in your second language so WPML registers the strings and translates them through String Translation.
Configuration Tweaks
A few settings make WPML work better with WPResidence:
Set Read from file to No in WPML settings, so translations come from the database instead. Change Pin Management to Single pin or price pins to avoid duplicate map markers. Disable Adjust IDs for multilingual functionality and make sure category slugs and titles match correctly across languages, or your search may break.
If some strings still do not translate, enable Store a language cookie to support language filtering for AJAX in the WPML settings.
Multilingual SEO with WPML
When you pair WPML with Yoast SEO or Rank Math, you can manage multilingual sitemaps and hreflang links. The SEO add-on included in WPML’s Multilingual CMS package helps handle translated meta titles and descriptions.
Polylang: The Lighter Alternative
WPResidence works with Polylang, though the documentation is not as detailed as WPML’s. The theme uses standard WordPress translation functions, so Polylang can hook into them.
Polylang adds minimal database queries, even with multiple languages active. It uses core WordPress taxonomies instead of its own system, which can improve performance. You manually assign a language to each post and translate categories and menus.
The tradeoff is that the workflow is more manual. You duplicate posts, translate content, and manage custom fields yourself. Theme translation files can be imported through Polylang’s String Translation module.
Test thoroughly before going live, especially if your site uses many custom fields, property filters, and Elementor templates.
Weglot: Automatic Translation Made Easy
Weglot offers a different approach. It is cloud-based and automatically translates content with minimal setup. WPResidence documentation recommends it alongside WPML.
Translations do not live in .po files. They are stored on Weglot’s servers. This makes setup fast, but it also means your translations depend on their service.
Payment Page Exclusions
Stripe and PayPal require unique pages that must not be translated. You need to exclude payment processor pages using Weglot’s Exclude URL feature. If you miss this step, you may have payment processing issues.
Weglot generates separate URLs for each language, such as /fr/ for French, adds hreflang tags automatically, and integrates with SEO plugins for multilingual sitemaps. It is a fast path to a multilingual site, but it requires a subscription.
TranslatePress: Visual Front-End Editing
TranslatePress provides a visual editor that lets you translate content directly on the front end. You can see how translations look in real time.
The plugin handles text from shortcodes and forms, works with WooCommerce, and offers a freemium model. The Business tier adds SEO features that are usually needed for a serious multilingual site.
Recent Improvements and Issues
WPResidence version 5.3.0 added a menu caching fix specifically for TranslatePress. Another update addressed active menu color when language switchers were used. The developers are working on compatibility.
Some users have reported conflicts when running TranslatePress with WPResidence Core and Elementor. If you use this setup, test carefully with your exact plugin list and versions before going live.
Theme Strings vs User Content
Understanding what needs translation, and where it is translated, saves a lot of frustration.
Theme interface strings, such as buttons, labels, headers, and footers, live in translation files. Handle these with Loco Translate or the String Translation modules in WPML or Polylang. If you rename theme words, update both the WPResidence theme file and the WPResidence Core plugin file.
User-generated content, such as properties, agents, agencies, blog posts, and custom fields, is WordPress content. WPML’s Translation Dashboard manages these. With Polylang and TranslatePress, you translate posts individually. Weglot handles them automatically.
Backend labels from Theme Options, such as property labels and custom field names, are not always in .po files. You translate these directly in the theme settings.
The front end, user dashboard, submission forms, and favorite list are translated through standard WordPress functions, so WPML and Polylang can detect many of them. Some strings may still need manual translation through the String Translation modules.
SEO for Multilingual Sites
Getting search engines to index your translated content properly requires attention to technical details.
WPResidence can work with multilingual hreflang tags and sitemaps when you use WPML or Weglot together with Yoast SEO or Rank Math. Weglot generates separate URLs for each language and updates metadata automatically.
With manual translation through WPML or Polylang, you get more control over SEO keywords, translated categories, and translated slugs. This matters because poor slug management can affect both search functionality and SEO.
TranslatePress requires the Business plan to access SEO pack features for translating meta titles and descriptions.
Step-by-Step Translation Workflow
Here is how to set up a multilingual WPResidence site properly:
1. Install a child theme
Create and activate a child theme before anything else. This protects your customizations during updates.
2. Choose your translation approach
If you need automatic translation with minimal setup, Weglot is an option. If you want manual control and better SEO customization, WPML or Polylang may be better choices.
3. Translate theme strings
Install Loco Translate, select WPResidence and wpresidence-core, and translate interface strings. This handles buttons, labels, and standard theme text.
4. Configure your translation plugin
For WPML, install the core and String Translation modules. Set custom fields to translate. Disable Adjust IDs for multilingual functionality. Translate categories with matching titles and slugs across languages.
For Polylang, create languages and assign them to posts and listings. Import translations from .po files for theme strings. Manually translate custom fields and categories.
For Weglot, sign up, connect your API key, and select languages. Exclude payment processor pages immediately.
For TranslatePress, install the plugin, select languages, and use the front-end editor. Test thoroughly with your specific setup.
5. Handle user content
Translate properties, agents, custom fields, and categories through your chosen plugin. Do not forget SEO metadata, such as titles, descriptions, and keywords.
6. Test everything
Check your sitemap in your SEO plugin. Verify hreflang tags are present. Test that search filters work in all languages. Inspect canonical URLs and confirm translated pages index correctly.
Common Issues and Solutions
WPML not translating some strings?
Make sure custom fields are marked as translate in WPML Settings. Open a property in the second language to register strings. Enable the language cookie setting for AJAX filtering.
Search breaking after translation?
Check that category slugs match correctly across languages. Verify that Adjust IDs for multilingual functionality is disabled. Confirm that you left slug fields blank when translating categories, so WordPress generated them automatically.
Payment processing fails?
With Weglot, use the Exclude URL feature to exclude Stripe and PayPal pages from translation. These processors need consistent, untranslated URLs.
TranslatePress conflicts?
Test with only WPResidence and TranslatePress active. If it works, add other plugins individually to identify the conflict.
Missing translations in Theme Options?
Property labels, search labels, and category names may need manual translation in Theme Options. They are not always stored in .po files and may not translate automatically.
Making the Right Choice
WPML offers the most complete integration with WPResidence. It handles custom field translation, string management, multilingual sitemaps, and advanced translation workflows. The cost and complexity may be worth it for professional multilingual real estate websites.
Polylang works well if you are comfortable with manual translation and want to avoid subscription costs. Just be aware that you will manage more of the work yourself, and documentation is thinner.
Weglot gets you multilingual fast with automatic translation. It is useful for quick launches or when you want the fastest setup. Remember to exclude payment pages and know that your translations depend on their service.
TranslatePress offers visual front-end editing, but compatibility should be tested carefully depending on your plugins and setup.
Whatever route you choose, use a child theme, translate all labels and taxonomies manually where needed, configure your chosen plugin correctly, and test your multilingual SEO before launch. The groundwork pays off when international clients can browse your properties in their native language without issues.
FAQ
What translation support is built into WPResidence, and where should I store custom translations?
WPResidence ships with ready-made translation files, .po and .mo, in its main languages folder. WPResidence Core also has its own separate translation files.
Before you translate anything, set up and activate a child theme. If you edit translations in the parent theme, a theme update can remove your changes. With a child theme, you can store your custom language files in wpresidence-child/languages so updates cannot overwrite them.
WPResidence also supports RTL languages out of the box, so layouts flip correctly for languages like Arabic or Hebrew without extra configuration.
How do I translate WPResidence with Loco Translate for basic interface strings?
Loco Translate is a practical option for basic theme and plugin string translation because it lets you edit translation files from inside the WordPress admin.
In your dashboard, go to Loco Translate, choose Themes and select WPResidence. For WPResidence Core, choose Plugins and select wpresidence-core. Then create a new language, or edit an existing one, translate the strings you need, and save.
Even though a child theme protects most customizations, you should still back up your translation files before running theme updates.
Why aren’t some property labels and taxonomy terms translating, and how do I fix it?
In WPResidence, not everything is stored in standard .po files. Property detail labels, advanced search labels, and taxonomy terms, such as property types, cities, areas, features, amenities, and status options, may require manual translation inside the Theme Options panel.
When translating categories, leave the slug field blank so WordPress generates the slug automatically from the translated title. If you set custom slugs that do not match correctly between languages, you can break search filters and multilingual search behavior.
How do I configure WPML correctly with WPResidence, especially for custom fields and strings?
WPML is officially supported with WPResidence and can translate pages, posts, property listings, agent and agency profiles, user dashboard elements, and custom fields.
For theme elements that are not standard posts, such as header text, footer content, and button labels, use WPML’s String Translation module under WPML > String Translation.
For custom fields, go to WPML > Settings > Custom Fields and mark each relevant field as translate. Then open a property in your second language so WPML registers the strings, and translate them through String Translation.
WPResidence-specific settings include setting Read from file to No, using Single pin or price pins to avoid duplicate map markers, disabling Adjust IDs for multilingual functionality, and keeping category slugs and titles consistent across languages. If AJAX-filtered strings still fail to translate, enable the setting to store a language cookie for AJAX language filtering.
If I use Weglot on a WPResidence site, what should I exclude from translation to avoid payment issues?
With Weglot, you must exclude Stripe and PayPal payment processor pages from translation. These processors require unique pages that should not be translated, and translating them can cause payment processing issues.
Use Weglot’s Exclude URL feature to prevent those payment-related URLs from being translated.
Weglot translations are stored on Weglot’s servers, not in .po files. Weglot also generates separate language URLs, such as /fr/ for French, and adds hreflang tags automatically.
