# LIFULL Connect Agent/Developer Back-Office — Lamudi, MyProperty, Dot Property & Proppit
Clean-room competitive study of the shared agent/back-office platform behind three LIFULL Connect-owned
Philippine property portals — **Lamudi** (lamudi.com.ph), **MyProperty** (myproperty.ph), **Dot Property**
(dotproperty.com.ph) — and **Proppit**, LIFULL Connect's agent CRM/lead-management product. Method: public
signals only (robots.txt, sitemaps, homepage HTML/CSS, nav/footer links, subdomain probing, help-center
articles, blog posts, app-store listings, corporate pages). No login, no account creation, no auth bypass.
All URLs below were fetched and observed on 2026-07-11 unless noted. Statements not directly observed are
marked `(inferred)`; absent evidence is marked `not observed`.
---
## 1. Admin surface overview
The three portals sit on **the same LIFULL Connect white-label consumer front-end stack** and largely share
one back-office product for agents: **Proppit**. Concretely:
- Both **Lamudi PH** (`www.lamudi.com.ph`) and **MyProperty** (`www.myproperty.ph`) serve an **identical**
`robots.txt` (same Disallow list, same Magento-style path conventions) and both render an "Agent Login"
nav button (CSS class `nav-login-proppit`) that links to **`https://pro.lamudi.com/login`** — a
cross-country (non-`.ph`) login endpoint. The `.ph` market is selected via a query parameter
(`https://pro.lamudi.com/?country=ph`), i.e. one shared Proppit tenant serves multiple Lamudi country
sites. This confirms **MyProperty.ph and Lamudi PH share the same agent identity/back-office**, not just
the same consumer template.
- The `pro.lamudi.com/login` page's JS bundle emits a Sentry error-tracking release tag
`proppit@4a579135899d44d0a97e586f1f593bd62feec00a` — direct technical proof that **`pro.lamudi.com` is a
white-labeled instance of the Proppit application**, not a separate Lamudi-built CRM.
- **Dot Property PH** does not expose an obvious `pro.dotproperty.com.ph` (that subdomain does not resolve
publicly). Its homepage instead shows a plain `/login` (titled "Login | Dot Property") plus its own
native, lightweight self-serve listing flow (documented in Dot Property's own blog — see §4). Dot
Property's official blog separately documents **"Proppit" as the tool that powers XML-feed/bulk agencies
on its network** ("Proppit users can now enjoy even more visibility with unlimited listings" —
dotproperty.com.ph/blog). So Dot Property appears to run **two parallel listing-management paths**: (a) a
native, Dot-Property-branded self-serve flow for small landlords/individual agents, and (b) the shared
Proppit back office for agencies pushing bulk/XML inventory, same as Lamudi/MyProperty.
- **Proppit itself** (`proppit.com`, corporate page at `lifullconnect.com/brands/proppit/`) is described by
LIFULL Connect as a standalone global product: *"support real estate agents and developers to run their
businesses more effectively,"* operating **"across 60 countries through 63 websites in 11 languages,"*
with explicit sites for Chile, Colombia, Peru, **Philippines**, Thailand, Panama, Ecuador, Argentina. Its
network (confirmed via `info.proppit.com` help docs) redistributes listings to: **Dot Property,
Thailand-Property, HipFlat, Trovit, Mitula, Nestoria** — i.e. Proppit is the multi-portal listing
syndication + lead-CRM layer sitting *behind* Lamudi, Dot Property and several other LIFULL Connect
brands simultaneously.
**Who it serves:** independent agents, agency admins (multi-seat), and property developers/project
marketers — see role model in §3.
---
## 2. Discovered admin/agent entry points
| Entry point | Portal | How discovered | Notes |
|---|---|---|---|
| `https://pro.lamudi.com/login` | Lamudi, MyProperty | Nav button (`nav-login-proppit` class) on both `www.lamudi.com.ph` and `www.myproperty.ph` homepages | Confirmed Proppit instance (Sentry `proppit@` release tag). Country selected via `?country=ph`. |
| `https://proppit.com/login` | Proppit (cross-brand) | Direct probe, HTTP 200 | Corporate/global Proppit login, SPA shell (webpack `runtime`/`vendors`/`index` bundles), Facebook domain verification `enjd29ajmz1xtbbmnir5qcl46bqkvq` shared with `pro.lamudi.com`. |
| `https://www.dotproperty.com.ph/login` | Dot Property | Homepage nav link | Generic "Login \| Dot Property" page; no Proppit branding observed in static shell (SPA — inconclusive either way). |
| `https://www.dotproperty.com.ph/dashboard/saved-properties` | Dot Property | Homepage link + confirmed in `robots.txt` (`Disallow: /dashboard/*`) | Reads as a **consumer** account area (saved properties), not clearly agent-only. |
| `Disallow: /saved-search/`, `/login`, `/contact-agent-page-form/`, `/contact-developer-form/`, `/request-phone-agent-page-form/`, `/api/v1/projects/` | Lamudi & MyProperty `robots.txt` | curl | Confirms private/gated paths incl. a `projects` API and agent/developer contact-form endpoints. |
| `Disallow: /dashboard/*`, `/portal-*`, `/applies/*`, `/211923689/*` | Dot Property `robots.txt` | curl | `/portal-*` and `/applies/*` are unexplained gated path families — plausible agent/application admin routes `(inferred)`. |
| `https://register.dotpropertygroup.com/exclusive-projects-network` | Dot Property Group | WebSearch → WebFetch | Separate micro-site: **"Dot Property Exclusive"** developer/agent registration for a curated new-projects network (see §4). |
| `https://www.lamudi.com.ph/advertise/` | Lamudi | Homepage/search | "For agents" pricing/CTA page (fetch blocked by 403 bot-wall; existence + URL confirmed via search index). |
| `https://www.lamudi.com.ph/academy/` | Lamudi | WebSearch | **Lamudi Academy** — agent training portal, open to subscribers and non-subscribers. |
| Google Play `com.lamudi.pro` ("Lamudi Pro") | Lamudi | WebSearch | Agent-facing mobile app, explicitly Proppit-powered ("Proppit is the must-have tool for all property professionals"). Also on Apple App Store (`id6746932691`). |
| Google Play `com.lamudiconnect` ("Lamudi Connect PH – For Agents") | Lamudi | WebSearch | **A second, separate agent app**: "Philippines' first all-in-one property platform" for co-broking on verified listings, developer-project access, lead generation/management. |
| Public agent profile pages `/real-estate-agent/{id}` (Lamudi, MyProperty) and `/publisher/{slug}` + `/agents/all` (Dot Property) | All three | Homepage HTML | Public-facing directory pages, not admin, but confirm agent-account IDs and a "publisher" naming convention distinct from "agent" on Dot Property. |
| Public developer profile pages `/developer/{id}/{slug}` + `/developers` directory | Dot Property | Homepage HTML | Public developer landing pages (e.g. `/developer/180/vista-land`), not admin consoles. |
---
## 3. Role & account model
Observed/inferred account types, no two identical across the three portals:
- **Individual agent** — free self-serve account (Dot Property's native flow: sign up via Google/Facebook/
email, verify phone number, up to 10 free listings). Lamudi/MyProperty equivalent not directly observed
(gated by `/login` `Disallow`), but the same free-tier pattern is implied by the existence of paid
subscription tiers starting only at Bronze (§4).
- **Agency / agency-admin with sub-agents** — Lamudi's **Platinum** subscription tier explicitly includes
**"7 child accounts"** — direct evidence of a hierarchical agency-admin → sub-agent (child account) model
tied to the paid package, not a separate RBAC concept.
- **Developer / project marketer** — separate public-facing entity type (`/developer/{id}` pages, "For
Developers" directory) and a separate **project team** context: Lamudi's `/advertise/` copy (per search
index) frames Platinum specifically as for "developers and their property management teams." Dot
Property runs a distinct developer-facing product, **Dot Property Exclusive**
(`register.dotpropertygroup.com/exclusive-projects-network`), with its own 4-step registration: **Register
→ Get approved → Receive marketing materials → Start selling**, collecting *agent type: Freelance or
Agency* at signup — i.e. developer/project accounts and agent accounts are onboarded through the same
form but tagged by type.
- **Proppit account** — the underlying identity used to log into `pro.lamudi.com`; help-center language
("How can I add more users to my account?", "Agent assignment to properties") confirms **multi-user
accounts** where individual agents are assigned to specific properties under one company/agency account —
i.e. Proppit's primitive is agency-account-with-assignable-agents rather than fully independent per-agent
logins.
- No public evidence of a distinct "super-admin"/portal-staff role (expected — internal, not surfaced
publicly). `not observed`.
---
## 4. Admin feature inventory
**Listing management (create/edit/bulk/feed/API)**
- Proppit's Properties page (`info.proppit.com/en/support/properties-page`): filter by status/type/
operation, activate/deactivate **Boost**, delete (irreversible, confirmed by dialog copy), **"Export
data"** button to Excel/CSV.
- Three ingestion modes documented under Proppit's "Properties publishing and management" help section:
**Manual** (single-property form), **External CRM management** (agency's own CRM pushes into Proppit —
mechanism/protocol not disclosed publicly), and **XML feed management** (see §6).
- Dot Property's own native flow (blog "How to upload your property to Dot Property Philippines"): login →
"Upload a property" → up to 15 photos (min. 5, 600×400px) → listing type/price/category/location/
facilities/contact → title + description (min. 200 characters) → preview (eye icon) → publish via an
**Online/Offline toggle slider**. Free tier caps at **10 online listings**.
- `api/v1/projects/` path is explicitly disallowed in Lamudi/MyProperty `robots.txt` — a private
projects-related API exists `(inferred: developer/new-launch project data)`.
**Media**
- Dot Property native flow: drag-and-drop photo dropzone, manual reordering, first photo used as the
search-result thumbnail.
- Shared LIFULL Connect CDN observed via `` on the Dot Property homepage — a **centralized "Projects Manager" image service**
used for developer/new-project media, shared across portals rather than portal-specific `(inferred from
hostname)`.
**Lead inbox / CRM (Proppit)**
- **Enquiries page** — Proppit's lead inbox (per `discover-proppits-sections` help doc).
- Lamudi's own blog ("Boost Your Property Sales with Lamudi's Lead Management Tool," "Lamudi Lead
Management Tool Spotlight: To-Do List") documents agent-facing lead tooling including a **To-Do List**
feature for follow-ups (fetch of both posts returned HTTP 403 from a bot wall; existence, titles and
topic confirmed via search index — content of the to-do feature itself is `not observed` beyond the
title).
- LatAm marketing copy for Proppit (via Lamudi Mexico journal, found in search) additionally describes
real-time visibility into "who has viewed a property, who has called, who has sent a message," plus a
**WhatsApp integration** for responding to leads in real time — `(inferred to extend to PH; not directly
confirmed on a .ph-specific page)`.
**Analytics / performance dashboards**
- **Overview page** — Proppit's dashboard summary/metrics view (per help docs).
- Properties-page **"Export data"** to Excel/CSV functions as a lightweight reporting/export mechanism.
- No granular KPI list (impressions/clicks/conversion funnels) was directly observed — `not observed`
beyond the existence of the Overview page.
**Promotion management (featured/premium purchase)**
- **Boost** (standard) and **Superboost** (diamond icon, "the highest exposure among all listings, appearing
at the top of search results") — both toggled per-listing from the Properties page.
- Lamudi consumer-facing mechanic (from lamudi.com.ph journal): after purchasing credits, agent selects a
property → **"Set as Featured Listing"** → choose a **7/14/30-day** boost window; boosted listings carry a
visible **"Premium"** flag in search results.
**Billing / subscription (agency premium tiers)**
- Lamudi PH flat-fee tiers (PHP, monthly / 6-month prepay), per lamudi.com.ph journal + search index:
- **Bronze** — ₱4,299/mo or ₱25,794/6mo — 40 listings, "Partner Kit" (discounts, freebies, discounted
Featured-listing add-ons, 2 months Lamudi Academy access).
- **Silver** — ₱7,999/mo or ₱47,994/6mo — 80 listings.
- **Gold** — ₱8,999/mo or ₱53,994/6mo — 120 listings.
- **Platinum** — ₱14,999/mo or ₱89,994/6mo — 300 listings, **7 child accounts**, 2 months Lamudi Academy
access; targeted at developers/property-management teams.
- Proppit's LatAm/global corporate framing describes a **performance-based** ("pay for a click, a
conversion, or an impression") pricing model at the LIFULL Connect brand level — this appears to diverge
from the flat-fee PH tiers actually observed on Lamudi, suggesting **PH runs subscription pricing while
other Proppit markets may run usage-based pricing** `(inferred divergence — not reconciled by any single
source)`.
- Dot Property's free tier: 10 listings at no cost; paid packages exist (implied by "get in touch with your
account manager for more information" language in the Superboost/unlimited-listings blog post) but exact
DP price points are `not observed`.
- Unlimited-listings mechanic (Dot Property blog on Proppit): even without an active paid package, **XML
clients' listings still auto-publish for free at lower visibility/ranking** (suppressed only on
Thailand-Property.com); manual-upload clients must choose which properties consume their paid-package
slots, with the remainder publishing free.
**Team / agency / sub-agent management**
- Platinum tier's 7 child accounts (Lamudi) is the only concretely quantified sub-agent mechanism observed.
- Proppit help topics "How can I add more users to my account?" and "Agent assignment to properties" (listed
under Getting Started) confirm multi-user/agent-assignment exists as a first-class concept, without
exposing the underlying permission model.
**Developer / new-project ("Complex Projects") management**
- **Dot Property Exclusive** (`register.dotpropertygroup.com/exclusive-projects-network`) — the clearest
publicly documented developer product: full marketing/sales control for developers, early-launch access
and commission opportunities for agents, pre-qualified leads for buyers; registration captures agent
type (Freelance/Agency), company, and primary market area; post-approval benefits include white-label
marketing materials, legal/invoice/post-sale coordination support, and access to "limited promo units and
buyer incentives."
- Public `/developers` directories and `/developer/{id}/{slug}` pages exist on Dot Property (and `/projects/`
search on Lamudi/MyProperty), but these are **read-only marketing pages**, not the admin console itself —
the actual project-management back office is `not observed` (gated).
- Shared `projects-manager-images.prd.lifullconnect.com` CDN hostname strongly implies a centralized,
cross-portal "Projects Manager" tool for new-launch/project content `(inferred)`.
**Verification / moderation / badges**
- Lamudi's **"Fully Verified"** agent badge is free and requires: a professional headshot, an agency logo,
agency profile/background details, and a verified mobile or WhatsApp number (confirmed via search index
summary of Lamudi's own FAQ).
- Directly observed on a live Lamudi public agent-profile page: CSS/markup classes `verified-agent`,
`verified-agent-green`, `verified-agent-black`, `verified-icon-fully`, and body copy **"badge have the
backing of Lamudi"** — confirming the badge is real and rendered, though the moderation workflow behind
granting it is not exposed.
- No equivalent badge system was found in the fetched Dot Property or MyProperty markup — `not observed`
(may still exist; not surfaced on the pages sampled).
**Lead-routing / notifications**
- WhatsApp-integration claim (Proppit LatAm marketing copy, see Lead CRM above) — `(inferred applicability
to PH, not directly confirmed)`.
- No PH-specific lead-routing/SLA/auto-assignment documentation was found — `not observed`.
---
## 5. Implementation & tech
- **Proppit** (`proppit.com`, and its white-label instance `pro.lamudi.com`) is a pure client-rendered SPA:
webpack bundles `runtime.*.js` / `vendors.*.js` / `index.*.js`, self-hosted web fonts (Inter, woff2/woff/
ttf), Sentry error tracking (release tag format `proppit@`), Segment analytics
(`cdn.segment.com/analytics.js`), Google Tag Manager, and a shared Facebook domain-verification token
(`enjd29ajmz1xtbbmnir5qcl46bqkvq`) identical between `proppit.com` and `pro.lamudi.com` — strong
corroborating evidence both are the same deployed application.
- **Lamudi / MyProperty** consumer sites: identical `robots.txt` between the two brands, with Magento-style
admin path fragments visible in the disallow list (`/generate-seo-friendly-url`,
`/index/renderblognewsletter/`) `(inferred: Magento-derived stack)`. Sentry + Segment + GTM present on the
agent-login surface as noted above.
- **Dot Property**: Cloudflare-fronted (Rocket Loader, `/cdn-cgi/` scripts), New Relic RUM
(`js-agent.newrelic.com`, browser app IDs visible in inline config), OneSignal web push, its own
webpack/Vue-style asset pipeline served from `build.dotproperty.com.ph`, and photo hosting on
`photosrp.dotproperty.co.th` (regional SEA infra) alongside the shared LIFULL Connect
`projects-manager-images.prd.lifullconnect.com` CDN for developer/project imagery.
- Dot Property's homepage footer/asset markup includes literal `lifullconnect-part-of-*.svg` badge assets
and a link to `www.lifullconnect.com` — the parent-brand relationship is disclosed on-page, not just
inferred from infrastructure.
- Overall picture: **Proppit is one shared, centrally-deployed product** consumed by Lamudi (white-labeled
under `pro.lamudi.com`) and by Dot Property's bulk/XML agencies; **Dot Property additionally maintains its
own lighter-weight native listing system** for small/individual users; MyProperty has **no independent
agent back office at all** — it delegates entirely to the Lamudi/Proppit login.
---
## 6. Listing FEED / bulk-upload
Yes — Proppit supports XML-feed-based bulk syndication, documented publicly:
- Help article: **"How can I share my ads via CRM with an XML integration file?"**
(`info.proppit.com/en/support/how-to-prepare-an-xml-file-for-proppit`). It states the feed lets an agency
"manage all of your listings automatically from your website/database" and propagate them across the
Proppit network: **Dot Property, Thailand-Property, HipFlat, Trovit, Mitula, Nestoria**.
- The exact field-level XML schema is **not observed**: the help page links out to **country-specific Google
Docs** ("Proppit XML feed Instructions – English SEA" covering Thailand & Philippines, plus a Thai-language
variant) that were not fetchable in this clean-room pass (external Google Docs, likely access-gated or
outside the crawl scope) — their existence and naming is confirmed, their content is not.
- A companion PH landing page exists at `info.proppit.com/publish-in-proppit-ph` ("Publish in Proppit"),
advertising one-click publishing to "the most important real estate portals in the Philippines" and a
"request a demo" CTA — but it does not name Lamudi/Dot Property/MyProperty directly, nor does it expose
pricing or sign-up mechanics.
- Operational nuance confirmed via Dot Property's own blog: **feed-connected ("XML") accounts auto-publish**
even past their paid package limit, at reduced visibility, while **manually-managed accounts** require the
agent to hand-pick which listings consume paid slots — i.e. the feed pathway and the manual pathway are
treated as genuinely different ingestion pipelines with different default publishing behavior, not just
two UI options over the same backend queue `(inferred from described behavior)`.
- No public REST/JSON API documentation, API keys, or developer portal for programmatic listing submission
was found (the only API-shaped surface observed was the disallowed `/api/v1/projects/` path on Lamudi/
MyProperty, whose contract is not public) — `not observed`.
---
## 7. Takeaways for property-portal's future admin/CMS
1. **Separate the CMS identity from any future "agent CRM" identity early, the way LIFULL Connect did.**
Lamudi/MyProperty don't build their own agent back office — they federate entirely to Proppit via a
single "Agent Login" nav button. For our roadmap, this argues for designing the admin/CMS with a clean
boundary between "content operations" (our own listings CMS) and any future "lead CRM" concern, so the
latter could later be swapped for a bought-in tool without touching the core listings admin.
2. **Model two ingestion pipelines from day one: manual single-listing edit, and a feed/bulk path with
different default behavior.** Proppit treats XML-fed listings and manually-managed listings as distinct
pipelines (auto-publish-at-reduced-visibility vs. manual package-slot selection). Even a minimal
CSV/JSON bulk-import path for our CMS should be designed as a first-class ingestion mode, not a
thin wrapper over the single-edit form — it changes moderation, quota, and publishing-state logic.
3. **Tie package/quota logic to listing count and boost duration, not just to a flat "plan name."** The
observed Lamudi tiers (Bronze/Silver/Gold/Platinum) key off three concrete levers: listing-count cap,
boost duration (7/14/30 days) purchasable via credits, and child-account count. That's a compact,
implementable data model (`plan → {listing_cap, child_account_cap, boost_credits}`) worth adopting
directly rather than inventing a bespoke tiering scheme.
4. **A lightweight "verified" badge is cheap trust-signal leverage.** Lamudi's Fully-Verified badge requires
only four low-friction inputs (headshot, agency logo, agency profile, verified phone/WhatsApp) and is
free — it's a moderation gate, not a paid feature. For property-portal, a similar free verification
checklist (photo + phone OTP + basic company info) would visibly differentiate listings without needing
a billing system first.
5. **Plan the developer/new-project flow as a distinct object type from agent listings, not a variant.**
Both Lamudi (`/projects/`) and Dot Property (Dot Property Exclusive, `/developer/{id}` pages,
`projects-manager-images.*` CDN) give "complex projects" their own URL namespace, their own media
pipeline, and (for Dot Property) their own registration/approval funnel with a distinct "agent type:
Freelance vs Agency" field. If property-portal ever adds new-development/pre-selling inventory, model it
as its own entity (developer → project → unit-type) from the start rather than overloading the existing
listing schema.
6. **Don't over-invest in bulk XML/API tooling before there's agency demand.** Even a mature, well-funded
platform (LIFULL Connect) still routes its country-specific feed spec through a Google Doc rather than a
public developer portal with self-serve API keys — bulk ingestion here is white-glove/manually
onboarded, not self-service. For our MVP-stage CMS, a simple CSV import reviewed by an admin is
proportionate; a public feed API is not worth building until an actual multi-listing agency partner
asks for it.
---
## Admin matrix row
| Roles | Admin entry points | Listing mgmt (bulk/feed?) | Lead CRM | Analytics | Promotion/boost admin | Billing/credits | Team/brokerage mgmt | Developer/project mgmt | Verification/moderation | White-label CRM product | Tech/implementation | Standout admin capability |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Individual agent (free); agency-admin w/ child accounts; developer/project team (Freelance or Agency type) | `pro.lamudi.com/login` (shared by Lamudi+MyProperty); `proppit.com/login`; `dotproperty.com.ph/login` (native); `register.dotpropertygroup.com/exclusive-projects-network` (dev/project onboarding) | Yes — Manual, External-CRM push, and XML feed (auto-publish, network-wide: Dot Property, Thailand-Property, HipFlat, Trovit, Mitula, Nestoria); exact XML schema gated in a linked Google Doc, not observed | Yes — Proppit "Enquiries page" lead inbox; WhatsApp integration and real-time view-tracking claimed in Proppit's LatAm marketing (not PH-confirmed) | Proppit "Overview page" (metrics summary) + per-listing "Export data" to Excel/CSV; no granular KPI breakdown observed | Boost + Superboost toggle per listing; consumer-facing "Set as Featured Listing" with 7/14/30-day credit-based duration and "Premium" flag | Flat-fee PH tiers: Bronze ₱4,299–Platinum ₱14,999/mo (listing cap + child accounts + Academy access); Proppit corporate messaging elsewhere describes pay-per-click/conversion pricing (not reconciled with PH tiers) | Platinum tier = 7 child accounts; Proppit help topics confirm multi-user accounts + "agent assignment to properties" | Dot Property Exclusive: 4-step register→approve→materials→sell flow, full marketing/sales control for developers, early-access/co-broke for agents; shared `projects-manager-images.prd.lifullconnect.com` CDN across portals | Lamudi "Fully Verified" badge (free): headshot + agency logo + agency profile + verified phone/WhatsApp; badge CSS/copy confirmed live on public agent profile | **Proppit** — single product white-labeled as `pro.lamudi.com`, confirmed via shared Sentry release tag `proppit@` and shared Facebook domain-verification token with `proppit.com` | Proppit: SPA (webpack), Sentry, Segment, GTM. Lamudi/MyProperty: Magento-style paths, identical robots.txt. Dot Property: Cloudflare + New Relic + OneSignal + own Vue/webpack build, regional TH photo host | One Proppit back office quietly powers listing distribution + lead inbox for **two** portal brands (Lamudi, MyProperty) plus feeds a **third** (Dot Property) and 4 more regional sites (Thailand-Property, HipFlat, Trovit-adjacent), all from one login |
---
### Sources consulted
- `https://www.lamudi.com.ph/` (homepage HTML, robots.txt, sitemap index)
- `https://www.myproperty.ph/` (homepage HTML, robots.txt)
- `https://www.dotproperty.com.ph/` (homepage HTML, robots.txt)
- `https://pro.lamudi.com/login`, `https://proppit.com/`, `https://proppit.com/login`
- `https://www.dotproperty.com.ph/login`
- `https://www.lifullconnect.com/brands/proppit/`
- `https://info.proppit.com/en/support/getting-started-in-proppit`
- `https://info.proppit.com/en/support/discover-proppits-sections`
- `https://info.proppit.com/en/support/properties-page`
- `https://info.proppit.com/en/support/how-to-prepare-an-xml-file-for-proppit`
- `https://info.proppit.com/publish-in-proppit-ph`
- `https://www.dotproperty.com.ph/blog/upload-property-dot-property-philippines`
- `https://www.dotproperty.com.ph/blog/proppit-users-can-now-enjoy-even-visibility-unlimited-listings`
- `https://register.dotpropertygroup.com/exclusive-projects-network`
- `https://www.lamudi.com.ph/real-estate-agent/41032-73-14719a51c100-63c2-19ce01b-acb1-70f5` (public agent
profile, verification badge markup)
- Search-index summaries (page content not directly fetchable, blocked by bot-wall/403): Lamudi
`/advertise/`, `/journal/lamudi-cost-per-listing/`, `/journal/boost-your-property-sales-with-lamudis-
lead-management-tool/`, `/journal/lamudi-lead-management-tool-spotlight-to-do-list/`, `/academy/`,
Lamudi FAQ (verification requirements); Google Play listings for `com.lamudi.pro` and `com.lamudiconnect`