# Competitive Research: Hoppler (hoppler.com.ph)

Clean-room reverse-engineering notes for the `property-portal` roadmap. All data gathered from public HTTP responses (`curl`, desktop Chrome UA), public `robots.txt`/`sitemap.xml`, and public web search. No authentication, scraping automation, or ToS-violating access was used. Captured 2026-07-11.

## 1. Overview & positioning (brokerage-led model)

Hoppler is not a pure classifieds/listings board — it is a **licensed real-estate brokerage that operates its own online marketplace**. The homepage `Organization`/`RealEstateAgent` JSON-LD self-identifies as:

- Legal name **"Hoppler Inc"**, `foundingDate: "2004"` (per site's own structured data — note this conflicts with press coverage, see below), founder **Ramon Ballesca**.
- Registered office: "Penthouse, PNB Makati Center, 6754 Ayala Avenue, Barangay San Lorenzo, Makati City" — a real brokerage address, not just a tech company mailing address.
- `RealEstateAgent` schema type with `openingHours: Mo-Su 08:00-20:00` — the site models itself in structured data as an actual real-estate agency, not just a platform.

Web search (public sources) adds context (inferred, not directly observed on-site):
- Press (Inquirer, NewsBytes.ph) reports Hoppler was founded ~2012–2014 by Ramon Ballesca; raised early seed funding (~$200K) plus a ₱22M round from Elizalde-Roxas Corp in 2014.
- **Frontier Digital Ventures** (Malaysia-based, backs multiple SEA property portals e.g. iProperty group affiliates) invested in 2017 and increased its stake to **51% in 2021**, i.e. Hoppler is majority-owned by a regional proptech roll-up, not fully independent.
- Total reported funding across trackers (Crunchbase/Tracxn/PitchBook, inferred, not verified first-hand): low single-digit millions USD.
- Sitemap shows **9,207 indexed listing URLs** (`sitemap-listings-1.xml.gz`), consistent with press claims of "10,000+ listings," concentrated in Metro Manila (Makati, BGC/Taguig, Mandaluyong, Muntinlupa, Pasig, Parañaque, Las Piñas, Quezon City appear repeatedly as location facets).

The positioning is "search + real brokers behind every listing," reinforced by a **"Trusted Brokers and Top Agents"** tagline in the meta description, an inquiry flow that routes to human agents (see §4), and a dedicated **partner-broker recruitment program** ("KUMITA by Hoppler," `/kumita-brokers`) that lets independent brokers list properties and earn commission through the platform — brokerage network expansion is a first-class product surface, not just a footer link.

## 2. Tech stack & architecture

Observed via response headers, HTML markers, and the main JS bundle (`/xpoc/js/main.c674426a.js`, 1.17 MB):

- **Public site (`www.hoppler.com.ph`)**: `Server: nginx`, `X-Powered-By: Express` — a **Node.js/Express** app behind Nginx, doing **server-side rendering** of marketing/search/detail pages (no cookies set on these responses; stateless SSR).
- **API host (`api.hoppler.com.ph`)**: `Server: Apache-Coyote/1.1` and a `JSESSIONID` cookie — a separate **Java (Tomcat, likely Spring)** backend on its own subdomain, with wide-open CORS (`Access-Control-Allow-Origin: *`, custom `X-CSRF-*` allowed headers). The homepage `<link rel="preconnect" href="https://api.hoppler.com.ph">` confirms the front end calls this host directly from the browser.
- **No Next.js/Nuxt markers**: `__NEXT_DATA__`, `__NUXT__`, `__INITIAL_STATE__`, `wp-json` all **not observed**. Instead, page-specific data is embedded as **base64-encoded JSON inside `<script type="application/json" id="...">` tags** (see §3) — a custom hydration mechanism, not a known meta-framework.
- **Custom elements / component model**: markup uses custom tags with an `hi-` prefix (e.g. `<hi-property-card>`… actually CSS-class based; true custom elements observed: `<hi-properties-map>`, `<hi-card-vl-button propertyKey="RR3068881">`, `<hi-hero-search-box>`, `<hi-vl-count-bubble>`, `<hi-results-page-filters>`, `<hi-login-nav-button>`, `<hi-virtual-tour-button>`, `<hi-maintenance-message>`). The JS bundle contains **90 occurrences of `react`**, so these are almost certainly React components registered as Web Components (custom-elements wrapper), rendered as SSR "islands" inside server-generated HTML rather than a full client SPA — an **SSR-shell + hydrated-islands** architecture.
- **Second, fully separate SPA**: `/kumita-brokers` (partner-broker portal) serves a near-empty shell (`<body><hi-app></hi-app></body>`, 353 bytes) loading `/kpb/js/main.57e7d222.js` — a **fully client-side-rendered app**, distinct bundle from the public "xpoc" SSR bundle. So Hoppler splits rendering strategy: **public SEO-critical pages = SSR; authenticated/internal broker tooling = CSR SPA**.
- **CDN/hosting**: Static assets and images served from **CloudFront** (`dzjqf1alh39sw.cloudfront.net` for logos/icons/site chrome, `d2wy52y0hrt3v.cloudfront.net` for property photos) and **imgix** (`hoppler-inc.imgix.net`, `hoppler-blog.imgix.net`) for on-the-fly image resizing/format negotiation (`?fit=crop&w=…&auto=format,compress` query params — responsive `auto=format` implies WebP/AVIF negotiation via imgix).
- **Fonts**: Google Fonts, **Roboto** (400/500/700), loaded via `fonts.googleapis.com`/`fonts.gstatic.com` with `preconnect` + `media="print" onload` async-swap pattern for render-blocking avoidance.
- **Analytics/marketing tags**: Google Tag Manager (`GTM-P27HZF`), Google Ads conversion tag (`AW-959146815`), `gtag()` calls. **Not observed**: Meta/Facebook Pixel, Hotjar, Segment, Mixpanel, Microsoft Clarity (absent from all fetched pages/bundle, despite Hoppler having a Facebook page).
- **AMP**: homepage advertises `<link rel="amphtml" href="https://www.hoppler.com.ph/.amp">`, though that endpoint currently 302-redirects to `/` (inferred: AMP support was built but may be deprecated/misconfigured now).
- `robots.txt` is minimal: `Disallow: /_blog/` only — everything else (including search results and listing detail pages) is crawlable.

## 3. Data layer & hidden APIs

**No GraphQL, Algolia, or Elasticsearch endpoint strings found** in the JS bundle or HTML (checked explicitly). Search/filtering appears to hit the Java REST API on `api.hoppler.com.ph` (exact result-fetching path not captured in static assets — likely called at runtime via XHR/fetch not present in the static bundle strings we could grep, so **not observed** directly, only inferred from the `preconnect` hint and REST-style paths below).

**REST paths found by string search in `/xpoc/js/main.c674426a.js`** (site-relative; base host not always statically determinable — some resolve against `www.hoppler.com.ph`, others likely against `api.hoppler.com.ph`):

```
/api/cis
/api/cis/
/api/contact-us
/api/partnerbroker/complete
/api/partnerbroker/partial
/api/properties/inquire
/api/properties/inquire/cart      <- batch inquiry across multiple saved listings
/api/users
/api/users/change_password
/api/users/forgot_password
/api/users/resend
/api/users/reset_password
/api/yelp/businesses/search        <- third-party Yelp API integration, likely for nearby-amenities on detail pages
/auth
/login
/signup-type
/client/listing/
/client/results-page/search        <- results/search-page data endpoint
/client/sign-up
/client/sign-up/buyer
/client/sign-up/resend
```

The `/api/properties/inquire/cart` path corroborates the "Viewing List" feature (§4): users can queue multiple properties and submit one combined inquiry, rather than contacting one listing at a time.

**Embedded page state**: rather than a global `window.__STATE__`, Hoppler SSR pages embed **base64-encoded JSON payloads** in dedicated `<script type="application/json" id="...">` tags, decoded client-side. Confirmed on the results page (`/condominiums-for-rent`):

- `#hiResultsDivCat` → taxonomy context for the page, e.g.:
  ```json
  {"division":"Residential","category":"Rent","type":"Condominium","level":"Top",
   "permalink":"/condominiums-for-rent","locationPermalink":"","label":"Condo for Rent"}
  ```
- `#hiResultsPageResult` → the actual result set (24 listings on this page), each item shaped like:
  ```json
  {
    "propertyKey": "RR3549781",
    "feStatus": "Available",
    "division": "Residential",
    "category": "Rent",
    "type": "Condominium",
    "views": 0,
    "building": "La Vie Flats",
    "area": "Alabang",
    "city": "Muntinlupa",
    "region": "National Capital Region",
    "address": "La Vie Flats, Alabang, Muntinlupa",
    "latitude": 14.413131,
    "longitude": 121.036153,
    "permalink": "/muntinlupa-alabang-la-vie-flats-rr3549781",
    "minPrice": 53000,
    "maxPrice": 53000,
    "pricePerSqm": 1060,
    "discountedPrice": 53000,
    "floorArea": 50,
    "bedrooms": 1,
    "bathrooms": 1,
    "photos": ["hoppler/properties/residential/Condominium-rent-RR3549781-731417_orig.png", "...9 more"],
    "dateAvailability": "2026-07-10T12:00:00+08:00",
    "dateModified": "2026-07-10T17:54:45+08:00"
  }
  ```
  Note the `minPrice`/`maxPrice`/`discountedPrice` triple (supports price-range and promo/discount pricing on one SKU), `pricePerSqm` precomputed server-side, and `views` (listing popularity counter, exposed to the client).
- `#hiFormDefaults` → empty (`{}`) on this page load — filter defaults populated dynamically elsewhere, not observed with values.
- Detail page equivalents: `#hiListingDivCat` (`{"type":"Condominium","category":"Rent","division":"Residential"}`) and `#hiListingLocation` (`{"city":"Makati","area":"Rockwell Center","region":"National Capital Region","building":"One Rockwell"}`).

**Listing ID scheme**: alphanumeric keys like `RR3068881`, `RR2917581`, `RR3549781`, `RR0589581` — two-letter prefix (`RR` observed on Rent/Residential examples) + numeric sequence; used directly in the URL slug and as the DOM `id` on card elements and as the `propertyKey` attribute on the `<hi-card-vl-button>` custom element.

**JSON-LD structured data**: only `Organization` + `RealEstateAgent` graph observed on the **homepage**. **Not observed** on the results page or the detail page (checked both explicitly) — no `Product`, `Offer`, `RealEstateListing`, or `BreadcrumbList` JSON-LD on listing/detail pages, despite listing cards using inline **schema.org Microdata** instead: `itemscope itemtype="https://schema.org/Offer"` on each property card, with `itemprop="price"`, `itemprop="priceCurrency"` (`PHP`, rendered as a visually-hidden `<span class="d-none">`), `itemprop="name"`. The property detail page also only carries `itemtype="https://schema.org/Offer"` microdata, no JSON-LD — an SEO gap (Google's preferred format is JSON-LD, and richer types like `RealEstateListing`/`Residence` are not used at all, observed nowhere).

**Third-party data**: `/api/yelp/businesses/search` shows Hoppler proxies Yelp's API server-side to show nearby amenities/POIs on detail pages (inferred purpose from path name only — exact usage on-page not directly captured in this pass).

## 4. Feature inventory

**Search filters** (enumerated from visible SSR text + JS bundle strings):
- Transaction: **For Sale (Buy)** / **For Rent (Rent)** toggle.
- Property type facets: **Condominium, House and Lot, Townhouse, Vacant Lot, Commercial Lot, Commercial Space, Office Space, Warehouse, Building, Serviced Office** (10 types).
- Location facets (repeated per type in footer/nav link farm): Makati, Taguig/Bonifacio Global City, Mandaluyong, Muntinlupa, Pasig, Parañaque, Las Piñas, Quezon City.
- Price: `minPrice`/`maxPrice` range (field names from bundle).
- Floor area: `minFloorArea`/`maxFloorArea`.
- `petFriendly` boolean filter (found as a distinct field name in the bundle).
- Amenity checkboxes (strings found in bundle): **Swimming Pool, Gym, Parking, Balcony, Garden, Security, Elevator, Playground, Function Room, Clubhouse**.
- Sort options (results page, visible text): **Date Modified (Newest first)**, **Date Modified (Oldest first)**, **Price (Highest first)**, **Price (Lowest first)**.
- Full filter UI itself is rendered by the `<hi-results-page-filters>` component behind a "Set Filters" button/modal — exact full field set beyond the above strings not directly observed (client-rendered).

**Map**: `<hi-properties-map>` custom element present on both results and detail pages. Provider confirmed as **Google Maps**: bundle contains `maps.googleapis.com/maps/api/js?v=3.34&key=…` (API version pinned to 3.34) plus a `maps.google` reference on the homepage JSON-LD `hasmap` link. No Mapbox/Leaflet/OSM strings found anywhere.

**Gallery/media**: per-listing photo arrays (10 photos observed on one card, 245 photo URLs total referenced across one detail page across gallery + building-level photos) served from CloudFront, filenamed with random numeric suffixes suggesting an internal asset-management pipeline (`Condominium-rent-RR3549781-731417_orig.png`). Detail page includes a **YouTube-embedded virtual tour** (`<hi-virtual-tour-button>`, "virtual-tour"/"YouTube" strings observed) — no Matterport/3D-tour provider observed.

**Agent/lead contact**: no phone-number-reveal or WhatsApp/Viber deep link observed in the fetched pages. Contact is funneled through an **"Inquire"** nav item/button and a per-listing inquiry form hitting `/api/properties/inquire`. Distinctively, Hoppler has a **"My Viewing List"** feature (nav item observed: "Inquire · My Viewing List · Sign-up") — a persistent cart-like list of properties (`<hi-card-vl-button propertyKey="…">` on every card, `<hi-vl-count-bubble>` badge showing count) that batches into a single combined inquiry via `/api/properties/inquire/cart`. This is a notably different pattern from single-listing "contact agent" forms.

**Saved search / alerts / email**: not observed. No "save this search," "email me new listings," or alert-subscription UI/copy found on the fetched pages.

**Accounts/auth**: `/login`, `/signup-type`, `/client/sign-up`, `/client/sign-up/buyer`, `/client/sign-up/resend`, plus `/api/users`, `/api/users/change_password`, `/api/users/forgot_password`, `/api/users/reset_password`, `/api/users/resend` — standard email/password account system with password-reset flow, and a distinct "buyer" sign-up type (implying multiple account types, e.g. buyer vs. broker/partner). A promo banner offers a **"NEWHOME" signup promo code to win prizes"** — a growth/incentive mechanic tied to registration.

**Monetization**: (inferred from architecture, not a pricing page) revenue is **brokerage commission-based** (Hoppler is a licensed broker itself, per its `RealEstateAgent` schema), plus a **"Post Property For Free"** lead-gen CTA for owners/sellers repeated in every page's nav (funnels supply-side listers in), and the **KUMITA partner-broker program** (`/kumita-brokers`, `/kumita-brokers/listings`, `/kumita-brokers/post-property`) which recruits third-party brokers — likely a revenue-share/referral model (inferred). Google Ads conversion tracking (`AW-959146815`) confirms active paid-acquisition spend. No display-ad inventory, subscription paywall, or featured-listing "upsell" UI observed on the fetched pages.

**i18n & currency**: **English only** — no `hreflang`/`alternate` language links found on homepage or detail page (checked explicitly), no visible language switcher. Currency is **PHP only** — every price is prefixed `₱` with `itemprop="priceCurrency">PHP` hardcoded; no currency-toggle UI or USD/other-currency pricing observed anywhere.

**Mobile app**: Native apps confirmed via app-store links present on every page fetched: **iOS** (`itunes.apple.com/us/app/hoppler/id1254840096`) and **Android** (`play.google.com/store/apps/details?id=app.ph.com.hoppler`).

## 5. UX & content notes

- Homepage hero is a single full-bleed search box (`<hi-hero-search-box>`) over a background photo, responsively art-directed via imgix `<link rel="preload">` variants for 4 breakpoints (480w mobile crop, 720w, 960w, 1920w desktop) — real effort put into LCP image optimization.
- A **"Real Estate Magazine"** content-marketing section exists (`/magazine/...` URLs, separate `sitemap-magazine-1.xml.gz`), covering lifestyle/neighborhood content (e.g. "Outdoor activities to do in Nuvali," restaurant guides) — classic SEO/content-marketing funnel into specific developments/areas, not just transactional listings.
- Results pages show a live results counter (e.g. "Condo for Rent (3657 results)") and a persistent "Show map" toggle alongside "Set Filters" — map and list appear to be togglable rather than always-split-screen (at minimum on mobile: `<hi-results-map-toggle-mobile>`-equivalent element observed).
- A `<hi-results-one-broker-notif>` element on results pages suggests some kind of "single broker owns all these results" notice/badge — page-level broker attribution UX (exact trigger/content not observed).
- `<hi-maintenance-message>` custom element present sitewide — implies a feature-flagged maintenance-mode banner system built into the shell.

## 6. SEO & metadata

- Homepage `<title>`: "Philippine Real Estate Listings & Property Finder | Hoppler"; meta description present and matches OG description.
- OpenGraph tags use nonstandard `<meta name="og:...">` (should be `property="og:..."` per spec) — `og:description` and `og:image` observed, but **no `og:title`, `og:url`, or `og:type`** found on the homepage — a partial/malformed OG implementation.
- `rel="canonical"` present on both homepage and detail page.
- JSON-LD `Organization`/`RealEstateAgent` graph only on homepage (§3); listing pages rely solely on `Offer` microdata, missing richer `RealEstateListing`/`BreadcrumbList` types.
- Sitemap is a proper index (`sitemapindex`) split into `sitemap-static`, `sitemap-listings-1` (9,207 URLs), `sitemap-results-pages-1`, and `sitemap-magazine-1`, each gzip-compressed with `<lastmod>` — well-structured for a site this size.
- `robots.txt` only disallows `/_blog/`; all listing/search content is crawlable, consistent with an SEO-led acquisition strategy (reinforced by the content Magazine + AMP attempt).

## 7. Takeaways for property-portal

Prioritized ideas, given property-portal is a bilingual JP/EN SUUMO-like demo:

1. **"Viewing List" batch-inquiry pattern is the standout differentiator worth borrowing.** Instead of only a single-listing contact form, let users add several listings to a shortlist and submit one combined inquiry/booking request. This maps well onto property-portal's booking feature and is a much stronger lead-gen mechanic than a bare "contact" button — likely raises inquiry conversion by lowering friction for comparison shoppers.
2. **Fix what Hoppler gets wrong on SEO as an easy win**: ship full, correct JSON-LD (`RealEstateListing`/`Offer` with `BreadcrumbList`) on both search-results and detail pages, and use spec-correct `property="og:*"` tags including `og:title`/`og:url`/`og:type`. Hoppler's own detail pages have no JSON-LD at all and a malformed OG block — property-portal can out-execute this cheaply since it's a greenfield build.
3. **Precompute and expose the same lightweight listing-card shape** Hoppler uses server-side (`minPrice`/`maxPrice`/`discountedPrice`/`pricePerSqm`, lat/lng, bedroom/bathroom/floorArea, first-N photos) as a stable JSON contract for the results grid — it's a proven, minimal shape that keeps result payloads small and map+list in sync from one source.
4. **Adopt an SSR-for-public-pages / CSR-for-authenticated-tools split**: Hoppler serves marketing/search/detail pages server-rendered for SEO and crawlability, but its partner-broker portal is a separate pure-SPA bundle. property-portal (Next.js static export) should keep this same boundary in mind if/when an authenticated agent/broker dashboard is added later — don't force SSR requirements onto internal tooling.
5. **Currency/i18n gap is a real opportunity, not just a gap to avoid**: Hoppler is English/PHP-only despite the Philippines having significant OFW and foreign-buyer audiences — property-portal's bilingual JP/EN + currency-toggle design (already built per project history) is a genuine differentiator versus the market leader, worth foregrounding in any pitch/demo narrative rather than treating as a "nice to have."
6. **Consider a lightweight "amenities near this listing" integration** (Hoppler proxies Yelp via `/api/yelp/businesses/search`, inferred for nearby POIs) — even a static/demo version (e.g. canned "nearby BTS/MRT, schools, malls" data per listing) adds perceived polish cheaply for a demo without needing a live third-party integration.

Sources consulted for background (public web search, not scraped): [Hoppler — Tracxn company profile](https://tracxn.com/d/companies/hoppler/__xDfkJN9ar6S4OXn3a39IHE0_dhJgmuQARojqFJCFpdk), [Hoppler — PitchBook profile](https://pitchbook.com/profiles/company/132014-35), [Hoppler Celebrates Fourth Anniversary (hoppler.com.ph magazine)](https://www.hoppler.com.ph/magazine/real-estate-news/hoppler-celebrates-fourth-anniversary), [Hoppler — Crunchbase](https://www.crunchbase.com/organization/hoppler), [Pinoy-owned real estate app eyes expansion via brokers network — NewsBytes.ph](https://newsbytes.ph/2018/01/29/pinoy-owned-real-estate-app-eyes-expansion-via-brokers-network/), [Frontier Digital Ventures — Philippines](https://frontierdv.com/philippines/), [Real Estate Startup Hoppler Celebrates Growth of Partner Broker Network — Inquirer Business](https://business.inquirer.net/264683/real-estate-startup-hoppler-celebrates-growth-of-partner-broker-network), [Hoppler — CB Insights](https://www.cbinsights.com/company/hoppler).

---

## Matrix row

Category | Framework | Host/CDN | Search filters | Map | Saved search/alerts | Agent/lead contact | Auth | Listing data source | Notable API endpoints | Monetization | i18n/currency | Mobile app | Standout feature
--- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | ---
Brokerage-led marketplace | Node.js/Express SSR (public site) + React "islands" via custom elements; separate Java/Tomcat API; separate React CSR SPA for partner-broker portal | Nginx front + CloudFront (`dzjqf1alh39sw.cloudfront.net`, `d2wy52y0hrt3v.cloudfront.net`) + imgix image CDN | Buy/Rent × 10 property types, location, min/max price, min/max floor area, pet-friendly, amenities (Swimming Pool/Gym/Parking/Balcony/Garden/Security/Elevator/Playground/Function Room/Clubhouse), sort by date/price | Google Maps JS API (v3.34) | not observed | "Inquire" form + "My Viewing List" batch-inquiry cart (`/api/properties/inquire/cart`); no phone-reveal/WhatsApp observed | Email/password (`/login`, `/client/sign-up/buyer`), password reset endpoints, distinct buyer vs. partner-broker account types | Base64-JSON embedded in `<script type="application/json">` tags (`#hiResultsPageResult`, `#hiListingLocation`, etc.), schema.org `Offer` microdata on cards; no GraphQL/Algolia/Elasticsearch found | `/api/properties/inquire`, `/api/properties/inquire/cart`, `/client/results-page/search`, `/api/partnerbroker/complete`, `/api/yelp/businesses/search`, `/api/users/*` | Brokerage commissions (site is itself a licensed `RealEstateAgent` per schema.org) + "Post Property For Free" seller lead-gen + KUMITA partner-broker recruitment program + active Google Ads spend | English only, PHP only — no hreflang, no currency toggle observed | iOS (`id1254840096`) and Android (`app.ph.com.hoppler`) apps linked sitewide | "Viewing List" cart that batches multiple listings into one combined inquiry, rather than one contact form per listing