A multilingual real estate website needs WPML, RTL, and multi-currency support. See how WPResidence handles all three, plus its honest limits and costs.
Last updated: July 7, 2026
By Cris Bean
Disclosure: our team builds and sells the WPResidence theme. We think it’s a strong pick for international real estate work, and this article explains why, but you should weigh what follows knowing we make it. Where we cite our own numbers or status, we say so in the text so you can judge them for yourself.
Yes. WPResidence is built to run a multilingual real estate website from a single WordPress install, without bolting a country site onto every language you serve. The codebase is translation-ready out of the box, it ships with ready-made language files, and it has native right-to-left (RTL) support for Arabic and Hebrew.
A built-in multi-currency engine converts prices on the fly, and the theme has tested integration with the major translation plugins: WPML, Polylang, Weglot, and TranslatePress. That combination is what makes it a genuine WPML real estate theme rather than one that only claims translation readiness on a sales page.
One portal can carry several languages and currencies at once, so an agency serving buyers across borders manages listings, agents, and leads in one dashboard instead of a stack of separate installs. The rest of this guide walks through exactly how each piece works, and where it stops.
Yes, and the mechanism matters more than the label. Every front-end string in WPResidence is wrapped in standard WordPress translation functions, so nothing is hard-coded English waiting to trip you up later.
The theme ships with the full set of translation files: a .po file, a .mo file, and a master .pot template that gets refreshed at major releases. That .pot file is the source you edit when you want to change wording, and it covers the whole interface, not just a handful of headline labels.
WPResidence says it bundles over 32 pre-translated language files. Read that number honestly: these are machine-made starting points meant to be refined, not polished human translations. They save you the blank-page problem and get a second language visible fast, but you'll still want a fluent reviewer to fix local slang, legal wording, and anything that reads stiff.
You edit those files two ways. Loco Translate runs right inside the WordPress dashboard, so a non-technical admin can rename labels without leaving the browser. PoEdit works offline for anyone who prefers to translate on the desktop and upload the finished file.
And "every label" really does mean every label. Property, Price, Bedrooms, the search field prompts, buttons, dashboard messages, even error text: all of it is translatable.
WPResidence puts the relabeling job at roughly 10 to 15 minutes for someone who has never touched a translation tool. Using the bundled files, its documentation says a second language can go live often under an hour.
That's the floor. The interesting decisions start when you pick the plugin that manages those languages.
Pick by three things: budget, how much control you want, and how fast you need to launch. WPResidence works with four plugins, and each one wins a different situation.
WPML is the pick for serious portals running three or more languages where SEO carries real weight. WPResidence states it sits on WPML's official recommended-themes list, which means the two were jointly tested on real listings, taxonomies, and search rather than just tagged "WPML-ready."
With WPML, each language gets its own post and its own URL, and you control translation field by field through the WPML Translation Editor. The String Translation addon handles interface labels, and Menu Sync keeps your navigation aligned across languages.
Polylang is the free, manual route. You duplicate each listing and assign it a language yourself. That hands-on approach works fine on smaller sites; WPResidence points to roughly 200 properties as the sensible ceiling before the manual work stops being worth it.
Weglot is cloud machine translation. You paste an API key, choose your languages, and it auto-translates the front end and drops in a switcher. It's the fastest way to get a multilingual site live, and you refine the key pages later.
TranslatePress edits translations visually, inline on the front end, so you see the page as you change it. That suits people who'd rather point at text than work through a back-end list.
Here's the part competitors rarely mention: you're not locked in. A common path is to start on Weglot for speed, then migrate to WPML or Polylang as the content and SEO plans grow. The theme doesn't block the switch, so an early shortcut doesn't become a cage.
The classic failure mode on a multilingual real estate website is search that quietly breaks. You add a language, the slugs drift out of sync, and the advanced filters start returning nothing. WPResidence documents how to avoid exactly that.
Properties, Agents, Agencies, and Developers are all custom post types, and every one of them is translatable, custom fields included. Titles, descriptions, amenities, Floor, Year Built: you mark each as "Translate" in WPML and store a separate value per language.
The real-estate taxonomies matter just as much. Property type, city, area, features, and status are all exposed for translation.
So "Apartment" becomes "Appartement," a city name localizes, and the query still points at the same listings underneath. The visitor sees their language; the search still finds the property.
This is a recurring difference between WPResidence and themes that stop at "translation ready." Marking strings for translation is the easy half. Keeping advanced search and AJAX filters working across translated slugs is the half that breaks sites, and it's the half the theme's documentation actually walks you through.
Front-end submission forms pull their labels from those same translatable strings too, so an agent adding a listing sees the prompts in their own language rather than defaulting back to English.
Yes, and it's native, not a bolt-on. RTL support is baked into the core style set through a dedicated stylesheet that loads automatically the moment WordPress is set to a right-to-left language.
When it kicks in, the whole layout flips. Menus, sidebars, property cards, sliders, search forms, mortgage calculators, user dashboards, icons, and text alignment all mirror correctly. You don't need a child theme, and you don't need to write custom CSS to force the direction.
WPResidence maintains a dedicated RTL demo that shows this in practice: Arabic menus, property grids, advanced search, and the front-end user areas, all running right-to-left. It's worth looking at before you commit, because it shows the theme handling a full Arabic interface rather than a single translated page.
You can also run mixed directions on one install. English and Arabic can live in parallel, and the direction switches with the language the visitor picks, so a bilingual portal doesn't force one script to compromise for the other.
For Gulf markets this pairs naturally with currency. You'd run Arabic alongside SAR, AED, or QAR pricing with a geolocation default, which is a good moment to look at how the currency engine actually works.
The multi-currency engine is a built-in core feature. No WooCommerce, no separate plugin, no add-on to license. It stores one base price per property and converts it on the fly for display.
That single design decision does a lot of quiet work. Because each listing holds one base price rather than a separate field for every currency, search and sort stay fast, and you never maintain parallel price entries that drift apart over time. The visitor sees their currency; the database sees one number.
Visitors switch currencies through a front-end switcher you can place in the header or a widget. Behind it, live exchange rates come in through an API, WPResidence names currencyconverterapi.com, where you paste a single API key and set how often rates refresh (daily, every 12 hours, every 24 hours, or weekly).
One honest caveat on that API, because it sits under your headline feature. The free currencyconverterapi.com tier is a no-warranty service: the key has to be renewed every month, and the free plan caps you at 100 requests an hour. For a live, buyer-facing portal that is a real operational risk, since rates can quietly stop refreshing without anyone noticing. Budget for the paid tier if rates matter to you, or take the manual route. WPResidence lets you enter static rates by hand instead of calling the API, and it treats that endpoint as one service among others rather than a hard dependency, so you are not married to a single free feed.
Note: If you run page caching, and a portal this size should, exclude the currency switcher's cookies from the cache. Miss this and the switcher breaks under caching, so every visitor gets served the same stale currency no matter what they pick. WPResidence's documentation names the three cookies to exclude: my_custom_curr, my_custom_curr_pos, and my_custom_curr_symbol.
The engine can also set a default currency by IP and geolocation: GBP for a UK visitor, USD for the US, CAD for Canada. Visitors can still switch manually, and if you'd rather not auto-detect at all, an admin can turn it off.
Number formatting is fully configurable, which matters more than it sounds. You control the symbol and its position, the thousand separator, the decimal symbol, and the decimal count, so "1,200,000.00" and "1.200.000,00" both render the way the local market expects. There's a dedicated toggle for the Indian lakhs and crores system too, so a price shows as 15,00,000 rather than 1,500,000.
WPResidence says you can run 10 or more display currencies without a real slowdown, since conversion is just math on a stored number. In practice, WPResidence puts the norm at 3 to 6 currencies, which is plenty for most international portfolios.
Unit and locale display is theme-option-driven: you set it once, and it applies sitewide. The global area-unit label (square feet or square meters) is a single setting that feeds both listings and search, so a metric switch isn't just cosmetic, it changes what the filters measure against.
There's a metric-or-imperial toggle for distance and map radius, and date formats plus decimal separators follow the locale, so nothing reads foreign to the market you're targeting.
One install can serve multiple offices under a single domain, with each branch's listings and team kept separate. WPResidence handles this through its Agent, Agency, and Developer roles, each with its own dashboard, where an Agency groups its agents and shows the office About page, contact details, and map.
The routing that makes a franchise portal practical comes from MLSImport, WPResidence's default MLS and IDX solution. MLSImport uses office-code mapping to send each imported MLS listing to the correct agency or office automatically. So a portal covering a dozen branches keeps every branch's stock cleanly separated, without anyone hand-sorting the feed.
Leads land in one place too. The built-in WP Estate CRM stores every inquiry as a structured lead tied to the property, the agent, and the contact. Whatever language or currency a buyer used, their inquiry shows up in the same dashboard, which is what keeps a multi-market operation from splintering across tools.
For a franchise handling stock from several branches and buyers from several countries, that single-inbox behavior is the difference between a portal a manager can actually oversee and a dozen disconnected sites pretending to be one.
If your team already lives in HubSpot, WPResidence pushes leads there while the built-in CRM still logs them for agents, so nobody loses their working record. And role-based membership controls who can submit or edit listings, with admin approval and membership packages governing access.
That's a fair amount of machinery running at once, which raises the obvious question about speed and search visibility.
Short answer: the theme itself sets no hard limit on languages or properties, and multi-currency switching doesn't touch your URLs, so it can't muddy indexing. The real constraint on a big multilingual site is translation workload and hosting, not the theme.
WPResidence's own guidance runs 2 to 5 languages comfortably, and 8 or more with strong hosting behind it. Each language you add creates more database entries, which is normal.
The theme's documentation puts real-world page loads in the 1-to-3-second range, with healthy Core Web Vitals, once you have caching, a CDN, and image compression in place. WPResidence's guidance puts the gain from a CDN positioned near your secondary markets at 30 to 60 percent.
As a rough hosting guide, WPResidence suggests sizing for 20,000 to 30,000 monthly visits if you're expecting genuine global traffic.
On SEO, the structure holds up because the multilingual plugin does the heavy lifting. Each language gets its own URLs, titles, meta, and canonical tags, plus hreflang and split sitemaps generated through Yoast or Rank Math working alongside the plugin. Currency switching, by contrast, never changes the URL, so it creates no duplicate-content headache.
The taxonomy template builder is a useful lever here, letting you build per-country or per-city SEO layouts, an "Apartments in Berlin" block distinct from a "Villas in Dubai" one.
One honest caveat: machine or browser auto-translation on its own is weaker for SEO than a structured plugin with real per-language URLs. A properly built multilingual site can start to gain traction across markets, but it can take a while, and no theme can promise a ranking. What WPResidence gives you is the structure that lets the work pay off, not a shortcut around it.
Each niche real estate website type demands a different audience focus, data schema, and proof of authority.
For a multilingual real estate website, the usual pitch is bundling, and it’s worth being precise about where that actually holds. WPResidence puts multi-currency and a CRM in the box as core features. So does Houzez, which bundles comparable tooling, so this isn’t a clean sweep and we won’t pretend it is.
The clearest genuine gap is against RealHomes on multi-currency, which RealHomes treats as a separate add-on where WPResidence builds it in. And one honest asterisk on our own side: the MLS routing that makes a franchise portal practical runs through MLSImport, which is a separately priced add-on (from about $49 per month), not something bundled free with the theme.
So the fair read is narrower than “WPResidence does more.” It packages multilingual, RTL, multi-currency, CRM, and role management together, which saves integration work, but Houzez covers much of the same ground, and one of WPResidence’s own strengths, MLS routing, is a paid extra. Weigh it feature by feature against your actual needs, not on a bundling headline.
| Feature | WPResidence | Houzez | RealHomes |
|---|---|---|---|
| Multi-currency | Built-in core engine | Built-in | Separate add-on |
| CRM | Built-in (WP Estate CRM) | Built-in | Via add-on |
| Multi-office / MLS routing | Via MLSImport (separate paid add-on, from $49/mo) | Built-in options | Via add-on |
| RTL support | Native | Native | Native |
One caveat on the table: MLSImport is priced separately from the WPResidence theme, and the Houzez and RealHomes cells reflect their bundled offerings at the time of writing, which vendors do change. Confirm the current feature split on each vendor’s own site before you decide.
The practical migration sequence is straightforward. Launch your main language first, then export your current listings to CSV or XML.
The WP All Import add-on maps those fields into WPResidence, that import becomes your master language, and you add the other languages on top later. Set 301 redirects on the old URLs so any rankings you've built carry over.
Licensing is simpler than people expect: one WPResidence license covers one production site, no matter how many languages run on it. You only need extra licenses if you split languages across separate domains or separate installs.
Now the honest cost picture, because "built-in" doesn't mean free. The WPResidence theme is a one-time license.
WPML and Weglot are separate, ongoing costs billed yearly or by usage; WPResidence frames modest setups as often under $100 per year for those plugins. Polylang is free for a simple two-language site.
Layer hosting on top, and you have real recurring costs, so don't budget this as a one-and-done purchase.
On time, WPResidence's figures line up like this. Renaming and translating labels runs about 10 to 15 minutes, a second language using the bundled files often goes live in under an hour, and currency setup is usually under an hour too.
The theme's guidance puts a basic bilingual site at a one-or-two-working-day job for a careful non-developer. A full small-to-mid site, including listing migration and design, is more like 4 to 6 weeks.
Those aren't contradictory numbers; they're two different scopes, a bare bilingual switch versus a whole site build.
If nearly all your clients pay in one local currency and speak one language, you don't need any of this, and forcing multi-currency or multilingual on a single-market business just adds complexity a clear single currency would avoid. As a rough line, WPResidence's own guidance puts the tipping point at something like 20 to 30 percent of your leads coming from other regions before multi-currency starts earning its place.
Be clear-eyed about what the theme does and doesn't remove, too. WPResidence lowers the technical barrier; it doesn't do the planning for you.
Someone on your team still owns translation quality, field mapping, slug rules, and per-language search testing. That gap, the human work, is where projects stumble, not in the theme settings.
And sometimes separate country sites genuinely make more sense: when each market needs very different branding, has different legal rules, or calls for a different content structure entirely. If that's you, one unified portal is the wrong tool, and it's worth saying so plainly.
Each niche real estate website type demands a different audience focus, data schema, and proof of authority.
WPResidence's multi-currency engine is built into the core, storing one base price per property and converting on the fly using live rates from currencyconverterapi.com.
WPResidence says it sits on WPML's recommended-themes list and supports four translation plugins: WPML, Polylang, Weglot, and TranslatePress.
Native RTL support ships in the core stylesheet and flips the full layout for Arabic or Hebrew with no child theme or custom CSS required.
One WPResidence license covers one production site regardless of language count, but WPML or Weglot, hosting, and MLSImport for MLS routing stay separate recurring costs, so "built-in" is not the same as free.
One base price. WPResidence stores a single base price per property and converts it on the fly for display in whatever currency the visitor selects. That keeps search and sort fast and avoids maintaining separate price fields for every currency, which is what causes prices to drift out of sync on sites that store them individually.
Yes. WPResidence can set a default currency by IP and geolocation, so a UK visitor sees GBP and a US visitor sees USD automatically. Visitors can still switch currencies manually at any time, and if you'd rather show a single currency to everyone, an admin can disable auto-detection entirely in the theme settings.
Yes. WPResidence includes a dedicated toggle for the Indian lakhs and crores system, so a price displays as 15,00,000 rather than 1,500,000. It's part of the broader number-formatting controls, which also cover the currency symbol and its position, thousand separators, the decimal symbol, and how many decimal places show.
Yes, and the multilingual plugin governs which structure you use, WPML being the usual choice. It supports language subdirectories, subdomains, and separate domains per language for a stronger country focus. Remember the licensing rule with WPResidence: one license covers one production site, so splitting languages across separate domains or installs means each one needs its own license.
No. In WPResidence, switching currency never changes the page URL, so it creates no duplicate-content or indexing problems for search engines. Your multilingual SEO is driven by the translation plugin's per-language URLs, titles, and hreflang tags, not by the currency switcher, which only changes how the price is displayed on the same page.
One WPResidence license covers one production site no matter how many languages run on it, so a five-language portal on a single domain needs just one license. You only need additional licenses if you split languages across separate domains or separate WordPress installs, since each distinct production site requires its own license.
Not from the theme itself: WPResidence sets no hard limit on languages, each added language simply creates more database entries, and currency conversion is lightweight math on a stored number. Real-world load times stay in the 1-to-3-second range with caching, a CDN, and image compression in place. The practical constraint is your hosting and translation workload, not the theme.
Often not. If nearly all your clients pay in one local currency, a single clear currency keeps a WPResidence site simpler and easier to manage. Multi-currency starts earning its place once a meaningful share of your leads come from other regions and are thinking in another currency, at which point converting prices for those buyers becomes worth the setup.
WPResidence's multilingual toolkit does one main thing well: it collapses a stack of separate plugins into one package. A translation-ready core, native RTL, a built-in multi-currency engine, and MLSImport-routed multi-office management all live in the same theme, so you're not integrating five tools to run one international portal. What it can't do is the human work, translation quality, slug discipline, and per-language testing still belong to your team.
So the sensible next step isn't a purchase button, it's a look at your own numbers. Map your actual language mix and your lead-source split, and if a meaningful share is coming from other regions, WPResidence gives you a serious, honest foundation for a multilingual real estate website. If it isn't, keep things simple, and skip the machinery until your buyers ask for it.
You may also want to read our guides on setting up MLSImport for IDX feeds, configuring the WP Estate CRM, and building per-city landing pages with the taxonomy template builder.
