Yes, you can map MLS fields to custom fields in WordPress and use them for filters, taxonomies, and advanced search tuned to San Francisco neighborhoods and property types. With MLSimport, MLS data comes in as real WordPress fields you can rename, hide, and connect into your theme’s search tools. That means you pick which MLS fields power SF specific filters like neighborhoods, condos, TICs, and luxury homes without touching core plugin code.
Before you touch any code, how exactly does MLSimport handle field mapping in WordPress?
You can choose, rename, and hide MLS fields before they show up on your WordPress site.
Inside MLSimport, every connected MLS(Multiple Listing Service) board exposes a mapping screen with many RESO based fields you can manage. The plugin lets you flip each field on or off, so only the data you care about lands in WordPress. That keeps your San Francisco site focused and lighter, instead of dragging in every obscure MLS column you’ll never show to users. At first this seems like a small gain. It isn’t.
After you pick fields, MLSimport saves them as post meta attached to the property custom post type used by your theme. In practice, “ListPrice”, “BedroomsTotal”, “BathroomsFull”, “LivingArea”, and more become standard WordPress custom fields. You can then connect those fields into page templates, map widgets, and search panels without hacking the plugin core or your MLS feed.
The mapping UI also lets you relabel fields and mark some as private so they never display on the front end. For example, you can rename “MLSAreaMajor” to “District” for a friendlier San Francisco label, and keep “Agent Remarks” hidden for back office only. The plugin still imports the data for admin use, but your public pages stay clean and consistent with local MLS rules most of the time.
- You can turn single MLS fields on or off before import to control database size.
- Every imported MLS field is stored as WordPress post meta under the property post type.
- Field labels can be renamed so RESO technical names turn into human friendly terms.
- Marking a field as private keeps it in admin while hiding it from visitors.
How can I map MLS fields into custom fields, ACF, and theme taxonomies?
Imported listing data can fill both native theme fields and any extra custom fields you define.
Core RESO fields like city, state, postal code, and property type can map into your theme’s taxonomies. MLSimport uses these standard fields to feed things like “City”, “Neighborhood or Area”, and “Property Type” terms so your archives and filters match your design. That helps on San Francisco sites where you may want separate archives for condos, TICs, single family homes, or multi unit buildings.
The plugin can also route extra MLS attributes into theme custom fields or Advanced Custom Fields (ACF) groups you set up. For example, you might push “LotSizeSquareFeet”, “ViewYN”, and “WaterfrontYN” into ACF fields and then show them as badges or filter options. Because MLSimport writes data into standard post meta, compatible themes and tools can pick it up without custom code most of the time.
With themes like WPResidence 5.2+ and similar, ACF fields attached to the property post type are auto detected and can show in templates or search. That means you can create a custom ACF group called “Investment Metrics” for cap rate or rent to price ratios and keep it beside MLS driven data. Fields you add yourself that aren’t tied to MLSimport mapping, such as manually entered investor numbers, aren’t overwritten during sync, even when the plugin updates listings hourly.
| Data source | Mapped WordPress target | Common San Francisco use |
|---|---|---|
| RESO PropertyType | Theme property type taxonomy | Split condos TICs single family multi unit |
| RESO City and State | Location taxonomies | Limit searches to San Francisco listings |
| MLS Area or SubArea | Custom Neighborhood taxonomy | Tag properties with SF districts or micro areas |
| ListPrice and BedroomsTotal | Custom fields or ACF fields | Price sliders and beds filters in search |
| HOA Fees and ViewYN | ACF extra meta fields | Filters for low HOA condos and view homes |
The table shows how standard RESO fields flow into taxonomies and custom fields you control. Once mapped through MLSimport, that structure lets you build targeted SF niche pages like “Pacific Heights condos with views and low HOA” using your theme tools and ACF. No custom importer code needed in most setups.
How do I build San Francisco neighborhood and micro‑market filters with MLSimport?
Neighborhood taxonomies can pull from MLS location data and then be refined by hand for SF micro markets.
When your board supports RESO Web API, the feed can include location data like city, area, postal code, and often coordinates. MLSimport pulls those fields into WordPress so your theme can form location taxonomies that match how you talk about San Francisco. That gives you the raw material for “San Francisco” city filters, “94110” zip filters, and map searches focused on the core city instead of the whole Bay Area.
You can map MLS Area or Sub Area into a custom “Neighborhood” taxonomy that mirrors real SF districts. For instance, you might map certain MLS areas to terms like “Noe Valley”, “Mission Dolores”, “Pacific Heights”, or “Outer Sunset”. The plugin’s mapping keeps these as structured taxonomy terms instead of loose text, which means your search and archive pages can use them as exact match filters. Sometimes mapping takes trial and error, and that’s normal.
Where your MLS doesn’t provide clear neighborhood names, you have two options. Assign neighborhoods by hand in the WordPress editor, or write a script that tags listings by coordinates or postal code rules. MLSimport keeps your custom neighborhood taxonomy separate from MLS synced fields, so those manual tags survive routine listing updates. After that, WordPress archives, menus, and theme widgets can expose these neighborhoods as clickable filters and landing pages for each micro market, even if the setup felt messy while you tuned it.
What’s the best way to turn mapped fields into advanced search and front‑end filters?
Once fields are mapped, your theme’s search builder can expose them as targeted front end filters.
MLSimport handles the data layer by filling custom fields and taxonomies, and your real estate theme turns those into search controls. In practice, you pick which fields power dropdowns, sliders, and checkboxes, such as price, beds, baths, HOA dues, or “ViewYN”. Most modern themes let you do this in their options panel, so you rarely need custom PHP to wire up the filters. Some sites still add code, but that’s usually for edge cases.
Any imported field stored as post meta can support a filter when the theme knows how to read it. On compatible setups, ACF backed fields attached to the property post type can also appear in search without extra coding. That makes it easy to add SF focused filters like “Neighborhood”, “Condo vs TIC”, or “Parking included” just by mapping the MLS fields correctly and then enabling those fields in the theme’s search builder. Earlier it might seem like field names don’t matter, but they do.
How does RESO Web API support cleaner mapping and performance for San Francisco sites?
Using standardized RESO fields can reduce the work of mapping multiple MLS feeds into one site.
The RESO Data Dictionary defines shared names such as “ListPrice”, “BedroomsTotal”, and “BathroomsFull” that stay consistent across many Bay Area MLSs. MLSimport connects over the RESO Web API and pulls normalized JSON data, which is cleaner to map than older RETS feeds. That uniform structure means your San Francisco site can reuse one mapping design across multiple boards instead of building unique setups for each feed.
Standardization also helps performance and stability, because the plugin handles one predictable field layout even when you join SFAR data with nearby MLS coverage. With consistent names and types, your WordPress database can stay organized, and search queries against mapped fields can run more efficiently. For a city site handling thousands of listings, that cleaner data model helps advanced filters and map search stay fast for visitors.
FAQ
How often does MLSimport sync new and updated listings into my WordPress site?
MLSimport typically syncs new and updated listings on an automated hourly schedule as a general rule.
The plugin connects to the RESO Web API and runs regular pulls so San Francisco listings stay close to real time. You can usually tune the sync frequency within safe limits agreed with your MLS board. Because data is stored in WordPress, visitors still see the last synced listings even if the MLS API goes offline for a bit.
Do MLS listing images slow down my San Francisco WordPress site with MLSimport?
Images are usually served from the MLS CDN, which keeps your server lighter while still loading fast for users.
MLSimport links to the MLS hosted photos instead of copying every file onto your hosting account. That approach can save many gigabytes of storage when you handle thousands of listings. The plugin still outputs proper image tags with titles and alt text, so your property pages stay SEO friendly without a heavy media library on your own server.
Can I keep sensitive MLS fields private while still importing them for back‑office use?
Sensitive fields like “Agent Remarks” can be imported as private meta so they never appear on public pages.
Inside the mapping UI, MLSimport lets you flag certain fields as private while still storing them as post meta. That setup is useful for internal notes, showing remarks or showing instructions only to logged in staff in the WordPress admin. You stay within MLS rules by not publishing fields that should stay restricted, yet you keep them handy for your team.
Does MLSimport work with Bay Area MLS boards and cross‑region projects?
MLSimport supports many MLSs across the U.S. and Canada, including major Bay Area boards using RESO APIs.
Because the plugin relies on the RESO Web API and Data Dictionary, it can normalize fields from different MLSs into one schema. That makes it realistic to run a San Francisco focused site that also shows nearby Marin or Peninsula listings on shared templates. You map the fields once, then let the standardized feed handle the regional quirks in the background.
Table of Contents
