Rightmove UK Property Scraper (Unofficial)

Scrape Rightmove UK property listings, locations, filters, and property details with normalized output for price monitoring, property research, market research, and real estate workflows.

This is an unofficial actor and is not affiliated with Rightmove.

Proxy behavior

This actor uses the shared Apify proxy contract used across the workspace. rightmove_uk is expected to work in direct mode first, with proxy fallback if the site starts blocking cloud runs. UK proxies are recommended for improved location accuracy.

Supported operations

• probe
• locations
• search_filters
• search
• category
• item

Operation guide

The Apify Console form shows the union of all supported fields, so the visible inputs do not change when you switch operation. Use the guide below to know which fields are required.

• probe Required: none Optional: postcode, location, includeRaw

• locations Required: query Optional: limit, includeRaw

• search_filters Required: one of query, postcode, location, location_identifier, or url Optional: channel, radius, includeRaw

• search Required: one of query, postcode, location, or location_identifier Optional: channel, toRent, newHomes, commercial, radius, priceMin, priceMax, bedroomsMin, bedroomsMax, bathroomsMin, bathroomsMax, propertyType, furnished, mustHave, dontShow, sort, filter, page, limit, includeRaw

• category Required: one of location_identifier, url, postcode, or location Optional: channel, toRent, newHomes, commercial, radius, priceMin, priceMax, bedroomsMin, bedroomsMax, bathroomsMin, bathroomsMax, propertyType, furnished, mustHave, dontShow, sort, filter, page, limit, includeRaw

• item Required: one of propertyId or propertyUrl Optional: includeRaw

Example inputs

These starter examples were validated locally against the live site.

{
  "operation": "probe",
  "location": "Bristol",
  "includeRaw": false
}

{
  "operation": "locations",
  "query": "Bristol",
  "limit": 10,
  "includeRaw": false
}

{
  "operation": "search",
  "query": "Bristol",
  "channel": "sale",
  "page": 1,
  "limit": 24,
  "sort": "newest",
  "includeRaw": false
}

{
  "operation": "category",
  "locationIdentifier": "REGION^219",
  "channel": "sale",
  "page": 1,
  "limit": 24,
  "sort": "newest",
  "includeRaw": false
}

{
  "operation": "item",
  "propertyId": "171636185",
  "includeRaw": false
}

{
  "operation": "search_filters",
  "locationIdentifier": "REGION^219",
  "channel": "sale",
  "radius": 1.0,
  "includeRaw": false
}

Output

• Dataset: normalized property listings, locations, or structured filter rows depending on the operation
• Key-value store OUTPUT: run summary with source, operation, success, total, errors, proxy, and monetization

Output fields (listing)

• id, property_id, url, slug, title, summary
• price, price_pcm, currency, price_display, price_qualifier
• property_type, bedrooms, bathrooms, status
• address, postcode, location, latitude, longitude
• image, images
• added_on, updated_on, added_on_text
• floor_area_sqft, floor_area_sqm
• agent_name, agent_branch, agent_phone
• features, listing_update
• channel, source

Output fields (item - additional)

• short_description, description
• floorplans, brochures, videos, virtual_tour_url
• epc_rating, epc_graphs, council_tax_band
• transaction_type, tenure
• nearest_stations
• review_summary
• heating, parking, garden features
• agent_profile_url, agent_address, agent_logo

Limitations

• Page size on public list pages is capped at 24 listings
• Location identifier format must be TYPE^ID (e.g., REGION^219, OUTCODE^264)
• No browser required - uses HTML/JSON extraction
• Individual review rows not extracted (summary only)