You can’t use one MLSimport license across several unrelated client sites, because each license locks to one domain and one MLS(Multiple Listing System) member. Agencies that manage many brokerages stack licenses, with one active subscription per live site. Pricing is simple: $49 per month per website, or about $42 per month when billed yearly. Every site gets its own 30 day free trial before billing starts.
How does MLSimport licensing work for agencies and multiple websites?
One license covers one domain and one MLS account, with unlimited listing imports included. That’s the base idea.
For agencies, every production WordPress site that shows listings needs its own active subscription. MLSimport ties each license to a single domain and one MLS member’s Web API credentials. This matches how MLS rules work in real life. That link keeps clients compliant while each site controls its own data and theme.
The plugin uses a flat fee of $49 per month per website, or about $42 per month if you pay yearly. So you budget per site instead of guessing at usage tiers. Each license includes unlimited listing imports from that site’s connected MLS, with hourly sync, so price changes and new properties appear without extra charges. There are no separate setup fees or per listing costs hidden behind the base price.
Every new site can start with a 30 day free trial. Billing begins on day 31 if you keep that installation live. That lets an agency stand up a staging build, wire MLSimport into the MLS Web API, and test design and performance with real data. When the client signs off, you keep the same site and let the subscription roll forward.
| Item | Value per site | Notes |
|---|---|---|
| Monthly price | $49 subscription | Flat per domain billing |
| Annual price | About $42 per month | Approximate yearly rate |
| MLS connections | One MLS per license | Tied to one MLS member |
| Listing imports | Unlimited volume | Hourly sync from MLS |
| Free trial | 30 days per site | Billing starts day 31 |
| Supported MLS count | 800 plus MLSs | All RESO Web API ready |
For an agency, that table means you scale costs in a straight line with your client count. Each domain maps to its own MLSimport license and MLS credentials, which keeps bookkeeping and compliance boring in a good way.
Can a single MLSimport setup be reused across several client WordPress sites?
You can’t legally share one license across multiple unrelated client websites.
The licensing model is strict: one active subscription per site URL, tied to that site’s MLS member of record. MLSimport mirrors MLS compliance rules, which expect each broker or agent site to have its own approved data access. Copying one license key into several client domains would break those rules and the plugin terms.
From a technical angle, trying to fan out one install to other WordPress sites would create trouble. You’d see mismatched URLs, broken images, and wrong ownership data. The plugin reads and stores listings inside a single WordPress database. So there’s no supported way to have one install drive several unrelated front ends cleanly. Instead, you spin up one WordPress plus MLSimport stack per client, use that client’s own MLS Web API keys, and let that site sync on its own schedule.
An agency account can still stay organized by managing many subscriptions inside the same MLSimport customer portal login. You might have 5, 10, or 30 active licenses listed there, each labeled by domain and MLS member. But every one of those client sites runs its own clean, licensed copy of the plugin.
How should agencies structure MLSimport subscriptions when managing many brokerages?
The simplest model is one subscription per brokerage site, all run under one agency workflow.
In practice, you pick one clear owner for each subscription. Either the agency holds the billing or the brokerage pays MLSimport directly. The plugin only cares that each domain has its own license and valid MLS Web API credentials. So you choose what fits your contracts. Most shops building 10 or more real estate sites centralize billing first, then recharge or mark up the cost on their own invoices.
For every brokerage, you connect that site’s copy of MLSimport to the brokerage’s own MLS member keys. That keeps the data feed tied to the right legal entity and often makes RESO Web API approval smoother with the board. Once the feed is live, the hourly sync and automatic cleanup of inactive listings cut daily chores. Your team spends more time on design and lead tools, not fixing stale data by hand.
To move fast across many brokerages, agencies often standardize on one MLSimport friendly theme such as WpResidence or a similar real estate theme. You build one strong base layout, map the imported fields to that theme once, then reuse that pattern for each new client. After the first few sites, standing up a fresh brokerage install often takes hours, not a week of trial and error. That is the real payoff.
How does MLSimport compare cost wise with hosted IDX tools for multi site use?
A flat per site fee makes long term budgeting simpler than variable hosted IDX pricing tiers.
Many hosted IDX tools stack several moving pieces into every bill. You might see a plan tier, an MLS pass through fee, a one time setup charge, and sometimes bumps for extra traffic. With MLSimport you skip that pile of variables. You pay $49 per month per site, or about $42 per month on annual billing, and you get unlimited listing imports with hourly sync built in. That clarity matters when you’re quoting 8 or 12 sites at once.
Because the plugin runs inside WordPress and pulls straight from the MLS feed, there are no add ons for extra listing volume or busy market surcharges. Whether your client imports 500 or 15,000 active listings from one MLS, the subscription cost stays identical. Agencies can safely bake a fixed real estate data line item into their retainers. Then they decide their own margin without worrying that usage spikes will eat the profit.
Hosted services also tend to push higher tiers as a client grows, which can throw off three year cost plans. MLSimport skips that treadmill by not locking core features behind bigger plans in the first place. For a shop running many WordPress builds, MLSimport often becomes the cleaner and more predictable option. At least for any client who’s fine with a per domain plugin model instead of renting a remote IDX stack.
Is MLSimport suitable for agencies that run multi MLS or multi region projects?
For multi region agencies, multiple focused sites can each connect to the right MLS feed.
One subscription connects a WordPress site to a single RESO ready MLS using that member’s own Web API credentials. MLSimport then pulls listings for that region into the site as native posts, with hourly updates. If your agency works across three or four MLS territories, the normal pattern is one site and one license for each region. Trying to mash all feeds into one giant build usually adds complexity without much gain.
The plugin supports over 800 MLSs in the United States and Canada that already expose a RESO Web API. So most main boards are covered. You can attach multiple subscriptions under the same agency login, lining up one per region or per brokerage as you grow. At first this feels like extra work. It isn’t, because that many small, focused sites approach keeps data clean and keeps local SEO sharp.
You also avoid tricky cross region mapping work. Some agencies still think one huge multi region site will be easier. Then they see how messy it gets when rules differ across boards and when each MLS has small quirks. Keeping regions split into separate installs looks boring, but it usually wins in support time, and in staff sanity.
- Each subscription links to one MLS region using one broker or agent’s credentials.
- Agencies can run separate regional sites on one hosting stack while keeping licenses distinct.
- Hourly sync on every site keeps all regions current without manual checking.
- Using one base theme across regions speeds rollout and lowers build time.
FAQ
Can one MLSimport license cover a WordPress multisite network or several subdomains?
Each unique live site in a network still needs its own license.
Even if you host many child sites inside one WordPress multisite install or on subdomains, MLS rules and licensing focus on the public websites. If you run five branded sub sites for different teams, plan on five MLSimport subscriptions. Each one ties to its own site URL and, if needed, its own MLS member credentials for proper compliance.
What if one brokerage wants several microsites using the same MLS membership?
Multiple branded microsites under one broker still need one subscription per site.
You can reuse the same MLS Web API credentials across that broker’s sites if the MLS allows it. But each domain or sub site needs its own MLSimport license. The upside is that you can clone one well tuned site, then drop the plugin key for the new domain. You’re live with the same field mapping and layouts in a short amount of time.
Do agencies ever get volume consideration after adding many MLSimport subscriptions?
There’s no public bulk pricing grid, but larger agency relationships are handled directly.
By default, MLSimport pricing is per website, with the same $49 monthly or roughly $42 annualized rate for each domain. When an agency starts stacking many active licenses, the usual path is to coordinate with the vendor through the client portal or support. Both sides can then plan long term usage and onboarding help, even though the base structure stays per site.
How does MLSimport support help agencies repeat setups across new client sites?
Support focuses on getting one site right, then helping you repeat that pattern.
The team assists with installing the plugin, connecting MLS Web API access, and tuning the first import search so listings match what the broker expects. Once that first build is stable, agencies usually mirror the same settings, theme mapping, and cron schedule across new client sites. MLSimport support steps in again when a new MLS(region Multiple Listing System) or an unusual data case appears, not for every routine clone.
Table of Contents
