Pricing

Rating

Developer

Actor stats

Categories

Share

Property Finder Egypt Scraper

Property Finder Egypt Scraper extracts structured real estate listing data from propertyfinder.eg for both sale and rent searches. It supports location-based discovery and direct URL seeding, crawls Property Finder search pages, normalizes records into a clean dataset, and can optionally track newly seen listings for monitoring workflows. The actor is designed for market research, lead generation, inventory snapshots, and repeat runs where you only want fresh listings.

Use cases

• Build a normalized database of Property Finder Egypt listings
• Monitor a district, compound, or city for newly published listings
• Export sale or rent inventory for market research and pricing analysis
• Track apartments, villas, chalets, duplexes, and other property types
• Feed downstream CRM, analytics, enrichment, or alerting pipelines

What this actor extracts

Each dataset item is normalized into a consistent property record and may include:

• Listing URL and provider-scoped IDs
• Offer type such as sale or rent
• Property type
• Price and currency
• Bedrooms, bathrooms, area, and area unit
• Governorate, city, district, compound, and street text
• Latitude and longitude when available
• Furnishing and finishing status
• Listed and updated timestamps when present
• Verification flags
• Listing images
• Optional raw provider payload for debugging or custom post-processing

Features

• Scrapes Property Finder Egypt search result pages
• Accepts direct list URLs and direct property detail URLs
• Supports location-based seeds for Egypt
• Deduplicates normalized results before output
• Supports monitoring mode using a key-value tracking store
• Can enrich listings with unit numbers via a secondary actor
• Supports metric and imperial area normalization

Input options

Provide at least one of the following:

• location
• sourceUrls
• listUrls
• propertyUrls

Example: location-based run

{
"location":{
"country":"EG",
"governorate":"Cairo",
"city":"New Cairo",
"district":"Fifth Settlement"
},
"offerTypes":["sale","rent"],
"realEstateType":"Apartment",
"maxResultsPerProvider":100,
"units":"metric",
"deduplicateResults":true,
"threads":3,
"monitoringMode":false,
"retrieveUnitNumber":false,
"enableDelistingTracker":true,
"proxy":{
"useApifyProxy":true,
"apifyProxyGroups":["RESIDENTIAL"]
}
}

Example: direct search URL run

{
"sourceUrls":[
{
"type":"list",
"url":"https://www.propertyfinder.eg/en/search?l=2254&c=1&t=1&fu=0&ob=mr"
}
],
"maxResultsPerProvider":100,
"deduplicateResults":true,
"threads":3,
"monitoringMode":false
}

Example: direct property URL run

{
"sourceUrls":[
{
"type":"detail",
"url":"https://www.propertyfinder.eg/en/plp/buy/apartment-for-sale-cairo-new-cairo-city-example-12345678.html"
}
],
"includeRaw":true
}

Output

Results are stored in the default Apify dataset. The actor emits normalized listing items, and when monitoringMode is enabled it only emits properties that have not been seen in the tracking store before.

Typical output fields include:

{
"canonicalId":"propertyfinder_eg:12345678",
"offerType":"sale",
"realEstateType":"Apartment",
"price":8500000,
"priceCurrency":"EGP",
"bedrooms":3,
"bathrooms":2,
"area":180,
"areaUnit":"sqm",
"country":"Egypt",
"governorate":"Cairo",
"city":"New Cairo",
"district":"Fifth Settlement",
"street":"North 90 Street",
"gps":{
"lat":30.01,
"lng":31.45
},
"images":[
"https://..."
],
"sourceType":"list"
}

Notes

• listUrls and propertyUrls remain supported for backward compatibility.
• Detail-page enrichment is best-effort and is disabled automatically when no residential proxy hint is detected.
• If retrieveUnitNumber is enabled, the actor expects APIFY_TOKEN to be available so it can call the configured unit-number actor.
• If monitoringMode is enabled and a listing already exists in the tracker store, it will be skipped from the final dataset output.