Go Search Property — Philippine Real Estate Portal
A property marketplace for buying, renting, pre-selling and foreclosed homes across the Philippines, in the spirit of Lamudi, Dot Property and Property Finder. Built with Next.js, Tailwind CSS and PostgreSQL/PostGIS.
Homepage layout. This screenshot was taken offline, so the hero shows the illustrated fallback; with an internet connection it shows the photographs.
Features
Homepage
- Rotating hero of professional photographs (El Nido, BGC, Batad rice terraces, Mayon Volcano, Chocolate Hills)
- Search panel with Buy / Rent / Pre-selling / Foreclosed, location suggestions from the location tree (understands aliases such as "BGC"), and a compact version on phones
- Destination cards, featured developer slots (empty until partnerships are signed), latest listings, "Buying from abroad" and a financing section
Search (/search)
- Shareable URL filters: transaction type, location (a province or city includes everything inside it), property type, price, bedrooms, condos open to foreign buyers, sort
- "More filters" drawer, empty state, loading skeleton
- Interactive Philippines map (Natural Earth outline) with clustered peso pins, zoom-on-cluster and a preview card; full-screen map on phones
Property page (/property/[slug])
- Photo mosaic and full-screen viewer, key facts in sqm and ₱/sqm, pre-selling payment terms or foreclosure details, amenities, nearby places and a map
- Pag-IBIG and bank amortization calculator with published rates by fixing period, the ₱6M Pag-IBIG cap, and sources and dates
- Sticky agent card with PRC/DHSUD licence, Viber, WhatsApp, call, and an inquiry form with Data Privacy Act consent; "Request sample computation" fills the form from the calculator
- Schema.org
RealEstateListing data and social preview images
Agent dashboard (/dashboard): leads by channel (Viber, WhatsApp, inquiry, sample computation), latest leads including overseas buyers, listings with quality score and promotion
Calculator (/calculator): standalone Pag-IBIG vs bank comparison
International buyers: prices in pesos with an estimate in 12 currencies (Bangko Sentral ng Pilipinas reference rates, dated), foreign-buyer badges and a sourced explainer of ownership rules
Lead routes: GET /api/ph/leads/viber and /whatsapp record the lead (ignoring crawlers and repeat taps) and open the chat (WhatsApp with a pre-filled message); POST /api/ph/leads accepts JSON only, validates every field, rate-limits by hashed IP, drops bot submissions and logs events without personal data. Inquiries are saved to the Lead table before the buyer sees "sent"; with no database a production server answers 503 rather than losing them. GET /api/health is the uptime check and pings the database.
Security and privacy: Content-Security-Policy, HSTS and other security headers on every page; the agent dashboard is locked with DASHBOARD_USER / DASHBOARD_PASSWORD; rate limits are shared across servers through Postgres; erase_user() and purge_old_leads() handle Data Privacy Act erasure requests and the 24-month retention period; a draft privacy notice is at /privacy (fill in the highlighted details and have it reviewed). Set LEAD_IP_SALT, DASHBOARD_USER, DASHBOARD_PASSWORD and NEXT_PUBLIC_SITE_URL in production
Data model (prisma/schema.prisma, 20 models), see docs/data-model.md: locations from Region to Barangay, properties in PHP and sqm for sale, rent, pre-selling and foreclosure, developers and projects with DHSUD License to Sell, RESA-licensed agents, hero banners, leads, saved searches and financing programs, with database CHECK rules and PostGIS triggers
Screens
| Search with map | Property page |
|---|
| |
| Agent dashboard | Mobile |
| |
Tech stack
- Next.js 16 (App Router, Server Components, Cache Components) and TypeScript
- Tailwind CSS 4, lucide-react icons, Motion for animation, self-hosted fonts
- PostgreSQL + PostGIS on Supabase, schema in Prisma 6, queried with
pg
- Supabase Auth for agent sign-in, Supabase Storage for listing photos
- Hosted on Vercel (region
dub1); client preview on GitHub Pages
Getting started
Requires Node.js 20 or later.
npm install
cp .env.example .env.local
npm run dev
Open http://localhost:3000. The homepage runs on sample data, so no database is needed to try it.
Database (Supabase)
The production database is the Supabase project uyfiidwrmytdugzcjjzo (organization "Go Search Property"). It already has the full schema, the listing rules, the audit log, the privacy functions, the daily retention job and the reference data (82 locations, 21 amenities, 5 hero backgrounds). Browser keys have no access: every table has row-level security and no grants, and the website talks to Postgres only from its server.
To recreate it on a new project, run these in order (Supabase SQL editor or psql):
prisma/migrations/0_init/migration.sql # tables, enums, indexes (PostGIS in the extensions schema)
prisma/migrations/1_foreign_key_indexes/migration.sql
prisma/sql/supabase-security.sql # row-level security, revoke browser-key access
prisma/sql/postgis.sql # geo triggers, listing rules, audit log, erase_user(), purge_old_leads()
prisma/sql/retention-job.sql # daily retention job (pg_cron)
npm run seed:sql > seed.sql # reference data as SQL, then run seed.sql
Then mark the migrations as applied so Prisma Migrate takes over from here:
npx prisma migrate resolve --applied 0_init and npx prisma migrate resolve --applied 1_foreign_key_indexes.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
