How does IDX lead capture work on WordPress?

Last updated: June 14, 2026

By Elena Stavros, IDX Integration Specialist. 8+ years configuring WordPress real estate sites with MLS data feeds and CRM automation; contributor to WPResidence documentation.

You built IDX lead capture on your WordPress site and spent real money driving traffic to your listing pages. A buyer clicks Request Info, types out a question about the three-bed on Main Street, and hits send. So where does that inquiry actually go? If you can’t answer that with confidence, you’re probably leaking leads, and you’re far from the only agent who is.

Here’s the short version. MLSImport pulls your MLS listings into WordPress as native property posts on your own domain, so they live at clean URLs like yoursite.com/property/123-main-st. The plugin itself has no lead form and no CRM. The capture happens in your theme (WPResidence is the easiest path) and the form plugins you already run, and the MLS CRM integration happens through one of three routes: WPResidence’s native HubSpot key, a form-plugin add-on, or a Zapier or Make webhook.

A buyer fills out the Request Info or Schedule a Tour form, and the lead lands in your CRM in under a minute, tagged with the property address and price. That’s how IDX lead capture on WordPress works in a nutshell: you own the page, you own the form, you own the lead, and you pay $49/month instead of a hosted IDX vendor’s $75 to $100-plus. The rest of this guide shows you exactly how each piece fits.

What this guide covers

1. Does MLSImport capture leads on its own?
2. Built-in IDX lead capture on every property page
3. Three paths to connect MLS leads to your CRM
4. Agent and team lead routing
5. Forced registration, saved searches, and price alerts
6. Lead ownership and portability
7. How MLSImport compares to hosted IDX for lead capture
8. Neighborhood and niche pages as lead funnels

Does MLSImport Capture Leads on Its Own?

MLSImport does not include a built-in lead form or CRM. It is a data import engine that pulls RESO Web API listings into your site as native WordPress “property” posts and keeps them synced hourly by default (you can adjust that schedule down to roughly 15 minutes if your hosting and cron can handle it). It does not render inquiry forms. It does not store, score, or manage leads. If you came here expecting a lead inbox baked into the plugin, that’s the one thing it deliberately leaves alone.

So how does anything get captured? Through a clean division of labor. Think of it as three layers, each doing one job:

1. MLSImport imports your MLS data and keeps it in sync.
2. Your theme (WPResidence, for the smoothest setup) renders the property pages, the contact and tour forms, the agent assignment, and a small built-in CRM.
3. Your CRM, form plugin, or Zapier handles lead storage, routing rules, and nurture sequences.

Here’s why this matters more than it sounds. Because your listings are real posts on your own domain, any form plugin you already pay for can sit right on the same page. No iframe walls. No vendor subdomain holding your leads hostage. The connection path is always the same: listing page, then form, then CRM or email tool, with MLSImport simply providing the property page itself. Get that mental model straight and every other decision in this guide gets easier.

Built-in IDX Lead Capture on Every Property Page

If you pair MLSImport with WPResidence, you get a working property inquiry form on day one. You don’t bolt on a third-party form plugin to get started, and you don’t touch a single listing by hand. The moment a listing syncs in, it inherits the same lead-capture furniture your manual listings already use.

Request Info and Schedule a Tour Dual Tabs

WPResidence ships a dual-tab widget, “Request Info” and “Schedule a Tour,” on every property page template. Because MLSImport creates standard WordPress property posts, your imported listings pick up that widget automatically the instant they sync. There’s no per-listing setup, ever.

The Schedule a Tour tab collects the date and the visit type (in-person or virtual). Every label is editable from theme options, so you can rename “Contact agent” to “Talk to our team” without a developer, and there’s no vendor branding forced onto your form. The form is mobile-friendly, and a buyer never needs an account to submit it.

The part that makes this useful for routing: hidden fields automatically pass the listing context into every submission. Listing ID, MLS ID, property URL, address, price, beds, city, and the agent slug all ride along quietly. So when a lead hits your CRM, it already knows which house the person was looking at and what it costs.

Why High-Intent CTAs Matter for Lead Quality

Now for the trade-off nobody tells new agents. A Schedule a Tour submission is rarer than a generic “Request Info” or “Ask a Question” click, but it carries far more weight. Someone asking to step inside a specific home has moved much closer to a decision than someone who clicks “Ask a Question,” so tour requests tend to be your highest-intent leads even though they arrive in lower volume. There isn’t a clean home-sales conversion multiple to hang on that, so treat it as a quality signal rather than a fixed number: the buyer who wants to walk the property is usually the one worth calling first.

Response time is the other half of the equation. Agents who treat tour requests as high priority aim to reply within 5 to 10 minutes, and within 30 minutes for info or question leads. The lesson is simple: more CTAs means more raw volume, but prioritizing the tour tab means fewer, far better conversations.

My honest take? Run both tabs. Let your CRM segment by submission type, and protect your sub-10-minute response window for tour leads like it’s a listing appointment. Get started today: open your WPResidence property page templates and confirm the Schedule a Tour tab is toggled on.

Three Paths to Connect MLS Leads to Your CRM

This is the part you actually came for. There are three ways to set up MLS CRM integration on your WordPress site:

1. Native HubSpot integration via WPResidence theme options.
2. Form-plugin add-ons (Gravity Forms, WPForms, and the rest).
3. Zapier or Make webhooks that fan a single submission out to many destinations.

Pick based on where your leads already live and how much routing logic you need. Here’s how each one works in practice.

Path 1: Native HubSpot Integration via WPResidence

This is the fastest route, and it’s hard to beat for solo agents and small teams. Paste one HubSpot private app API key into WPResidence theme options, and every property, agent, and contact form submission becomes a HubSpot contact with the property URL and full listing details attached. Setup runs under an hour.

The standout feature is per-agent HubSpot keys. Each agent on your team pastes their own key into their WordPress user profile, so leads from their assigned MLSImport listings flow into their personal HubSpot account instead of a shared inbox. Picture 10 agents, 10 separate HubSpot spaces, one shared MLS feed. That’s the whole setup.

Don’t have HubSpot, or don’t want it yet? WPResidence ships a built-in WordPress CRM dashboard at no extra cost. It logs every inquiry as a lead tied to the property URL, with a status, notes, and a follow-up timeline. The broker sees all the leads, while each agent sees only their own. For a solo agent or a small team, that’s often enough to run your whole pipeline before you ever connect an outside CRM.

Path 2: Form-Plugin Add-ons

Already married to a form plugin? Good news: the property template plays nice with all the usual ones, Gravity Forms, WPForms, Contact Form 7, Elementor Forms, and Ninja Forms. Each has CRM-specific add-ons or native integrations.

Through this path you can reach Follow Up Boss, LionDesk, kvCORE, Chime, Zoho, Salesforce, Mailchimp, ActiveCampaign, and ConvertKit, among others. The trick most people miss: those hidden listing fields (listing ID, address, price, agent slug) are already available as merge tags inside Gravity Forms and WPForms. Map them into your CRM’s “notes” or “deal name” field, and your leads segment themselves by property and price the moment they arrive.

Path 3: Zapier, Make, and Webhooks

When you want one submission to do five jobs, this is the path. A form fires a webhook, Zapier (or Make, formerly Integromat) catches it, and routes it to any of more than 5,000 apps from a single trigger.

Here’s the scenario that sells it. One property-form submit can simultaneously create a CRM contact, push a row to Google Sheets, ping a Slack channel, fire an SMS through Twilio or ClickSend, and email your inbox, all in under a minute. You set it up once and forget it.

This is also where price-based routing gets fun. Teams have wired rules like “price over $2.5 million goes to the founding partner and the concierge desk pipeline” and “anything over $1,000,000 goes to the luxury pipeline,” all from a single form feed. The webhook reads the hidden price field and sends the lead exactly where it belongs.

Pro tip: You can run more than one import task off the same MLS connection. If a single neighborhood is your bread-and-butter area, set that area’s task to sync about every 15 minutes while you leave the rest of your inventory on the default hourly schedule. New listings in your hottest zone then hit your saved-search prospects almost as fast as the big portals do.

Agent and Team Lead Routing

On a team site, the right lead has to reach the right agent without anybody babysitting it. The good news is that the MLS feed already carries the data you need to make that happen automatically.

How a Single Agent’s Contact Box Follows an Imported Listing

The RESO feed already carries everything the theme needs. MLSImport reads the agent and office fields straight from the RESO feed, the ListingAgentMlsId, ListingAgentFullName, ListOfficeName, and ListOfficeMlsId, and stores them as standard WordPress post meta. Your RESO Web API feed becomes the source of truth, and the theme maps those IDs to WordPress agent profile posts.

The result is tidy. Agent profile pages auto-populate with that agent’s live MLS listings and refresh about an hour after any MLS change. The contact box on each listing page shows the assigned agent’s photo, name, and email, even on listings that belong to another brokerage. And the lead notification routes to that agent’s address, not a shared team inbox, unless you want shared routing, which is fully configurable.

CRM Routing Rules for Teams (Price, Area, Agent ID)

Once leads hit your CRM, three kinds of routing rules cover almost every team setup:

1. Price-band rule: if price is over $800,000, send it to the luxury team pipeline.
2. Agent-identity rule: if the MLS agent ID matches Agent A’s profile, keep the lead with Agent A.
3. Round-robin rule: if the ListOfficeMlsId doesn’t match your company ID, drop it into a buyer-rep round-robin.

The per-agent HubSpot key is the capstone here. Ten agents, ten HubSpot spaces, one shared MLSImport feed means each person’s leads land in their own account with zero manual sorting. Delivery speed holds up across every path too: because the form fires the webhook or CRM add-on the moment it’s submitted, the lead reaches the CRM in real time rather than waiting on the next listing sync.

And because all this automation lives outside the plugin, you can change your routing strategy any time without re-importing a single listing. Decide tomorrow that luxury starts at $1M instead of $800K? Edit the rule, done. Ready to wire this up? Write down your three routing rules in plain English first, then build them in the CRM, never the other way around.

Forced Registration, Saved Searches, and Price Alerts

Form submissions are the leads you can see. The next three mechanisms work while you sleep: soft-gating your traffic, capturing search intent, and re-engaging prospects with alerts. None of these live in the plugin, by the way, they’re theme and plugin features sitting on top of your imported data.

Forced Registration: Volume vs Quality Trade-Off

WPResidence includes a Zillow-style login and registration modal that you can trigger on almost any event: saving a search, viewing the Nth listing, or scrolling to a certain depth. A common playbook is to allow 3 to 5 free property views (sometimes up to 10 to 20 in lower-intent markets) before the modal fires, often after the third page view or 50% scroll on a listing.

In practice, teams that let visitors browse a few listings (around 3 to 5) before the registration modal fires, then follow up with a saved-search confirmation email, tend to collect better-qualified leads than teams that hard-gate on the very first page view. A softer ask keeps more serious buyers in the funnel.

Now the honest tension. Hard forced registration gets you more raw leads, but a bigger share of them are fake or low-intent, throwaway emails just to see the photos. Softer prompts paired with richer forms tend to produce better-qualified leads once a normal follow-up cycle has had time to play out. Which is right? It genuinely depends on your market and your follow-up capacity. A high-volume buyer team can absorb the junk; a solo luxury agent usually can’t. Run the experiment on your own traffic before you commit.

Saved Searches, Favorites, and Email/SMS Alerts

WPResidence stores saved favorites and saved searches in WordPress user meta. When a new listing matches someone’s saved search, or a price drop hits a listing they’re watching, the theme captures and stores that intent, and your CRM or automation tool fires the alert email straight to that prospect. In practice, these alerts are some of the highest-intent re-engagement touchpoints you’ll ever send, because the person already told you exactly what they want.

This is where MLSImport’s sync cadence earns its keep. Because the feed updates hourly by default (and can be tightened to roughly 15 minutes), a fresh listing in someone’s saved-search area can trigger the alert within the same sync cycle. Speed is the whole point of an alert.

Want SMS instead of email? Wire it through Twilio or ClickSend on the same Zapier webhook path from Path 3. And here’s the compounding move: behavior signals like which listings someone viewed, how often, and in what price range can be passed into your CRM as contact properties through hidden fields or Zapier. Feed those into a score-based follow-up sequence and your nurture starts running itself.

Lead Ownership and Portability

This is the question hosted IDX vendors quietly hope you never ask. On a franchise or hosted IDX platform, your leads land in a corporate or vendor CRM, and when you leave, you may walk away empty-handed. With MLSImport on your own domain, leads go to your email, your database, your CRM, and they stay there. The plugin never inserts its own lead widget, never stores leads, and never charges a per-lead fee.

Keep the distinction clear: MLS display rules govern listing data, not the people who contact you. Your prospects’ contact details belong to you. The disclaimers and attribution affect what visitors see on the page, not what you do with an inquiry email.

Switching brokerages? You keep your domain, your pages, your SEO equity, and your existing leads. Usually only three to five things change: your logo, the broker name, the compliance disclaimer, the contact email, and the Office ID in the plugin settings. Re-point to the new RESO feed and you’re back in business.

And cancelling MLSImport doesn’t wipe your pipeline. New syncs stop and active listings should be retired for compliance, but already-captured leads stay in your CRM, and forms on existing pages keep firing. One responsibility comes with all that control: under GDPR and CCPA, you own the data, which means you also handle consent, access, and deletion requests (often inside a 30-day window). The plugin leaves consent collection in your hands, which is exactly where ownership lives. At $49/month against hosted IDX at $75 to $100-plus, you get the cost advantage and the control in the same package.

How Does MLSImport Compare to Hosted IDX for Lead Capture?

If you’re weighing MLSImport against a hosted or iframe IDX product, the comparison comes down to three axes where the evidence is clear: domain control, lead ownership, and CRM flexibility. Let me give you the fair version, including where hosted IDX actually wins.

On domain control, MLSImport listings live on your site, crawlable and accumulating value. Hosted IDX often fragments sessions across domains, which quietly breaks your GA4 attribution. On CRM flexibility, hosted IDX locks you into its built-in contact manager, while MLSImport plus a form plugin connects to anything.

Where does hosted IDX have the edge? Setup is genuinely faster, minutes versus the day or two an MLS board takes to approve your feed, and some platforms ship built-in lead nurture sequences out of the box. If you need to be live this afternoon, that’s a real advantage worth naming. The flip side is resilience: because your WordPress database holds the data and the forms, your inquiry forms keep working even during a feed outage, while a hosted widget can go dark with it.

Neighborhood and Niche Pages as Always-Fresh Lead Funnels

Here’s the part that compounds. Because MLSImport creates indexed WordPress posts, you can build neighborhood hub pages that query and display live listings by area, price band, property type, or any RESO field, and the inventory refreshes every sync cycle without you touching the page.

Match each page type to a lead magnet and you’ve got a funnel that runs on autopilot: a neighborhood page with a “Get new listings emailed to me” opt-in, a condo building page with a “Be first to know when a unit lists” alert, a niche page like “homes with pools” with a Request Info form.

The logic holds up in practice. When investors swap a static before-and-after gallery for live, MLS-backed pages, inquiries tend to climb, because the pages stay fresh, rank for far more long-tail searches, and give visitors a current reason to reach out. One Canadian investor, for example, leaned on “live opportunities” neighborhood pages as a durable alternative to paid advertising, using CREA-compliant disclaimer options. You don’t need a guaranteed percentage to see the pattern: live listing pages out-earn static galleries on both SEO and lead volume over time.

Because these are real posts, your SEO plugins work natively, no cross-domain session fragmentation muddying your GA4. Want this on your own site? Pick your single best neighborhood and build one hub page with an alert opt-in. Pair it with Yoast or Rank Math with WPResidence and let it start working.

Key Takeaways

1. MLSImport has no built-in lead form or CRM; it’s a data import engine, and WPResidence supplies the contact and tour forms on every property page.
2. WPResidence’s native HubSpot integration connects via a private app API key in under an hour, and each agent can use their own separate key.
3. A single inquiry can reach your CRM, a Google Sheet, a Slack channel, and an SMS in real time through one Zapier or Make webhook.
4. Tour-intent leads arrive in lower volume than generic Request Info clicks but signal higher buyer intent, so Schedule a Tour is usually your highest-value CTA and earns your fastest follow-up.
5. On a self-hosted MLSImport site all captured leads belong to you; cancelling the plugin or switching brokerages never transfers your contacts to a vendor.

Bringing It All Together

Here’s the thing to hold onto: MLSImport isn’t trying to be your lead machine. It’s the data pipeline that puts real, indexable listing pages on your own domain, and that’s exactly what lets your theme, your forms, and your CRM do the lead work the way you want it done. Wire up your preferred MLS CRM integration path, point the right lead to the right agent, and every IDX lead capture inquiry from now on lands somewhere you actually own.

Start with the path that fits your stack today, get one neighborhood page live, and build from there. Which CRM path did you wire up first, native HubSpot, a form-plugin add-on, or a Zapier webhook? Tell us in the comments and let your fellow agents learn from your setup.

Frequently Asked Questions

Does MLSImport include its own lead form or CRM?

No. MLSImport is a data import engine that brings MLS listings into WordPress as native posts and keeps them synced hourly by default. Lead forms and the CRM layer come from your theme and your existing tools. The WPResidence theme ships a Request Info and Schedule a Tour form on every property page, plus a built-in WordPress CRM dashboard and a native HubSpot integration that send those leads where you want them. That CRM option lives in the theme, not the plugin: the plugin itself never stores or manages lead data.

Can I legally capture leads on listings that are not mine?

Yes, under standard IDX rules. Most MLS boards let member agents display other brokers’ listings, with the required broker credit and disclaimer, and receive buyer-representation inquiries. You act as the buyer’s agent, not the listing agent. Every inquiry CTA on an MLSImport listing routes to you or your designated agent, never to the listing broker, while the required attribution text (listing office name and MLS copyright) still shows in the listing details.

How fast do MLS listing leads reach my CRM after someone submits a form?

Effectively in real time. The form submission triggers the webhook or CRM add-on immediately, so most setups deliver the lead to HubSpot, Follow Up Boss, or your inbox within moments of the visitor hitting submit. If your CRM endpoint is temporarily down, the plain email notification still fires as a backup, so no inquiry is lost. The MLSImport sync schedule (hourly by default) is unrelated to lead speed; form-to-CRM delivery happens regardless of when the listing last synced.

What happens to my leads if I cancel my MLSImport subscription?

Leads you’ve already captured stay in your CRM, because the plugin never holds your contact data. When you cancel MLSImport, new MLS syncs stop and active listings should be removed for compliance, but existing pages stay online and the forms on them keep firing. Any email or SMS alert automations connected to old listings also continue until you switch them off. Your lead database is entirely yours.

Which CRMs can I connect MLS leads to?

Effectively any of them. HubSpot has a native one-key integration through WPResidence theme options. Beyond that, the property template works with the major form plugins, and through their add-ons you can reach Follow Up Boss, LionDesk, kvCORE, Chime, Zoho, Salesforce, Mailchimp, ActiveCampaign, and ConvertKit, among others. And if a CRM has no direct add-on, a Zapier or Make webhook bridges a single form submission to more than 5,000 apps.

Do I have to use WPResidence, or will another theme work?

WPResidence is the smoothest path because it ships the Request Info and Schedule a Tour forms, a built-in WordPress CRM, native HubSpot support, and per-agent routing out of the box. But MLSImport creates standard WordPress property posts, so any theme plus any form plugin you already run can sit on the same page. WPResidence saves you the most setup; it isn’t a hard requirement for capturing leads.

Can each agent on my team use their own CRM account?

Yes. WPResidence supports per-agent HubSpot keys: each agent pastes their own private app key into their WordPress user profile, and leads from their assigned MLSImport listings flow into their personal HubSpot account instead of a shared inbox. Ten agents can run ten separate HubSpot spaces off one shared MLS feed, with no manual sorting. The broker still sees every lead in the built-in CRM dashboard, while each agent sees only their own.

Can I route leads automatically by price or area?

Yes, and this is where the Zapier path shines. Every submission carries hidden fields for listing ID, address, price, beds, city, and the agent slug, so your CRM or webhook can read those values and route accordingly. Teams wire rules like “price over $1,000,000 goes to the luxury pipeline” or “if the listing office ID isn’t ours, drop it into a buyer-rep round-robin.” Because the logic lives outside the plugin, you can change a price band any time without re-importing a single listing.

Which form plugins work with imported MLS listings?

The property template plays nicely with Gravity Forms, WPForms, Contact Form 7, Elementor Forms, and Ninja Forms. The useful detail: the hidden listing fields (listing ID, address, price, agent slug) are available as merge tags inside Gravity Forms and WPForms, so you can map them straight into your CRM’s notes or deal-name field and have leads segment themselves by property and price the moment they arrive.

Can I send lead alerts by SMS instead of email?

Yes. Wire the form through Twilio or ClickSend on the same Zapier or Make webhook path you’d use for CRM delivery. One submission can fire an SMS, create a CRM contact, push a row to Google Sheets, ping a Slack channel, and email your inbox at the same time, all in under a minute. The same webhook approach also delivers saved-search and price-drop alerts by SMS.

Does the lead tell me which property the buyer was looking at?

Always. WPResidence automatically passes the listing context into every submission through hidden fields: listing ID, MLS ID, property URL, address, price, beds, city, and the agent slug all ride along. So when the lead reaches your CRM it already knows which house the person viewed and what it costs, with no manual tagging on your end.

Will my lead forms keep working if the MLS feed goes down?

Yes. Because your WordPress database holds the property pages and the forms, your inquiry forms keep working during a feed outage, and the last synced listings stay live. This is a real edge over a hosted or iframe IDX widget, which can go dark entirely when the feed breaks. The MLS sync cadence and lead delivery are independent systems, so a paused feed never stops a form from capturing a lead.

What is forced registration, and should I turn it on?

Forced registration is a Zillow-style login modal, a WPResidence feature, that you can trigger on events like saving a search, viewing the Nth listing, or scrolling to a set depth. Hard-gating on the first page view gets you more raw leads but a bigger share of junk; letting visitors browse around three to five listings first tends to collect better-qualified leads. Which is right depends on your market and follow-up capacity, so test it on your own traffic before committing.

Do saved searches and price-drop alerts capture leads too?

Yes, and they’re some of your highest-intent touchpoints because the prospect already told you exactly what they want. WPResidence stores saved favorites and searches in WordPress user meta; when a new listing matches a saved search or a watched listing drops in price, your CRM or automation tool fires the alert. With MLSImport’s hourly sync (tightenable to roughly 15 minutes), a fresh listing can trigger that alert within the same sync cycle.

How much does MLSImport cost compared with hosted IDX?

MLSImport runs $49/month, against hosted or iframe IDX products that typically charge $75 to $100-plus, and it never adds a per-lead fee. You also keep the listing pages on your own domain, so they build SEO equity and feed clean analytics. The trade-off to name honestly: hosted IDX is usually faster to go live (minutes versus the day or two an MLS board takes to approve your feed), and some hosted platforms bundle lead-nurture sequences out of the box.

Can I keep my leads if I switch brokerages?

Yes. Your leads live in your CRM and your database, not a vendor’s contact manager, so a brokerage move never transfers them. You keep your domain, your pages, and your SEO equity. Usually only a handful of things change, your logo, broker name, compliance disclaimer, contact email, and the Office ID in plugin settings, then you re-point to the new RESO feed and you’re back in business.