# Feature Matrix & Synthesis — PH Property Portals

> Cross-competitor synthesis of the 14 teardowns in this folder. Read the per-competitor
> files for evidence and endpoint-level detail. This doc is the "what it means for us" layer.
> Compiled 2026-07-11. Our own design constraints live in `../../DESIGN.md`.

Legend: ✅ present · ◑ partial / gated / weak · ❌ not present · — not observed (couldn't confirm)

---

## Table A — Tech stack & data layer

| Portal | Category | Framework | Host / CDN | Listing data source | Structured data |
|---|---|---|---|---|---|
| **Homex** | Condo-mgmt SaaS + lead micro-site | Next.js (App Router, RSC) | Vercel (no CDN in front) | Client-fetched `/api/public/*` JSON (flat rows) | ❌ no JSON-LD |
| **Lamudi** | Major classifieds | Java / Jetty + web-component lib | AWS CloudFront | Multi-source ingestion; LIFULL Connect backend | ✅ RealEstateListing / BreadcrumbList |
| **MyProperty** | Major classifieds | Java / Jetty (same white-label as Lamudi) | AWS CloudFront | LIFULL Connect backend (same S3 bucket) | ✅ RealEstateListing / Offer / Breadcrumb |
| **Dot Property** | Major classifieds | Laravel + Blade (jQuery→Tailwind) | Cloudflare | LIFULL Connect backend (shared S3) | ◑ GeoCoordinates only |
| **OnePropertee** | Buyer-matching marketplace | Meteor.js (DDP/WebSocket) | AWS CloudFront + WAF | Meteor DDP (no REST observed) | ◑ ImageGallery only |
| **Hoppler** | Brokerage marketplace | Node/Express SSR + React islands; Java API | Nginx + CloudFront + imgix | Base64-JSON in `<script>` tags; Java/Tomcat REST | ◑ Offer microdata on cards |
| **Filipino Homes** | Agent-network brokerage | Next.js (RSC/ISR) + MUI | Vercel behind Cloudflare | Laravel backend (`laravel.filipinohomes.com`) | ✅ per-listing JSON-LD |
| **Rentpad** | Rentals | Legacy jQuery / `.htm` routes | Cloudflare (aggressive bot-mgmt) | `/ws/*.htm` AJAX endpoints | ◑ microdata (Product/Offer), no JSON-LD |
| **Property Source** | Boutique brokerage | WordPress (OceanWP child) | Cloudflare | WP custom post types → HTML | ❌ none (only wp-json core) |
| **Presello** | Boutique brokerage | WordPress + Elementor + Toolset | nginx/Plesk + FlyingPress | Toolset CPT → HTML | ✅ Yoast RealEstateListing |
| **REAL.ph** | Newer marketplace + agent SaaS | Laravel + jQuery | Cloudflare; media on S3 (ap-southeast-1) | First-party Laravel DB | ✅ RealEstateListing + SearchAction |
| **Berenta** | Rentals | Laravel/Blade + jQuery/Semantic UI | nginx/PHP 8.2, no CDN | Laravel REST-ish (`/properties/{id}`) | ❌ none |
| **Carousell** | C2C marketplace (property vertical) | React SPA + Redux SSR hydration | Cloudflare; media on karousell.com | Redux `listingsMap` + smart-attributes bag | ◑ generic Product/Offer |
| **Aggregators** | Meta-search (Trovit/Mitula/Nuroa/Nestoria) | Mixed (Trovit K8s; Nuroa Java servlet) | nginx; Nuroa assets on GCS | Aggregate 3rd-party feeds; LIFULL Connect / Thribee CPC | ◑ varies; Nestoria API dead |

**The single biggest structural fact:** LIFULL Connect (Japan-listed 東証 LIFULL, the SUUMO-adjacent group)
now owns **Lamudi, MyProperty, Dot Property _and_ all four aggregators** (Trovit/Mitula/Nuroa/Nestoria).
Proven by shared S3 buckets (`prd-lifullconnect-backend-b2b-images`, `prd-lifullconnect-projects-admin-images`),
a shared CPC backend (Thribee), a shared AdSense publisher ID, and Nuroa's redirect literally routing through
`lifullconnect.com/fakeAdUrl`. Practically, ~half the "market" is one company. That both validates the
SUUMO-model thesis for the client and means our real differentiation is **JP-buyer focus**, not raw listings.

---

## Table B — Feature inventory

| Portal | Search filters | Map | Saved search / alerts | Favorites | Lead contact | Auth | Monetization | i18n / currency | App |
|---|---|---|---|---|---|---|---|---|---|
| **Homex** | ◑ city/building/unit-type/tag | ❌ | ❌ | ❌ | Telegram button | ✅ 4-role | B2B SaaS (inf.) | ◑ EN/ZH toggle, PHP only | — |
| **Lamudi** | ✅ deep (price/bed/bath/area/72 amenities/geo) | ✅ SERP map | ◑ gated behind login | ◑ | phone-reveal + WhatsApp/Viber/Messenger | ✅ +Google One Tap | ✅ ads + bank-loan affiliate + premium agency | ◑ switcher UI, PHP prices | — |
| **MyProperty** | ✅ deep (+days-since, foreclosure) | ✅ static→interactive | ✅ **price-drop alerts + web-push** | ✅ | phone/WhatsApp/Viber/Messenger | ✅ +Google One Tap | ✅ agency premium + dev leads | ◑ en_PH, PHP | — |
| **Dot Property** | ✅ (+furnishing/ownership/transport) | ◑ geo, no map script | ◑ `saveSearchCheck` email + OneSignal | ✅ | click-reveal + enquiry | ✅ +Google | ✅ GAM ads + featured + freemium upload | ◑ PHP/USD/AUD/EUR/GBP, `/lang/` | ❌ |
| **OnePropertee** | ✅ (+Pasalo/foreclosed/pre-selling, brokers-only) | ❌ | ❌ | — | **Buyer Assistance Officer** + visit scheduler | ✅ passkey/OAuth/passwordless | ◑ 50/50 commission share | ❌ EN/PHP only | ✅ PWA + Android |
| **Hoppler** | ✅ (10 types + amenities, pet-friendly) | ✅ Google Maps | ❌ | ◑ | **"Viewing List" batch-inquiry cart** | ✅ buyer vs broker | brokerage + partner-broker recruit | ❌ EN/PHP | ✅ iOS + Android |
| **Filipino Homes** | ✅ (+AI on/off toggle) | ✅ Google (nearby-office) | ◑ save listing only | ✅ | JSON-LD agent + Socket.IO live chat | ✅ +Google | brokerage + featured devs | ❌ en-PH/PHP | ✅ (press) |
| **Rentpad** | ✅ **rental-term (Daily/Short/Long)** + furnishing | ✅ Google Maps | ◑ favorites only | ◑ gated | inquiry + **multi-provider lead broadcast** | ✅ +Facebook | AdSense + free posting + lead-gen | ❌ EN/PHP | — |
| **Property Source** | ❌ static category links only | ◑ embed iframe | ❌ | ❌ | Contact Form 7 + Messenger chat | ❌ | brokerage lead-gen | ❌ EN/PHP (price as text) | — |
| **Presello** | ◑ location/type/price/sort (no bed/bath range) | ◑ detail-only pin | ❌ | ◑ login-gated "My List" | phone/WhatsApp/chat/"Book a Viewing" modal | ✅ Profile Builder | brokerage + AdSense | ❌ EN/PHP | — |
| **REAL.ph** | ✅ deep (type-specific subtypes, area ranges) | ❌ | ❌ | ❌ | agent profiles + reCAPTCHA lead form | ✅ +Google/FB | agent SaaS (Renture) + featured | ❌ EN/PHP | — |
| **Berenta** | ✅ **rental-term + amenities (pets/smoking…)** | ✅ Google Maps | ✅ **`/save-searches` CRUD** + concierge | — | per-listing inquiry + concierge | ✅ +Google/FB | ✅ **freemium tiers ₱850–2,500/mo** (PayPal) | ◑ **UI EN/JA/ZH/KO**, PHP only | — |
| **Carousell** | ◑ radius/type/budget/beds (specs freeform) | ◑ Google (inferred) | ✅ SavedSearch + RecentSearch slices | ✅ liked | **Sendbird in-app chat** + Make Offer | ✅ +FB/Google One-Tap | ✅ coin economy (Bump/Spotlight) | ❌ EN/PHP per-country sites | ✅ iOS + Android |
| **Aggregators** | ◑ (Nuroa: price/bed/bath/size/amenities) | ◑ Nuroa Leaflet | ✅ email alerts (core to model) | ◑ cookie-based | ❌ deferred to source portal | ◑ Nuroa cookie only | ✅ CPC (Thribee) + AdSense | ✅ per-ccTLD markets, native ₱ | ◑ Trovit/Nuroa apps |

---

## What the market has vs. what it's missing

**Table stakes (nearly everyone has — we must match):**
- Deep structured filters: price / bedrooms / bathrooms / floor-area / property-type / location. The classifieds
  (Lamudi, MyProperty, Dot Property, REAL, Berenta) set the bar; the brokerages (Presello, Property Source) fall short.
- Per-listing agent lead capture; multi-channel contact (**WhatsApp / Viber / Messenger**) is a PH expectation.
- Map on the listing detail page.
- `RealEstateListing` JSON-LD — the LIFULL portals, Presello, REAL and Filipino Homes have it; it's becoming standard.

**Common gaps (our openings):**
1. **Bilingual JP/EN + currency toggle — almost nobody has it.** Berenta is the *only* competitor with a JA UI
   locale (EN/JA/ZH/KO), and even it has no currency conversion. Our locked JP/EN + JPY-toggle design (DESIGN.md)
   is the clearest, hardest-to-copy differentiator, and it maps exactly to the client's Japanese-buyer audience.
2. **Real saved-search email alerts as a first-class buyer feature are rare.** MyProperty (price-drop + web-push),
   Berenta (`/save-searches` CRUD) and the aggregators (whose whole model is email alerts) have it; most brokerages
   have nothing. Our saved-search → matching-feed → `notify()` seam is aligned with the strong end of the market.
3. **Rich social/OG previews are inconsistent.** Lamudi ships *zero* OG tags; Berenta and Property Source reuse
   generic sitewide tags on real listings; Hoppler's are malformed. Our per-property OG image (DESIGN.md) beats them
   cheaply — and directly answers the client's "text-only sharing is hard" pain point.
4. **Results-page map is missing at many brokerages** (Presello, Property Source, REAL, OnePropertee). Our
   Leaflet/OSM results map is a visible polish win at zero API cost.

**Anti-patterns to avoid:**
- **Homex exposes raw owner PII** (name, mobile, email) through an unauthenticated `/api/public/units` endpoint that
  every page calls — despite `Disallow: /api/` in robots.txt. Keep contact agent-brokered; never ship owner PII.
- **Carousell buries bed/bath/floor-area in freeform description text** (generic `Product` schema + a key/value
  "smart attributes" bag). We already model these as typed fields — lean into it for real filtering + clean JSON-LD.

---

## Standout features worth borrowing (prioritized for our demo)

| Idea | Source | Fit for property-portal | Static-export safe? |
|---|---|---|---|
| **Per-property JSON-LD (`RealEstateListing`+`Offer`) at build time** | LIFULL portals, REAL | High — cheap SEO win, half the market lacks it | ✅ build-time |
| **Per-property OG image + deep category URLs** (`/for-sale/condo/2br/bgc`) | Filipino Homes | High — sharing pain point + SEO long-tail | ✅ (static hero-image OG per DESIGN; deep routes at build) |
| **"Viewing List" shortlist → single batched inquiry** | Hoppler | High — better lead UX than per-listing forms; pairs with our booking stub | ✅ client-side (localStorage) |
| **Saved-search → push matching** (buyer intent → new listings) | OnePropertee, MyProperty | High — this *is* our matching-feed feature; validates it | ✅ mock now via `notify()` seam |
| **Multi-channel contact (WhatsApp/Viber/Messenger deep links)** | Lamudi, MyProperty | High — PH norm, trivial to add to broker card | ✅ static links |
| **Mortgage / down-payment + installment calculator** | MyProperty, Lamudi | Med-High — fits our pre-build payment-schedule feature; JP-buyer relevant | ✅ client-side |
| **Rental-term filter (Daily / Short / Long)** | Rentpad, Berenta | Low now (we're sale-focused) — note for a rentals phase | ✅ |
| **"Help me find a place" concierge intake** | Rentpad, Berenta | Med — a softer entry than saved-search; feeds broker matching | ✅ form stub |
| **Price-tier bucketing for analytics/segmentation** | Presello (Meta Pixel) | Low — post-MVP marketing instrumentation | ✅ |
| **Dynamic OG-image rendering** | Filipino Homes | Deferred — needs a runtime; conflicts with static export. Revisit if we add an edge function | ❌ needs runtime |

---

## Recommendation for the demo

Do **not** try to out-inventory the LIFULL portals — half the market is one well-funded company and we run on ~50
mock listings. Win on the axes they ignore: **first-class JP/EN + JPY**, **rich shareable per-property previews**
(OG + JSON-LD built statically), a **shortlist→batched-inquiry + saved-search matching** flow that feels like a
concierge, and **map + multi-channel contact** as baseline polish. Every one of these is static-export-safe and
already consistent with `DESIGN.md`; the only genuinely runtime-dependent idea (dynamic OG images) is explicitly
deferred. The three concrete additions worth pulling into scope beyond the current design are: (1) build-time
`RealEstateListing` JSON-LD, (2) a Hoppler-style shortlist that batches into one inquiry, and (3) WhatsApp/Viber/
Messenger deep links on the broker card.

---

# Round 2 — new competitors + the Japan-facing cluster

A second scouting pass (2026-07) went looking for competitors we'd missed, weighted toward **Japan-facing /
overseas-buyer** sites since that's our differentiator. 9 of 12 were analysed on the same pipeline (evidence via
local `curl`); 3 (Juwai, Savills PH, HousingInteractive) sit behind Cloudflare Turnstile / block curl and are
**deferred to a browser-capable pass**. Full reports are the new per-site files in this folder.

> **Headline:** the site we'd expected to be the key JP rival — **PropertyAccess.ph — has pivoted to Japan-only
> property and abandoned PH**. **ZipMatch, Property24.com.ph, and Persquare are dead/parked.** No competitor
> combines what we do (JP/EN + PHP↔JPY + shareable per-listing SEO). The JP-facing sites that *do* exist each
> nail **one** piece we should learn from.

## New-competitor snapshot

| Site | Category | Framework | i18n / currency | Standout for us |
|---|---|---|---|---|
| **Sekai Property** | JP overseas-property portal (PH vertical) | Next.js / Vercel | **JP-native; 万円 (JPY)** | **利回り (yield) framing** as the default JP-investor lens; ships no per-listing JSON-LD |
| **FazWaz.jp** | Regional SEA portal, full JP edition | Laravel / Cloudflare | **Full `.jp` edition; auto ¥ conversion** | **PHP/THB→¥ conversion at scale** + complete `SingleFamilyResidence` JSON-LD |
| **Manila Condo** | JP-language niche PH condos | WordPress | **JP-native area taxonomy** | Fully Japanese area names (マカティ/パサイ) + **LINE-first** contact |
| **Starts Manila** | JP corporate-relocation (PH) | Apache (Starts Corp) | JP support; JPY audience | **Relocation persona**: furnished/serviced + JP-speaking mgmt + living-info (safety/schools) |
| **Bed&Go** | JP-run PH brokerage (trust front-end) | Wix | JP-native | **Trust playbook**: YouTube walkthroughs (`VideoObject`) + LINE community + named JP staff |
| **Rent.ph** | PH rental marketplace (**Filipino Homes / Leuterio Realty stablemate** — proven by shared S3+CRM) | Nuxt 3 / Cloudflare | EN; PHP | Hidden `/api/*` + **broadest structured data** (SearchAction + FAQPage + AggregateRating) |
| **Ohmyhome PH** | SG-HQ concierge marketplace | WordPress+Elementor / CloudFront | Country sub-paths; **no JP** | Productized **concierge "packages"** + agent/reviews content model |
| **GlobalListings** | Overseas aggregator + API licensor | Apache / PHP 7.3 (EOL) | Intl framing; no JP | **Listings-as-a-white-label-API** (syndication mirror) |
| **Leechiu** | PH commercial RE advisory | Next.js / Vercel | EN; PHP | Advisory + **market-reports as trust asset** (CRE — mostly out of scope) |
| _Juwai_ | cross-border | — | — | **unreachable** (network-level; live brand `juwai.com` is China-facing, not JP) |
| _Savills PH_ | CRE | — | — | **URL unresolved** (savillsph.com 404s; low priority, out of residential scope) |
| **HousingInteractive** | 2003 pioneer general PH portal (invested in Hoppler, 2014) | PHP 7.2/Laravel + separate WordPress blog | Cloudflare / S3 (SG) | **analysed via Wayback** — no JSON-LD, no saved-search, no consumer accounts; building/project aggregation URLs for SEO |

### Deep CDP / network-capture pass (done 2026-07-11)

A browser network-capture pass (Playwright/CDP-class, via the Chrome extension) upgraded the curl-based Round-2
reports for the dynamic sites. Outcomes:

- **Sekai Property** — clarifying null: **no hidden API**. Pure Next.js App Router SSR; listing data is inlined RSC
  flight, so curl already had it. Extracted model: listings are "projects" (`/projects/{id}`), priced as a **万円
  range**, **pre-selling** (completion year), images on a **Tokyo-region S3 bucket**.
- **Rent.ph** — the payoff case: CDP revealed a hidden **`/api/*`** surface (`search-suggestions`, `Categories`,
  `reviews/google`, `auth/testimonials/platform`, `analytics/*`) **and** an ownership link curl could never see —
  it loads images from `filipinohomes123` S3 and calls `system.leuteriorealty.com`, i.e. **Rent.ph is a Filipino
  Homes / Leuterio Realty stablemate**.

- **FazWaz.jp** — deep capture confirmed **live ¥ conversion + a 賃貸料率 (yield-rate) on every card**, a first-party
  `/api/*` layer (`/api/track/v2` + cookie-gated search), Sentry, and a heavy retargeting stack (AdRoll/DoubleClick/
  FB/OneSignal) — a performance-marketing acquisition model.
- **Ohmyhome** — `/en-ph/buy/` redirects to a marketing SVG: **no self-serve listing search** at the obvious path;
  confirms the WordPress-marketing + separate-concierge-app split. Concierge-first, not search-first.
- - **HousingInteractive** — live site Cloudflare-challenge-blocked (not bypassed); **completed via Wayback archives**
  instead. Full teardown in `housinginteractive.md`: PHP 7.2/Laravel (Eloquent class names `App\Division`/`App\PropertyType`
  leaked in form markup) + a separate WordPress 5.2.7 blog, S3 images, Google Maps; **zero JSON-LD, no saved-search, no
  consumer accounts** (auth is broker-only). Notable: it **invested in Hoppler in 2014**, and uses a building/project
  aggregation-page URL pattern good for long-tail SEO.
- **Still blocked/unreachable:** **Juwai** fails at the network level in the browser too (juwai.asia down/geo-blocked;
  live `juwai.com` is Chinese-buyer-facing, not JP); **Savills PH** URL is stale (`savillsph.com` 404s at root) — CRE,
  low priority. See the per-site files for each.

**Method lesson (validated across the pass):** CDP pays off on **client-fetch SPAs** (Nuxt/React that call `/api/` —
Rent.ph) and for **cross-host infra fingerprinting** (shared S3/CRM → hidden ownership, e.g. Rent.ph = Filipino
Homes). It adds little on **SSR** sites (Next.js App Router like Sekai, WordPress) where the data is already inlined in
the HTML curl fetched — the win there is confirming *absence* of a hidden API, not finding one.

## What the Japan-facing cluster teaches us (this is the payoff)

1. **JPY is not a toggle, it's the default — and it comes with yield.** Sekai prices in 万円 and leads with 利回り;
   FazWaz.jp auto-converts a foreign catalog into ¥. Our PHP↔JPY toggle is right, but we should **add a simple
   yield/ROI line** (annual rent ÷ price) next to the yen figure — that's the number JP investors actually scan for.
2. **Per-language routing beats a separate domain — we already do the cheap version.** FazWaz runs a whole `.jp`
   domain; Sekai/Manila Condo are JP-native sites. Our locale-segmented `/ja/…` routes get the same JP-SEO benefit
   without running a second site — a genuine efficiency win, and **nobody offers true JP/EN + PHP/JPY together**.
3. **JP trust is built with media + LINE + a human face, not features.** Bed&Go (video walkthroughs, LINE
   community, named Japanese staff) and Manila Condo (LINE-first) both substitute trust devices for inventory.
   Cheap things to borrow: a per-listing **`videoUrl`** slot (YouTube embed) and a **LINE deep-link** on the broker
   card — both static-export-safe.
4. **Two distinct JP personas exist.** Retail *investors* (Sekai/FazWaz — yield, resale, pre-selling) vs corporate
   *relocation* (Starts — furnished/serviced, company-lease, JP-speaking management, safety/schools). Our schema can
   cheaply carry a `furnished` flag and a neighborhood/living-info block to speak to both.
5. **JSON-LD is still a broad open goal.** Sekai ships none; only FazWaz and Rent.ph have strong structured data.
   Our planned build-time `RealEstateListing`+`Offer` (plus the easy `SearchAction`/`FAQPage` Rent.ph shows) beats
   most of this cohort for free.

**Net effect on positioning:** the expansion *strengthens* the Round-1 conclusion. The JP-facing niche is real but
fragmented — each rival does one thing (yield framing, ¥ conversion, video trust, JP area names) and none combines
them with a modern, shareable, bilingual, mapped catalog. Two cheap additions surface from this round and are worth
folding into scope: a **yield/ROI line** on the detail page and a per-listing **`videoUrl`** slot; LINE deep-links
were already on the Round-1 list.