Case Study: Keyword MLS Search on WordPress for The Tri-Cities

Buyers rarely search the way MLS forms expect. They type ocean view, hot tub, or a half-remembered street — not a checkbox for SpaYN. On a busy Tri-Cities brokerage site, that gap turned property search into a filter maze: city and price worked, but lifestyle language bounced off stock WordPress and raw listing meta.

That is the problem we solved on thetricities.ca with the official Seekmodo Search for WordPress plugin, wired into their existing MLS property search UI.

The human problem

Shoppers and agents on the site kept hitting the same friction:

“I know there are inlet-view homes in Port Moody — why does search ignore ‘ocean view’?”
“Hot tub, suite, waterfront — those live in remarks and feature fields, not the filter row.”
“I still need city, neighbourhood, beds, and map polygons. Keyword search cannot replace those.”

Native WordPress ?s= was never going to index roughly 1,900 active listings the way a real-estate SERP needs. A pure MLS filter form was not going to understand natural language either. The site needed both.

Why stock WordPress search failed here

Core search is a SQL LIKE over posts and pages. MLS inventory on The Tri-Cities is a custom property experience: reciprocity listings, neighbourhood polygons, buy/sell and active/sold toggles, list vs map. Dumping that into the default search template would have broken the product surface buyers already trust.

We needed the official Seekmodo WordPress connector in the content vertical — paired to a production tenant — plus a thin site bridge that enriches each listing for keyword recall and feeds ranked IDs back into the theme’s property search.

What we changed

Production runs Seekmodo Search from seekmodo.com/plugins/wordpress (folder seekmodo/), alongside a small seekmodo-tri-mls bridge for indexing and hybrid query.

Keyword-first search bar — address, MLS® #, or lifestyle phrases sit above city and neighbourhood, with typeahead as shoppers type.
Hybrid SERP — Seekmodo ranks matching listing IDs; TRI keeps city, neighbourhood polygons, price, beds/baths, dwelling type, sort, and map/list chrome.
Feature-aware indexing — view, waterfront, pool, spa/hot tub, and suite signals expand into searchable aliases so ocean view and hottub both land.
On-brand powered-by — a compact Seekmodo mark under the form so the brokerage UI stays primary.

The Tri-Cities search bar with ocean view keyword, Port Moody city filter, and Powered by Seekmodo branding — Keyword + city on production — “ocean view” in Port Moody, with Seekmodo under the form.

Port Moody ocean view listing cards with prices and photos — Twenty-five Port Moody matches for ocean view, still in the familiar listing cards.

Map view of Port Moody with clustered ocean view listings inside the city polygon — Same hybrid query on the map — Port Moody polygon with clustered pins.

Hot tub keyword search results in Port Coquitlam with Seekmodo branding — Port Coquitlam “hot tub” — lifestyle language, not only checkbox filters.

What it feels like now

Shoppers type the words they actually use. Ocean view in Port Moody returns inlet and view-forward stock. Hot tub in Port Coquitlam narrows to spa-capable homes without abandoning neighbourhood or price. Filters-only browsing still works when nobody needs a keyword. Search stopped being “forms or nothing.”

Try the pattern

Live site: thetricities.ca/search. Product path: Seekmodo for WordPress, pricing, and the connector at seekmodo.com/plugins/wordpress.

FAQ

Is this the official WordPress plugin?

Yes. Production uses Seekmodo Search from the official Seekmodo WordPress package (Plugin URI on seekmodo.com). A small MLS bridge handles listing enrichment and hybrid ID merge; it does not replace the connector.

Do MLS sites need WooCommerce?

No. The content vertical indexes WordPress posts and custom listing payloads. WooCommerce is optional when you also sell products.