Yes, MLSimport supports bilingual and multilingual WordPress sites with tools like WPML, Polylang, or Weglot, including translated field labels and search forms. Listings are stored as normal WordPress posts and taxonomies, so translation plugins treat them like any other content. The real estate theme handles interface text, while translation tools handle property text. This lets you run English–French sites with synced MLS data in both languages without a separate feed.
Before choosing MLSimport, how well does it handle multilingual sites?
Importing listings into the site database is the base for real multilingual real estate content.
MLSimport brings MLS properties into your WordPress database as real posts, not remote iframes. That detail matters a lot for any serious bilingual setup. Because listings live inside WordPress, translation plugins can read and translate them like normal posts. You can then build English–French sites where both languages share the same MLS inventory, but keep their own URLs and menus.
The plugin imports into the custom post types and taxonomies of supported themes like WPResidence, Houzez, RealHomes, and WP Estate. These themes already work with common translation plugins. MLSimport fits into those theme structures, so property data from your MLS flows into fields and taxonomies that WPML or Polylang can mark as translatable. You are not stuck with a fixed IDX(Internet Data Exchange) layout, so each language still uses your theme templates.
Hourly sync keeps your WordPress database aligned with the MLS, so both language versions stay current on price, status, and new listings. When a listing goes pending or sold in the MLS, the change reaches your site in about 60 minutes. The change then shows in every language that exposes that listing. All translations sit on top of the same core post, so you keep one source of truth and avoid drifting copies.
- Imported listings as posts let translation plugins manage bilingual content with full SEO control.
- MLSimport fits into multilingual-ready themes, so language behavior stays handled at theme level.
- All imported listing content and taxonomies can be marked as translatable like any post type.
- Hourly RESO Web API sync keeps every language view aligned with live MLS changes.
Can I use WPML or Polylang to translate MLS-imported listings and pages?
Standard WordPress translation plugins can translate imported listing posts and their related taxonomies.
MLSimport fills your theme property post type, custom fields, and taxonomies with data that WPML or Polylang can register as translatable elements. In practice, you pick which parts to translate: titles, long descriptions, taxonomies like City, and URL slugs for each language. Raw numbers such as price, beds, baths, and square footage stay shared across languages. That keeps data consistent and cuts down on repeated work.
A common workflow is to let the plugin import everything in the base language, then use WPML or Polylang duplicate and translate features. You clone selected listings into French, Spanish, or another language and edit only human-facing text fields like title, short description, and SEO meta. Search-result archives and property templates keep using your theme layouts, but the language plugin controls which posts show for each language. It also controls how their URLs look in each language.
Weglot or similar services can sit on top of MLSimport to auto-translate visible content in real time. Often in less than a second per page. That path helps if you bring in thousands of listings and do not want to hand-translate every one. You trade perfect nuance for speed, but get near-instant coverage for every new and updated listing without touching MLSimport settings.
| Element | How MLSimport exposes it | How WPML/Polylang can translate it |
|---|---|---|
| Individual listings | Posts in the theme property post type | Duplicate and translate titles, excerpts, descriptions per language |
| Property taxonomies | Categories such as type, status, city, neighborhood | Mark as translatable and give language-specific names and slugs |
| Custom fields | Post meta mapped from MLS data fields | Translate text labels while sharing numeric or coded values |
| Archive and search URLs | WordPress archives using theme templates | Set language-specific URL structures, menus, breadcrumbs |
The table shows that MLSimport does not fight translation plugins. It feeds them clean WordPress objects to work with. Once elements appear as posts, taxonomies, and meta, your chosen multilingual tool decides how each language URLs, labels, and texts should appear. At first it seems more complex than that. It is not.
How are search forms and field labels translated on bilingual MLS sites?
The search interface and field labels are translated at the theme level, not inside the feed.
MLS data from MLSimport is only the raw content, while the search form, labels, and buttons come from your active real estate theme. Themes like WPResidence and Houzez ship with translation files and often include ready-made WPML configs for property interface strings. Translation plugins then pick up those strings, so labels such as Price, Bedrooms, Bathrooms, and City can appear in English on one URL and French on another.
Once you translate those strings, the same translated labels show on all search forms and listing pages. MLSimport keeps importing and syncing listing values underneath, but every dropdown, filter, and breadcrumb uses the language your visitor selected. This split stays simple in practice. The feed handles data, MLSimport maps it into theme fields, and the theme plus translation plugin handle what users read.
What is the practical workflow for a bilingual English–French MLSimport website?
A bilingual setup combines MLSimport, a translation-ready theme, and a clear translation workflow.
The first step is to pick a supported real estate theme that already works with WPML or Polylang and has French translations. After that, MLSimport connects to your MLS with RESO Web API credentials. Then you map MLS fields like price, beds, baths, and address into theme property fields through its setup screens. Within a day, you usually have hundreds or thousands of live listings in English, depending on MLS size.
Next, you configure your translation plugin so that property post types, taxonomies like Property Type and City, and menu items are marked as translatable. In WPML, for example, you can choose to translate only high-value listings or all listings. You can also control which meta fields such as title and short description should get a second-language version. The plugin keeps one shared property record underneath, so both English and French pages track the same MLS data updates.
For the actual translation work, you pick between manual human translation of key properties or automated tools like Weglot riding on top of the site. Many teams translate only their top 50 or 100 listings by hand and let machine translation cover the long tail. That is the honest trade. MLSimport keeps importing, updating, and pruning listings every hour, while your multilingual stack makes sure visitors switching language still see fresh data with the right labels.
I should mention one more thing. Some teams overcomplicate the workflow and then blame the tools. Start simple, test a few listings, then grow the bilingual setup once you see how your own process feels day to day.
FAQ
Does MLSimport itself provide multiple languages, or do I need another plugin?
MLSimport does not provide its own language system and works with WordPress translation plugins.
The plugin job is to pull MLS data into your site as clean WordPress content. For bilingual or multilingual behavior, you add tools like WPML, Polylang, or Weglot on top of that content layer. Those tools handle language switchers, translated URLs, and field labels, while MLSimport keeps every language view wired to the same live MLS feed. At first you might expect MLSimport to translate itself. It does not, and that is usually better.
How quickly do new or updated listings appear in the second language?
New and updated listings are available for translation within about an hour of changing in the MLS.
MLSimport runs an automatic RESO Web API sync roughly every 60 minutes, which pulls new listings and major changes. Once the base-language post exists, WPML or Polylang can clone and translate it, or Weglot can auto-translate it on the fly. The delay you see in the second language usually comes from translation time, not from the MLSimport sync itself.
Do English and French versions share the same MLS inventory or use separate feeds?
All languages on a site share a single MLS feed and a single listing inventory.
The plugin imports each MLS property once into WordPress, then translation plugins create language versions that sit on top of that record. That means status, price, and photos stay in sync across English, French, and any other language. You can still choose to only publish translations for selected listings if you want a smaller set visible in the second language.
How does bilingual SEO work with MLSimport when each language has its own URLs?
Bilingual SEO works by letting each language use its own URLs and meta while sharing one data source.
MLSimport feeds the WordPress database, and plugins like WPML or Polylang then assign language-specific slugs, titles, and meta descriptions to each version. Search engines can index en and fr URLs separately, while both still track the same MLS property underneath. This setup gives you clean language separation, proper hreflang signals, and current market data in every language you serve.
Table of Contents
