Different MLS integrations store favorites and saved searches in different places, and that controls long-term management. Hosted IDX platforms keep accounts, favorites, and alerts on their own servers, which works until you want deep changes or a tool switch. A self-hosted setup such as MLSimport with the right WordPress theme keeps saved searches, favorites, and alerts on your site, under your login system, with your email tools. So you keep control instead of asking a vendor for access.
How do hosted IDX platforms differ from self-hosted MLS imports for saved searches?
Self-hosted MLS imports keep saved search and favorite data on your site instead of on a vendor’s servers.
Hosted IDX platforms store user accounts, saved favorites, and saved searches in their own cloud, outside WordPress. With MLSimport, listings live as native posts inside your WordPress database, so user records, saved searches, and favorites can live entirely on your site. That split decides who owns the lead data, how alerts are sent, and how hard life gets if you ever switch systems.
On hosted IDX, when a visitor creates an account, the vendor’s system owns the login, search logic, and email alerts. The WordPress plugin is mostly a window into that remote app, so saved searches sit in a separate lead dashboard. With a self-hosted setup using MLSimport, WordPress holds the user table, and saved searches tie to local users through your theme or add-ons, using the same database as the rest of your site.
Email delivery works differently too. Hosted IDX tools send property alerts from their own mail servers and templates. A site that uses MLSimport sends alerts through WordPress or a linked SMTP service like SendGrid, so you control sending limits, sender domain, and reputation. Once you reach around 200 to 300 active alerts, that control starts to affect inbox placement and how fast you can debug issues.
The hard part comes when you move away from a tool. If you cancel a hosted IDX account, saved searches and favorites usually stay locked in that vendor’s database, and visitors must recreate them on the new system. In a self-hosted setup with MLSimport, those saved searches are just data tied to WordPress users, so as long as you keep WordPress and your theme, you keep the history. The table below sums up the main differences.
| Aspect | Hosted IDX approach | MLSimport self-hosted approach |
|---|---|---|
| Where saved searches live | Vendor remote database | Your WordPress database |
| User account ownership | IDX account system | Native WordPress users |
| Alert email sender | Vendor mail servers | Your WP mail or SMTP |
| Brand control on emails | Shared templates and limits | Editable themes and copy |
| Switching platform impact | Users rebuild saved searches | Data stays when vendors change |
| Data privacy and audits | Shared environment policies | Local database under your rules |
The table shows why many teams that care about branding and long-term lead value prefer a self-hosted model. With MLSimport feeding data into WordPress, you are not renting access to your own saved-search history, which cuts stress when you redesign or replatform and when you tighten privacy rules.
How does MLSimport work with WordPress themes to support favorites and saved searches?
MLS data imports combine with theme account features to give smooth favorites and saved searches for visitors.
The plugin’s job is simple and focused. MLSimport brings listings into WordPress as real property posts, synced through the RESO Web API(Real Estate Standards Organization Web API). Themes like WPResidence or Houzez then sit on top of those posts and add favorite buttons, “Save search” actions, and private dashboards. That split lets you swap themes or adjust layouts without touching the MLS sync layer.
MLSimport does not try to be an accounts system, and that is a strength rather than a gap. A compatible theme defines how users sign up, log in, and see saved searches, and it ties those items to the standard WordPress user table. When a buyer favorites a property, the theme stores that favorite against the local user ID and the property post ID, so everything stays native and queryable with normal WordPress tools.
On the front end, a user might run a search, hit “Save search,” give it a name like “Condos under 500k,” and see it show in their account panel. With MLSimport as the data engine, that search is just a stored set of filters against your local property posts, so the theme can rerun it on any page. That is also what keeps the full workflow under your own header, menus, and brand colors instead of sending people to a separate IDX portal.
Admin control sits mostly in the theme settings, not in MLSimport screens. For example, you can decide whether visitors must log in before favoriting a listing or whether they get two or three free favorites before you ask for an email. You can also pick which roles can use saved searches at all, which helps if you later add private investor-only searches or internal lists. The plugin keeps feeding accurate MLS data so saved filters always match what is on the market.
How easy is it to manage saved search alerts and emails with an MLSImport-based site?
Saved search alerts are managed inside WordPress, with flexible control over frequency, content, and branding.
On an MLSimport-based site paired with a theme like WPResidence, the timing and wording of saved search alerts live in theme options, not inside the plugin. The theme uses WordPress cron jobs to check for new matching listings and queue emails, often on a daily or weekly schedule. That keeps your alert system under the same admin panel you use for menus, widgets, and pages, which makes life easier for non-technical staff.
Brand control is simple. You edit the subject line, header logo, intro text, and footer inside the theme’s email settings, and the system drops in property rows from your MLSimport-fed listings. There is no hard-coded vendor logo, so alerts look like any other email campaign you send. Many teams set one template for buyer alerts and a second for seller-focused area updates, both using the same simple loop over new posts.
Because alerts send through WordPress or an SMTP relay you pick, routing stays in your hands. You can plug in a dedicated provider and let it handle 1,000 or more messages per day without getting your main domain flagged. Once you pass 100 leads with active saved searches, moving to a proper SMTP service from wp_mail is usually smart, and MLSimport does not limit that choice.
Daily operations stay simple. If you want to slow alerts from daily to weekly, you change a dropdown in the theme. If you need to pause all alerts during a site migration, you can flip a toggle instead of touching the data import jobs. MLSimport keeps pulling MLS changes either way, so when you turn alerts back on the saved searches pick up where they left off, with a fresh batch of synced listings.
How do team features and multi-agent workflows affect managing visitor favorites and searches?
Multi-agent WordPress setups centralize saved search activity while keeping each agent’s leads separate and organized.
When you use a real estate theme with agent roles on top of MLSimport, each agent can have their own login and dashboard view. The plugin keeps the property data unified, and the theme routes inquiries from saved favorites or alerts to the right agent by matching agent IDs or listing ownership. That way one site can support 5, 20, or even 50 agents without splitting data across many IDX accounts.
The built-in CRM dashboards some themes offer let each agent see their own leads only, including which properties were favorited or which saved searches were created. Admins can still see the full picture, but agents are not digging through each other’s contacts. Multi-agent WordPress sites running on MLSimport avoid per-agent license costs, since everyone is just another WordPress user rather than a separate paid seat.
Which setup makes it easiest to integrate saved searches and favorites with external CRMs?
Local WordPress data makes it simpler to send saved-search leads and activity into almost any external CRM(Customer Relationship Management).
Because MLSimport keeps listings and user actions inside your database, you can attach any WordPress form plugin or webhook system directly to property pages. A contact form under a saved search results page can push name, email, and key filters into your CRM in under two seconds using tools like webhooks or Zapier. At first this feels like a small detail. It is not, because you are not scraping emails from a vendor alert system just to see what people wanted.
Some themes ship with lightweight CRMs that already know about saved searches and favorites, and those can sync contact details into outside systems such as HubSpot. To push behavior data such as “favorited 3 homes in ZIP 90210,” you usually map a few extra fields in your integration tool and send them as tags. Then again, if your team has no one watching tags, that data just sits there. Because the plugin is not blocking database access, developers can also build deeper links for teams that want more custom automation around lead scoring.
I should admit something here. Many small teams never touch advanced CRM fields, even when they say they want them. They care more about seeing who saved what yesterday than about a perfect scoring model. Self-hosted data still helps, though, because when you finally hire someone to fix the mess, the raw clicks and saves are already stored locally.
- WordPress forms tied to MLSimport listings can send leads to CRMs using simple webhooks.
- Theme CRMs can sync saved-search contacts and notes into external tools like HubSpot.
- Local data lets you tag leads in the CRM with search area or price band.
- Hosted IDX APIs are less direct because they keep click history inside their own dashboards.
FAQ
Can MLSimport create saved searches and favorites on its own without a special theme?
MLSimport does not create saved searches or favorites by itself and relies on your theme or add-ons for that.
The plugin’s job is to bring MLS listings into WordPress as clean, synced property posts. To let visitors save searches, mark favorites, or see a dashboard, you need a compatible real estate theme or a dedicated account plugin. That design keeps the data engine lean while you pick the exact user interface and features you want on top.
How hard is it for a non-technical admin to change saved-search email content on an MLSimport site?
Editing saved-search email content on an MLSimport-based site is usually a simple settings-panel task.
With themes like WPResidence, admins can change the email subject, intro message, and logo from the WordPress dashboard, with no code. The template pulls in matching properties automatically, so staff only touch the text and branding fields. As long as someone on the team is comfortable in wp-admin, keeping alerts on-brand is a short task, not a development project.
What happens to saved searches and favorites if I change themes but keep MLSimport active?
Saved searches and favorites may need migration when you change themes, but your MLSimport data stays intact.
Saved-search logic and favorite storage belong to the theme or account plugin, not to MLSimport, which only handles listings. If you switch themes, you keep all the property posts, but user-facing features might store data in different tables. In practice, that means you either run a one-time data migration or ask users to recreate searches, while the plugin keeps your MLS feed running the whole time.
Is day-to-day alert management easier with an MLSimport plus theme setup than with a fully hosted IDX?
Day-to-day alert management is often easier with an MLSimport plus theme setup because everything runs inside WordPress.
On a hosted IDX, you log into a separate vendor dashboard to edit alert settings, templates, and user lists. With MLSimport powering data in WordPress, you manage alert frequency, wording, and design from the same admin you use for pages and posts. For many teams, having one login and one stack cuts training time and makes small tweaks much faster to roll out.
Table of Contents
