Rightmove Property Page Scraper
Under maintenancePricing
from $10.00 / 1,000 results
Rightmove Property Page Scraper
Under maintenanceCollect comprehensive information about properties listed on Rightmove, including details such as location, price, features, and any other relevant specifications available on the listing pages. pages.
Pricing
from $10.00 / 1,000 results
Rating
0.0
(0)
Developer
Jamshaid Arif
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Share
Rightmove Property Scraper
An Apify actor that scrapes property-for-sale listings from Rightmove and optionally enriches each listing with data pulled from the individual property's detail page (tenure, council tax band, full description, agent address, etc.).
Input
| Field | Type | Default | Notes |
|---|---|---|---|
searchLocation | string | "Newport, South Wales" | Display name in the URL — purely cosmetic. |
locationIdentifier | string | "REGION^991" | Rightmove's internal location code. This is the field that actually controls where the search runs. Find it by inspecting a Rightmove search URL. |
radius | integer | 40 | Miles. Max 40. |
sortType | integer | 2 | 1 featured, 2 highest price, 6 lowest price, 10 newest. |
maxListings | integer | 100 | Stop after this many unique records. |
fetchDetails | boolean | true | Visit each property's detail page for richer fields. Disable for a faster, shallower run. |
listingDelay | integer | 2 | Seconds between listing pages. |
detailDelay | integer | 1 | Seconds between detail-page requests. |
proxyConfiguration | object | Apify Residential, GB | Strongly recommend residential proxies — datacenter IPs get challenged by Cloudflare fast. |
Finding a locationIdentifier
Go to rightmove.co.uk, search for your area, and copy the value of the locationIdentifier URL parameter. Examples:
REGION^991— Newport, South WalesREGION^87490— LondonOUTCODE^2456— a specific postcode areaSTATION^9491— properties near a train station
Output
Each item in the dataset has the listing fields (always present) and, if fetchDetails is enabled, the detail fields too.
Listing fields (from the search results card):
property_id, price, price_qualifier, address, property_type, bedrooms, bathrooms, description, agent_name, added_date, image, details_url, featured
Detail fields (from the property's own page):
detail_address, detail_price, detail_property_type, detail_bedrooms, detail_bathrooms, tenure, floorplan, main_image, full_description, council_tax, parking, garden, map_iframe, street_view, monthly_repayments, detail_agent_name, agent_url, agent_address, recently_sold
Detail keys that overlap with listing keys are prefixed with detail_ so nothing gets silently overwritten — useful if you want to compare what the card said vs. what the detail page said.
