WPRentals Translation Plugin- Beta Version Is Here

You’re running WPRentals or WP Residence in one language. Your listings are fine. But most visitors won’t browse, search, or inquire in a language they’re not comfortable with. They just leave.

The usual fix? Stitch together third-party multilanguage plugins, pay extra licenses, and then bounce between support teams when something breaks. Custom fields stop matching. Filters break. Prices disappear. The content looks translated, but the data behind it is a mess.
So we built our own.
A free multilanguage plugin, made specifically for WPRentals and WP Residence. It’s integrated. It’s automated. And it’s designed around how real estate and rental sites actually work.

Important: You need WPRentals version 3.17.1 to run this plugin.

How to Get the Beta

This is a beta release. It works, and we’re using it on test sites. But we want real usage on real websites to find what we missed.

Download it from here download link

 

If you run into bugs or something doesn’t work the way you expect, message us through the ticket system or on Facebook. That feedback is how we make it production-ready.

Video Walkthrough
We recorded a full walkthrough of every feature. If you want to see it in action before installing:

Help Us Make It Better

This is a beta. That means we shipped it knowing it’s not perfect — because we’d rather build it with you than guess what you need.

Here’s what we’re looking for:

Bug reports. Something broke? A field didn’t sync? A menu item points to a 404? Tell us exactly what happened, on what page, and with what language pair. Screenshots help. The more specific, the faster we fix it.

Feedback on what exists. Does the workflow make sense? Is there a step that feels confusing or out of order? Did automatic translation miss something it shouldn’t have? We want to know what the experience is actually like on a live site — not just on our test installs.

Feature requests. What’s missing? Maybe you need a different translation engine. Maybe you want per-listing translation status tracking. Maybe the URL structure options don’t cover your setup. If you’re thinking “this would be great if it also did X” — that’s exactly what we want to hear.

Send everything through the ticket system or message us on Facebook. Every report gets read.

What It Does

Here’s what the plugin covers, step by step:
Languages setup. You define what languages your site supports, what’s visible to visitors, and what the default is. Each language gets its own locale, slug, and visibility toggle.
Theme and plugin string translation. Buttons, labels, filter names, search labels — all the small UI text that makes a site feel half-translated when you skip it. The plugin scans your active theme and plugins, collects the strings, and lets you translate the ones your visitors actually see. Then it generates a translation file so WordPress loads them properly.
If you skip this step, you end up with translated content but the site still says “Search” and “Property Status” in English. That looks broken.
Taxonomy translation rules. This controls how categories, tags, and custom taxonomies behave across languages. It affects filters, archives, and term links on the front end.

Custom field rules. This is the part most multilanguage setups get wrong with real estate sites. Prices, bedrooms, bathrooms, addresses, map coordinates, IDs — all the structured data that makes listings work. The plugin lets you set copy behavior for fields that should stay identical across languages (like price and coordinates) and translate behavior for fields that should change.
Skip this, and you get listings where the translated content looks fine but the data behind it stops matching how the theme queries and displays properties. Broken filters. Missing listings. Bad search results.

Automatic translation with AI. This is where you can bulk-translate selected post types into a target language. You pick your translation engine (OpenAI for this version), enter your API key, and choose which post types to translate — properties, pages, posts.
Two things to know about automatic translation:

You need an OpenAI API key. This is from OpenAI, the company behind ChatGPT. You’ll pay OpenAI directly for the API usage — it’s not included in the plugin. For most sites, translation costs are low (a few dollars for hundreds of listings), but it depends on your content volume.
It gives you a strong first draft, not a final human-level rewrite. You still need to review the output. It’s fast and surprisingly accurate, but treat it as a starting point.

Menu synchronization. The plugin copies your menu structure and maps items to translated posts and terms. If a translation doesn’t exist yet, you set a fallback link so the menu doesn’t lead to dead ends. This keeps navigation consistent across languages — which matters more than people think.

Settings and URL structure. Set your default language, choose your URL strategy, and configure language switcher placement in your menus.

Share the Post:

Related Posts