Tampa4U Search
The brokerage's main property site, and the newer of its two search apps: the same MLS inventory and URL scheme as Tampa MLS rebuilt on PHP 8 with Turbo page transitions, a map view and filters buyers here actually use - flood zone, community, days listed, price updates.
Overview
Tampa4U Search is the brokerage's main site and the newer of its two property search apps: the same MLS inventory and the same URL scheme as Tampa MLS, rebuilt on a current PHP 8 runtime with Hotwired Turbo page transitions, so moving between search results, listings and content pages happens without full reloads.
The search is wider than its predecessor's. On top of price, beds, baths, size and property type, a buyer can filter by flood zone, community, days on the market and recent price updates, switch between list and map views, and choose 12, 24, 48 or 72 results per page. Listing pages carry schema.org JSON-LD - the residence with its coordinates, an FAQ block and breadcrumbs - so a listing can be read by search and answer engines rather than only by people.
Around the search sits the content layer a local brokerage sells on: city pages for Tampa, St. Petersburg, St. Pete Beach, Riverview, Odessa and Tierra Verde, community pages, condos, golf and featured listings, and the explainers Florida buyers actually ask about - HOA, CDD districts, homestead exemption, demographics and buyer tips. Accounts, favorites and saved searches carry over from the shared member layer.
The Tampa Bay buyer market is not monolingual, and the site is not either: Spanish, Ukrainian and Russian versions live on their own subdomains and are declared to search engines with hreflang.
What was built
- A PHP 8 search application serving the same path-based search URLs and MLS-number listing URLs as the older site, so existing links and bookmarks keep working.
- Hotwired Turbo navigation over server-rendered pages: the speed of a single-page app without becoming one.
- A wider filter set - flood zone, community, days listed and price updates alongside the standard criteria - with list and map views and 12 to 72 results per page.
- schema.org JSON-LD on listing pages: SingleFamilyResidence with GeoCoordinates, an FAQPage block and BreadcrumbList.
- A local content layer: city and community pages, condos, golf and featured listings, agent pages, and buyer explainers covering HOA, CDD, homestead exemption and area demographics.
- Member accounts, favorites and saved searches on the shared member layer, and lead capture straight to the agent team.
- Spanish, Ukrainian and Russian versions on their own subdomains, cross-declared with hreflang.
- Hashed asset bundles (plugins and application code) served through Cloudflare, so a deploy invalidates caches by filename rather than by guesswork.
Stack
Frontend
- Hotwired Turbo 8
- Page transitions without full reloads across search, listings and content pages
- Semantic UI
- Cards, modals, dropdown filters and forms, carried over from the earlier site
- Hashed asset bundles
- plugins.<hash>.js and main.<hash>.js, cache-busted by filename
Backend
- PHP 8.2
- Server runtime of the site, per its response headers
Infrastructure & DevOps
- Cloudflare
- The site and its language subdomains are served through Cloudflare
Integrations
- MLS listing data
- Property facts, photos and schools behind every search card and listing page
- Google Maps + Street View
- Map view over search results and a street-level panorama on listing pages
Content & SEO
- schema.org JSON-LD
- SingleFamilyResidence, GeoCoordinates, FAQPage and BreadcrumbList on listing pages
- hreflang
- Spanish, Ukrainian and Russian versions declared across the es, ua and ru subdomains
Engineering highlights
The same product line on two runtimes: the older site still answers on PHP 5.5, while this one runs PHP 8.2 - the rebuild moved the stack forward without breaking the URL scheme buyers and search engines already had.
Search state stays in the URL path, which is what makes filtered pages shareable, bookmarkable and savable as alerts.
Structured data is on the listing pages themselves, so a home's address, size and coordinates travel with the link into search results and AI answers.
Three extra languages are a market decision, not a plugin: Tampa Bay's Spanish, Ukrainian and Russian speaking buyers get their own indexed versions.