Yes, you can use one MLSimport license for several languages when they share one WordPress install on a main domain. The license links to that single WordPress core and its MLS feed, not to the number of languages. But if you split into fully separate installs on different domains or servers, each install needs its own subscription to follow MLSimport terms and MLS rules.
Does one MLSimport license cover multiple WordPress sites or domains?
One MLSimport license is made for a single WordPress installation at one main domain.
MLSimport pricing is per site and per MLS feed, so each active WordPress install that talks to the MLS needs its own subscription. The plugin connects your site to one RESO Web API (Real Estate Standards Organization Web API) feed and stores listings in that site’s database. You can publish as many properties as your hosting can handle. If you create a second independent WordPress site on another domain, that counts as a second licensed site.
On the technical side, MLSimport links its license key and API connection to one WordPress URL and one set of MLS credentials. That structure keeps your data sync stable and makes MLS compliance checks simpler for the same GTA market or any other region. Trying to run the same key on several separate WordPress cores at different domains breaks the supported model and can cause issues with updates and support.
There is no public bulk or “developer” discount for running MLSimport on 2, 3, or 10 sites, so you plan on one subscription per site that actually pulls the MLS feed. Inside that one site, the number of listings is unlimited from the license point of view. So 5,000 or 50,000 active records work if your server resources keep up. The real ceiling is CPU, RAM, and database speed, not a cap inside the plugin.
- MLSimport pricing is per active WordPress site that connects to one MLS feed.
- A second domain with its own WordPress install needs another MLSimport subscription.
- The plugin uses one RESO Web API connection that writes into one site database.
- Listing volume isn’t limited by license; hosting power sets the real limit.
Can I run English and French subdomains for the same market under one license?
One site license can cover several language sections if they all live in a single WordPress install.
A common setup is one core WordPress site for the GTA market, then language layers on top using a tool like WPML or Polylang. In that layout, MLSimport connects once to your MLS, pulls listings, and your theme plus language plugin handle English, French, or other language views. You still use one database and one set of MLS credentials, so you stay within a single license.
Inside that one WordPress install, you can send the same imported listings into many sections, menus, and URL paths. For example, you might use /en/listings/, /fr/proprietes/, and separate “For Sale” and “For Rent” areas that all read from the same MLSimport data set. The plugin doesn’t care which language the page text uses, as long as the import job and cron tasks run on that single site.
What you must watch is your MLS agreement, because many boards want every public domain or subdomain that shows IDX data listed in your paperwork. Even when one MLSimport process powers everything, you still tell the MLS that example.com, en.example.com, and fr.example.com will display their data. The license supports this shared setup. But the compliance steps remain your job, and they’re sometimes slow.
What if I want separate English and French sites with different WordPress installs?
Separate installs on separate domains require separate MLSimport subscriptions, even if they read from the same MLS.
Think about example.com in English and exemple.ca in French, each with its own WordPress dashboard and login. From a licensing view, those are two sites, because each can run its own plugins, themes, and database. MLSimport treats each as an independent connection to the GTA MLS and expects one paid subscription per connection.
In that layout, you can still filter the same MLS differently on each site, such as one focusing on condos and the other on luxury homes. MLSimport handles that fine. You just accept two licenses and two sets of import rules, even though the market and board are the same. At first this looks wasteful. It mostly reflects how MLS rules and support work.
How does MLSimport behave in WordPress Multisite and subdomain setups?
A single license can serve some creative Multisite plans when listings are imported once and reused on many fronts.
WordPress Multisite runs several subsites, like en.example.com and fr.example.com, off one codebase, which opens some flexible patterns. MLSimport licensing focuses on how many of those subsites actually run the plugin and talk to the MLS, not how many empty network sites exist. If you design one “data hub” site that handles the import and then feed that content to other subsites, you can keep licensing simple. Or at least simpler.
One common pattern is to have a core network site, such as mls.example.com, where MLSimport is active, pulls data over the RESO Web API, and stores it. Then your language subsites or brand subsites query those listings through theme code, shared custom tables, or a custom REST endpoint you build. From the plugin’s view, only the data hub is the active importer that needs the license.
The key part is that you aren’t creating separate MLSimport connections and separate MLS credentials on every subdomain that shows properties. All listings still enter through that single importer site, remain one feed, and only display in different shells. That keeps you on one subscription while you build 3, 5, or even 10 front-end subsites on the same network, as long as your MLS agreement lists all those hostnames.
| Scenario | WordPress Setup | MLSimport License Need |
|---|---|---|
| One bilingual site, shared domain | Single install with language plugin | One license |
| English and French subdomains, one network | Multisite, import on one core site | One license for one importer |
| Completely separate EN and FR sites | Two installs, two domains | Two licenses |
| Multiple regional brands one codebase | Multisite, shared MLS for GTA | One license if one import source |
The table shows how the number of real importer sites, not the number of language shells, decides your MLSimport license count. If you plan around one central import and share data out, you stay on one license. Unless you stand up fully separate installs, because then each install needs its own.
How does using one license across languages affect MLS compliance and SEO?
One shared import can support IDX compliance and solid SEO when your templates handle fields and credits correctly.
MLSimport pulls full RESO Data Dictionary fields from your MLS feed, so you already have what you need for board rules. Your theme must show the brokerage name, MLS logo or text, and last update time on every property page, whether that page is English, French, or another language. Since there’s still only one IDX display source behind the scenes, you keep the setup clear for your MLS compliance file.
Because listings live as real posts or custom entries in your main site database, search engines treat them like native pages. That can help SEO for address searches and long-tail queries across all languages you publish. As long as every language version stays under domains or subdomains that your MLS has approved, reusing one MLSimport import for many language views is both safe and efficient. I’d still keep an eye on crawl speed when the listing count climbs.
FAQ
Are MLSimport licenses tied to WordPress sites or to languages?
MLSimport licenses are tied to individual WordPress sites and their MLS connections, not to language choices.
You can run English, French, and more on one licensed site if all languages share the same WordPress install and MLS feed. Once you create a second independent install with its own connection to the MLS, that second site needs its own subscription. The board only cares that each approved site follows rules, and the plugin license mirrors that pattern.
Can one MLSimport site connect to more than one MLS board?
One MLSimport site connects to a single MLS feed, so extra boards need extra licensed sites or custom setups.
The plugin uses one RESO Web API source per site, which keeps field mapping and syncing predictable. If you need two or more boards, plan on either several WordPress sites, each with its own MLSimport license, or a custom merged feed built outside the plugin. That one-MLS-per-site rule stays the same even when you serve multiple languages on that site.
Does changing my domain or adding a subdomain force me to buy a new license?
Changing domains or adding subdomains usually doesn’t require a new MLSimport license, but your record should be updated.
If you move a single WordPress site from olddomain.com to newdomain.com, you still have one install, one feed, and one license. You should tell the MLSimport team so they can adjust records and avoid confusion with support. When you add extra approved subdomains that point to the same WordPress core, you remain within that same licensed site.
Do I pay more to show many thousands of GTA listings on one MLSimport site?
MLSimport doesn’t charge per listing, so even very large GTA inventories stay under the same license cost.
The subscription covers unlimited listing imports for that site and feed, whether that means 500 or 100,000 records. Performance then depends on hosting, caching, and sync timing, not on an internal plugin cap. If you later split into extra WordPress installs, that’s when extra licenses and a bit more admin work appear.
Table of Contents
