Rightmove Property Discovery Scraper

Discover public Rightmove property listings from simple inputs: UK location, sale or rent, property type, and maximum results. The Actor searches Rightmove and returns structured UK real estate rows with listing URLs, prices, rooms, areas, descriptions, images, agents, timestamps, and optional workflow IDs.

Use it when you need a repeatable Rightmove property dataset without manually finding location identifiers, copying result cards, or normalizing listing fields by hand.

What does Rightmove Property Discovery Scraper do?

Rightmove Property Discovery Scraper converts a UK city search such as London into a clean Apify dataset of public Rightmove listings.

It can:

• search a curated set of major UK cities with stable Rightmove location identifiers
• collect sale or rental listings with operation
• request broad property types such as any, apartment, house, land, or commercial
• return listing identifiers, titles, URLs, prices, areas, bedrooms, bathrooms, addresses, descriptions, feature lists, seller names, images, and timestamps
• append results to an existing dataset through datasetId
• copy a workflow identifier into every row with runId

This is a discovery Actor. You provide search criteria, not Rightmove search-result URLs.

Why use this Rightmove scraper?

Use case	How it helps
UK property lead discovery	Build listing datasets for London, Manchester, Birmingham, Leeds, Liverpool, Bristol, Edinburgh, Glasgow, and other supported city-level searches.
Rental and sale monitoring	Schedule recurring Rightmove searches and compare new rows over time.
Market analysis	Compare price, priceText, areaM2, bedrooms, bathrooms, and city across listings.
Agency and proptech workflows	Feed normalized property rows into dashboards, CRM enrichment, valuation research, or lead scoring.
Multi-source real estate datasets	Combine Rightmove rows with other TroveVault property discovery Actors using datasetId and runId.

What data does it return?

Each dataset item represents one public Rightmove listing when the field is visible in search-result data.

Field	Description
platform	Source platform, normally Rightmove.
listingId	Listing identifier when exposed or derived from the public URL.
title	Listing headline.
url	Public Rightmove listing URL.
operation	Requested operation, such as sale or rent.
propertyType	Requested property type.
price, currency, priceText	Numeric price when parseable, currency, and original display text.
pricePerM2	Calculated only when both price and area are available.
areaM2, bedrooms, bathrooms	Main size and room attributes when visible.
address, city, country	Parsed listing location.
description, features	Public description and feature list when available.
sellerName	Agent, branch, or seller name when visible.
mainImage, images	Main image URL and gallery URLs when available.
listedAtText	Listing date or freshness text when exposed.
scrapedAt	ISO timestamp for when the row was collected.
runId	Optional workflow ID copied from input.

How do I run Rightmove Property Discovery Scraper?

1. Enter a supported UK city in Location, for example London.
2. Choose Operation: sale or rent.
3. Choose Property Type: any, apartment, house, land, or commercial.
4. Set Maximum Items for the number of listings to save.
5. Start the Actor and export results as JSON, CSV, Excel, or through the Apify API.

For quick validation, start with maxItems: 3. For broader discovery, increase the limit after confirming the city and property type return the kind of listings you need.

What input does it accept?

{
  "location": "London",
  "operation": "sale",
  "propertyType": "any",
  "maxItems": 25,
  "datasetId": "",
  "runId": "rightmove-london-sale-2026-08-17"
}

Input	Type	Required	Description
location	String	Yes	Major UK city to search. Examples: London, Manchester, Birmingham, Leeds, Liverpool, Bristol, Edinburgh, Glasgow.
operation	String	Yes	Use sale for properties for sale or rent for rental listings. Default: sale.
propertyType	String	Yes	One of any, apartment, house, land, or commercial. Default: apartment.
maxItems	Integer	No	Maximum listings to save, from 1 to 1000. Default: 3.
datasetId	String	No	Existing Apify dataset ID to append results to in addition to the default run dataset.
runId	String	No	Workflow or parent run ID copied into rows and the RUN_SUMMARY record.

What output should I expect?

{
  "platform": "Rightmove",
  "listingId": "example-listing-id",
  "title": "2 bedroom flat for sale in London",
  "url": "https://www.rightmove.co.uk/properties/example",
  "operation": "sale",
  "propertyType": "any",
  "price": 750000,
  "currency": "GBP",
  "priceText": "GBP 750,000",
  "pricePerM2": null,
  "areaM2": null,
  "bedrooms": 2,
  "bathrooms": 1,
  "address": "London",
  "city": "London",
  "country": "United Kingdom",
  "description": "Public listing description when available.",
  "features": ["Leasehold", "Balcony"],
  "sellerName": "Example Estate Agent",
  "mainImage": "https://example.com/rightmove-image.jpg",
  "images": ["https://example.com/rightmove-image.jpg"],
  "listedAtText": null,
  "scrapedAt": "2026-08-17T10:00:00.000Z",
  "runId": "rightmove-london-sale-2026-08-17"
}

Null values mean Rightmove did not expose that field in the public search data or it could not be parsed safely.

How can I use it through the Apify API?

curl -X POST "https://api.apify.com/v2/acts/trovevault~rightmove-property-discovery-scraper/runs" \
  -H "Authorization: Bearer <APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{
    "location": "London",
    "operation": "sale",
    "propertyType": "any",
    "maxItems": 25,
    "runId": "rightmove-london-sale-2026-08-17"
  }'

Use the run details to access the default dataset, or pass datasetId to append Rightmove rows into a shared dataset used by a larger workflow.

How much does it cost?

This Actor uses Apify pay-per-event pricing. Runtime depends mostly on maxItems, source response speed, and how many listing rows can be normalized for the selected city.

Cost controls:

• test new city searches with a small maxItems value
• use supported city names rather than broad regional text
• split broader research into separate city runs
• schedule only the searches you actively monitor

How do I troubleshoot common issues?

Issue	Likely cause	What to do
No listings returned	The city is unsupported, misspelled, or has no public Rightmove matches for the selected filters.	Try a supported city such as London, set propertyType: "any", and reduce filters.
Fewer rows than maxItems	Rightmove exposed fewer matching listings or some rows could not be normalized safely.	Treat maxItems as a cap. Broaden the search or run another city.
Missing area or pricePerM2	The source row did not expose area data.	Use priceText, bedrooms, and bathrooms; keep null-aware downstream logic.
Unsupported location	This version uses a curated set of stable Rightmove location identifiers.	Use one of the documented major cities or open an issue requesting another city.
Run is slow on a large batch	The source is responding slowly or the batch is too broad.	Lower maxItems and split by city or operation.

What are the limitations?

• It reads public Rightmove search-result data only; it does not access accounts, agent dashboards, private data, or hidden feeds.
• This version supports a curated set of major UK cities with stable Rightmove location identifiers.
• Search-result JSON keeps runs lightweight, but some detail-page fields may be missing if not exposed in search data.
• Prices, availability, and listing details can change after scraping.
• pricePerM2 is calculated only when both source price and area are available.
• This Actor is for data collection and workflow automation; it is not legal, investment, or valuation advice.

FAQ

Can I provide a Rightmove search URL?
No. This Actor discovers listings from structured inputs: location, operation, propertyType, and maxItems.

Why are only some UK locations supported?
Rightmove searches depend on internal location identifiers. This Actor prioritizes a curated set of major cities with stable identifiers so Store tests and scheduled jobs stay reliable.

Can I combine Rightmove with other portals?
Yes. Use datasetId for a shared dataset and runId to label which workflow or batch produced each row.

Does it return every Rightmove listing?
No. It returns public listings that can be discovered and normalized for the selected search. Source coverage and availability can change.

Support

Open an issue on the Actor page with the input JSON, run ID, expected city, and a short description of the problem. Include a sample listing URL when the issue is about a missing or misparsed field.