IDX and MLS plugins handle saved searches and alerts in two main ways. Some keep everything in your own WordPress site, while others store searches and alerts on remote vendor servers. With MLSimport feeding listings into WordPress and a theme like WPResidence handling alerts, every saved search, email, and lead stays on your own domain and in your user system. Alerts can look like they come from you, not from a third-party vendor with its own name everywhere.
How do IDX plugins technically store saved searches and who owns that lead data?
When saved searches live in your own database, you control and own that lead data. You decide how long to keep it and how to use it. You also decide what tools can see it.
On a self-hosted WordPress site, saved searches and alerts are data rows inside your own MySQL database, tied to real WordPress users. With MLSimport plus a theme like WPResidence, saved searches, favorites, and lead profiles sit as user meta and in a few custom tables on your own hosting. You can back them up, export them, or connect them to any CRM because the records are part of your site, not locked in a vendor account that might change later.
MLSimport keeps listing data in WordPress as native posts, while the theme writes each saved search and alert rule into your database. At first this sounds like a small detail. It is not. That setup means if you change themes, move hosts, or connect a new CRM, your leads and their saved criteria stay under your control. You are not asking a third-party to hand back the leads, because the plugin never moved them off your server in the first place.
| Setup type | Where saved searches live | Who controls lead records |
|---|---|---|
| MLSimport plus WPResidence | WordPress user meta and custom tables | Site owner with full database access |
| Self-hosted custom IDX code | Local WordPress or custom SQL tables | Developer or site owner |
| Hosted IDX basic plan | Vendor cloud accounts and services | Vendor controls storage and export paths |
| Hosted IDX brokerage plan | Central vendor CRM-style lead database | Vendor with admin access for broker |
| Mixed API plus WordPress widgets | Mostly vendor, some local session data | Vendor with limited API visibility |
The table shows a clear split between self-hosted and hosted setups. With local storage, you own and move your data as needed. With remote storage, you depend on the vendor’s tools and rules for export, long-term access, and any later migration. That trade-off never goes away, even if the features look similar on the surface.
How does MLSimport work with themes to deliver branded saved searches and alerts?
Pairing a data-import plugin with a real estate theme lets you brand every saved search and alert. The theme handles the client-facing parts, while the plugin stays in the background and just feeds data.
MLSimport pulls RESO Web API (Real Estate Standards Organization Web API) listing data into WordPress as clean property posts, and a theme such as WPResidence layers on the user features. The theme adds Save Search buttons, user dashboards, and alert settings on top of the imported listings, while WordPress itself tracks users and permissions. That split is simple: the plugin handles data sync, the theme handles how people save and get notified about that data.
In WPResidence, admins can turn on daily or weekly saved-search emails that run through WP Cron, so alerts go out from your own domain on a schedule you pick. MLSimport just keeps the listing inventory fresh, which means those scheduled checks always see the latest price changes and new homes. You can adjust the alert timing, and a basic rule is daily emails for hot markets and weekly for slower areas.
Inside the theme settings, you can edit the email templates: logo, colors, subject line, greeting, and the From address that shows in the inbox. MLSimport never injects its own branding into those emails, since the plugin stays in the background while the site and theme present everything under your name. Leads that come from saved searches or property forms log into the WPResidence CRM and can sync to tools like HubSpot, so the same branded alerts feed into your follow-up system.
In hosted IDX systems, will saved-search alerts and portals look like they come from me?
Hosted IDX alerts are usually co-branded, not invisible third-party emails. You may see your logo, but the vendor is still there.
Most hosted IDX services send saved-search emails from their own mail servers, even when they let you add your logo and contact info. The subject line and body can often match your colors, but the technical headers, SPF records, and sending domain usually point back to the vendor. A careful user or corporate spam filter can see that messages are relayed through an IDX provider instead of your own mail system, and that may affect how those messages get treated.
Some platforms allow strong visual branding, yet the client portals still run on the provider’s URLs or subdomains. So a buyer might click View all matches in an email and land on a page that looks like your site but lives at a different host name. Compared to a self-hosted stack powered by MLSimport, where alerts and search dashboards stay under your main domain, that hosted setup gives you less control over how personal the communication really feels.
How does using MLSimport affect whether clients see me as the sender of alerts?
When your site sends alerts directly, every message can appear to come from you personally. That includes the From line, reply address, and domain.
With MLSimport plus WPResidence, WordPress itself generates the alert emails and can send them through your own SMTP service on your domain. In the theme settings, you set the From name and email, such as Jane Doe, Broker <[email protected]>, so inboxes show you, not a software brand. That keeps the full path of the email under your control, from the sending domain to the reply-to address, unless your mail provider overrides it.
This setup also keeps the visual side clean. The theme’s templates show your logo, your colors, and only the MLS(Multiple Listing System) disclaimers that your board requires. MLSimport does not add outside logos or powered by lines into the client-facing emails or dashboards. Because leads and saved searches live inside WordPress, you can switch CRMs, change SMTP providers, or move to a new host without breaking alerts or changing how your name appears to clients.
What are the lead-nurturing differences between MLSimport and hosted IDX alerts?
Self-hosted alerts favor branding flexibility, while hosted alerts favor quick setup and scale. Both paths work, but they solve different problems.
On a site powered by MLSimport and WPResidence, you can have many saved searches and alerts, limited mainly by your hosting and email provider capacity. You decide how often alerts run, what they look like, and how they tie into your content, such as pages for New this week or Price drops in 90210. That freedom lets you match alerts to how you like to talk to buyers and sellers, not how a vendor template expects you to talk.
- MLSimport with WPResidence lets you tune each alert’s timing, content, and branding on your own terms.
- Hosted IDX tools favor quick setup, handling bulk email sending and tracking without using your server.
- A self-hosted stack makes it easier to tie saved searches to niche landing pages and blog content.
- Vendors often add canned market reports, which you trade for less control over design and data.
Here is the messy part. Hosted systems can feel easier, and sometimes they really are easier, especially when you are busy or your team is small. But that ease often hides limits around data ownership, styling, and long-term control of alerts. You may accept those limits for a while, then later find they slow down your follow-up plans. I am not saying one path is always better, only that the trade-offs tend to show up late, when changes are harder.
FAQ
Does MLSimport itself send saved-search emails to my clients?
No, MLSimport focuses on importing and syncing MLS listings into WordPress, not on sending emails. It stays on the data side.
Saved searches and alerts come from your theme or custom code that sits on top of the imported data. With WPResidence, for example, the theme handles the Save Search buttons, the alert schedule, and the email templates, while MLSimport keeps the listings up to date. That split keeps the plugin lean and lets you choose exactly how alerts should look and behave.
Can I remove all third-party branding from alerts when using MLSimport?
Yes, a site built on MLSimport and a capable theme can send fully white-labeled alerts. The vendor name does not need to appear.
Because the emails are generated by WordPress and styled by the theme, you control the logo, colors, wording, and sender identity. The only extra text you must keep is your MLS board’s required legal disclaimer, which is about compliance, not vendor promotion. No IDX provider logos or powered by messages need to appear in your client emails or dashboards.
Will I lose my clients’ saved searches if I leave a hosted IDX and move to MLSimport?
Yes, saved searches stored in a hosted IDX usually cannot be moved directly into a new self-hosted stack. That is a real loss.
Hosted systems keep saved-search rules and alert settings in their own databases, and most do not offer a clean export that another platform can read. When you move to a WordPress site powered by MLSimport and a theme like WPResidence, you typically invite clients to create new saved searches under your own domain. The upside is that from that point on, you own those searches and leads fully.
Can each agent on my site send alerts under their own name with MLSimport?
Yes, a multi-agent WordPress site can send agent-specific alerts when MLSimport is paired with the right theme. That can help teams feel more local.
WPResidence, for example, supports multi-agent setups where each agent has a profile and their own leads in the built-in CRM. The theme can use per-agent From names and reply-to addresses so alerts and follow-up emails look personal. MLSimport just keeps the listings current for all agents, while the theme handles which agent identity is used for each client touch point.
Table of Contents
