Can I manage and monitor multiple client sites using this plugin from a central dashboard, or do I have to log into each WordPress site separately?

MLSimport doesn’t give you one master control panel for every client site at once. Each WordPress site keeps its own plugin settings, MLS (Multiple Listing Service) link, and import rules, so you still log into each site’s admin to adjust how listings load and display. A shared MLSimport customer account can group and pay for all site licenses in one place, but the day to day listing controls stay inside each WordPress dashboard.

How does this plugin handle managing multiple client sites in practice?

Each website you build runs on its own, with its own MLS connection and settings. In real use, that means every client site has its own WordPress install, its own plugin setup, and its own MLS member tied to it.

MLSimport connects one site domain to one MLS user account, so the listing feed and search logic stay separate per project. At first this sounds like extra work. It actually makes mistakes on one site less likely to affect any other and keeps debugging simpler.

MLSimport ties each paid subscription to a single domain and a single MLS member’s RESO Web API credentials. For an agency with 5 or 20 client sites, the rule of thumb stays simple: one active subscription per live site. All imported listings are stored in that site’s own WordPress database as custom property posts, so you can hold thousands of listings per site without sharing data across clients.

The plugin behaves the same way on every project, but you pick the filters and import searches for each client. On one site you might only pull the broker’s own 800 listings. On another you might load a whole city or county, as long as MLS rules allow it. Because MLSimport keeps data local per site, each client can run their own theme, URL structure, and lead tools without touching anyone else’s setup.

Is there a true central dashboard to control all MLS-enabled WordPress sites?

There’s no single control panel for every site’s settings; management stays site specific. Every WordPress install gets its own plugin settings page where you enter MLS credentials, set import rules, pick field mapping, and control sync options.

That work always happens inside that site’s wp admin. So you still click into each dashboard when you want to change which listings you import or how they map to your property post type. MLSimport keeps MLS choices local to each site for clarity and safety.

Outside WordPress, the main MLSimport account gives you one place to see license keys, billing, and subscription status for all the sites you own or manage. That vendor portal helps when an agency runs, say, 12 sites and wants to keep renewal dates and invoices under one email. It isn’t a “change settings on every site at once” tool, but it does group the money side so bookkeeping stays sane.

If you run a WordPress multisite network, you can enable the plugin on several subsites and still configure each subsite on its own. In that setup, each subsite acts like a separate small site with its own MLSimport settings page and its own scheduled imports. Many agencies pair this with tools like MainWP or similar for mass plugin updates, while MLS choices still live per site.

The table shows the split. The account area groups money and keys, while each site keeps control over its own MLS connection and mapping. That layout fits agencies that want one owner for all subscriptions but still like strict, per site control over real estate data.

What multi-site workflows work best for agencies using this plugin?

Standardizing your build process makes handling many MLSimport sites faster and more boring, which is good. Agencies that stay calm at 10 or more installs often lock in a single real estate theme and a known plugin stack.

With MLSimport, that usually means picking one tested theme like WpResidence or another supported layout and cloning it for every new client. You then only change colors, logos, and a few search settings per site instead of rethinking layout every time. It sounds strict, but it keeps life simple when you’re tired.

The plugin lets you reuse the same import templates, mapping choices, and search rule patterns from project to project. A useful flow is to keep one “master” demo site where you refine your mapping and property detail layout first, then copy those settings when you spin up the next client. Because MLSimport uses the MLS RESO Web API and syncs hourly, a typical client site can handle thousands of listings without changing this routine.

From a process point of view, most agencies end up building an internal checklist that covers MLS approval steps, plugin install, first test import, and search page wiring. That list keeps you from missing things once you hit your fifth or fifteenth site. Actually, the plugin’s behavior stays the same on the twentieth install as on the first, so once your workflow is tuned, new builds move quicker and support questions drop.

• Pick one supported theme and one standard plugin stack for all client sites.
• Save a reference site with proven MLSimport mapping and search options.
• Clone that reference site to launch new clients in under a day.
• Use a written checklist for MLS approval, first import, and Go Live review.

Can I monitor listing sync health across multiple client sites efficiently?

You check sync status on each site, using its logs and any outside monitors you add. Inside each WordPress dashboard, the plugin shows its own import logs and last sync times so you can see when MLS data last updated.

MLSimport schedules hourly jobs to pull changes from more than 800 RESO certified MLSs, and those logs are your first stop if something feels off on a single site. You review them one site at a time, which keeps the picture clear when you track a specific client issue. Here’s the honest part. It can feel a bit repetitive when you have many sites.

Many agencies add outside monitoring, like uptime checks or cron monitors that ping a key import URL on each domain every few minutes. That outside watcher will alert you if a site stops responding long before listings look stale. In practice, combining the plugin’s logs with light external monitoring per site gives enough coverage to keep a dozen or more MLSimport sites healthy without guessing.

How does per-site licensing and pricing work when I have many clients?

Costs scale in a straight line with your client count, with one subscription per site. The pricing model stays simple: one paid subscription connects one website domain to one MLS member’s RESO Web API access.

MLSimport charges a flat monthly fee per site, with a yearly option at a lower effective rate, and there are no setup fees. Since there are no per listing limits from the plugin side, you can import as many listings as the MLS and your hosting allow without extra charges. That part is pretty nice.

For an agency, this means if you run 3 client sites you hold 3 active subscriptions, and if you grow to 15 sites you hold 15. The same customer login can store and pay for all of those in one billing profile, so accounting stays tidy even as your list grows. Each license remains tied to that specific domain and that specific MLS member, which keeps compliance clean and avoids mixing data between unrelated clients.

FAQ

Can one MLSimport license cover several different WordPress domains?

One license is meant for one WordPress site domain only. The subscription for MLSimport is bound to a single site URL and the MLS member behind that site.

If you build three separate client domains, each needs its own license so the vendor can keep billing, support, and MLS compliance separated. Sharing one license across unrelated domains isn’t the supported pattern and will cause problems.

Can one agent’s MLS credentials be reused on multiple sites they own?

One agent’s MLS access can be used on several sites, as long as each site has its own license. In that case, you’d create a separate MLSimport subscription for every domain, but all of them can point at the same RESO Web API credentials from that agent.

This works well when a broker runs, for example, a main brand site and a smaller community site. The MLS rules still apply, so the agent must be allowed to show the data on each domain.

Can I mirror listings from one MLSimport powered site to another automatically?

The plugin doesn’t sync listings between sites, it imports straight from the MLS on each site. Every install reads from the MLS feed into its own WordPress database instead of copying posts from another website.

If two of your sites should show the same homes, you connect both to the MLS and set matching import rules. That way updates like price changes appear correctly on both without building a fragile cross site sync layer.

Who should own the subscriptions, the agency or each client?

Either model works, but having the agency hold licenses often keeps management smoother. Many agencies keep all MLSimport subscriptions under one master account, then rebill clients as part of a care plan.

That gives you control over renewals and quick access when something needs a fix. Some shops prefer clients to pay the vendor directly; in that setup, make sure you still have admin access to each site’s plugin settings so you can support them properly. Here I’d pick the model that matches how you already bill for hosting and care plans.