Rightmove Scraper — UK Property Listings | $0.90/1K | No Login

Built for UK property investors, PropTech teams, and real estate agents who need daily market intelligence from the UK's largest portal (10M+ monthly visitors).

$0.90 per 1,000 listings — only pay for results delivered.

Scrape UK property listings from rightmove.co.uk — the UK's largest property portal with 10,000+ listings per region.

What it does

Extracts structured listing data from any Rightmove search URL (for sale or to rent):

• Price (numeric GBP, currency code)
• Address (full display address, city, postcode)
• Bedrooms & bathrooms
• Property type (Apartment, Terraced, Detached, etc.)
• Coordinates (lat/lng for map plotting)
• Agent (name, branch, phone)
• Images (all photo URLs + main image)
• Dates (listed date, updated date)
• Tenure type (Freehold / Leasehold)
• parse_confidence — quality score per listing (our reliability edge)

How to use

1. Go to rightmove.co.uk and run your property search (any location, filters, sale/rent).
2. Copy the full search URL from your browser.
3. Paste it into the searchUrl input field.
4. Set maxItems to control how many listings to fetch.

Example input

{
  "searchUrl": "https://www.rightmove.co.uk/property-for-sale/find.html?searchType=SALE&locationIdentifier=REGION%5E92829&numberOfPropertiesPerPage=24",
  "maxItems": 200
}

Output schema

Field	Type	Description
listing_id	integer	Rightmove property ID
title	string	Property type description
description	string	Listing summary
price	integer	Price in GBP
currency	string	"GBP"
address	string	Full display address
city	string	City (derived)
postcode	string	UK postcode
bedrooms	integer	Number of bedrooms
bathrooms	integer	Number of bathrooms
property_type	string	Property sub-type
lat	float	Latitude
lng	float	Longitude
agent_name	string	Estate agent name
agent_branch	string	Branch name
agent_phone	string	Contact phone
url	string	Rightmove listing URL
image_url	string	Main image URL
images	array	All image URLs
date_listed	string	ISO 8601 listing date
date_updated	string	ISO 8601 last updated
tenure_type	string	FREEHOLD / LEASEHOLD
transaction_type	string	buy / rent
scraped_at	string	ISO 8601 UTC scrape time
parse_confidence	float	Data quality score (0–1)
warnings	array	Quality warning codes

Output sample

{
  "listing_id": 148293750,
  "title": "2 bedroom apartment for sale",
  "price": 425000,
  "currency": "GBP",
  "address": "Flat 12, Battersea Square, London, SW11 3RA",
  "city": "London",
  "postcode": "SW11 3RA",
  "bedrooms": 2,
  "bathrooms": 1,
  "property_type": "Apartment",
  "agent_name": "Savills",
  "agent_phone": "020 3903 2890",
  "lat": 51.4774,
  "lng": -0.1657,
  "tenure_type": "LEASEHOLD",
  "transaction_type": "buy",
  "url": "https://www.rightmove.co.uk/properties/148293750",
  "parse_confidence": 1.0,
  "warnings": []
}

Pricing example

Run size	Cost
100 listings	~$0.09
1,000 listings	~$0.90
10,000 listings	~$9.00

Agent phone, coordinates, and tenure are included in every listing — no extra charge.

FAQ

Do I need a Rightmove account or proxy? No account, no proxy. Works clean from Apify cloud IPs.

What output formats are available? JSON, CSV, Excel, XML — all via the Apify dataset download or API.

Can I schedule it to run daily? Yes — use Apify Schedules (cron) to run the actor daily and push new results to your webhook, Google Sheets, or Airtable.

What if it returns empty results? Check that your searchUrl is a valid Rightmove search URL (must contain locationIdentifier). The actor logs the issue and exits cleanly with 0 results rather than crashing.

Why this actor vs. competitors

Feature	This actor	epctex/rightmove-scraper ($3/1K)	Typical Rightmove scraper
parse_confidence field	Yes	No	No
Agent phone extracted	Yes	No	Rarely
Tenure type (Freehold/Leasehold)	Yes	No	No
Source	__NEXT_DATA__ JSON	DOM / brittle CSS	DOM / brittle CSS
Proxy required	No	Yes	Often yes
Price per 1K listings	$0.90	$3.00	varies

No login required. No proxy setup. Works from Apify cloud IPs. 3× cheaper than epctex with a per-listing quality score.

parse_confidence

Every listing includes a parse_confidence score (0–1). Score < 0.8 means one or more critical fields are missing — check the warnings array before relying on those records.

Technical notes

• Data source: Rightmove's __NEXT_DATA__ embedded JSON (reliable, no brittle HTML parsing)
• No proxy required from Apify cloud IPs
• Pagination handled automatically

Pricing

Pay-Per-Event (PPE) — a single, simple event:

Event	Price
listing-item	$0.90 / 1,000 listings

Every listing includes price, address, bedrooms, bathrooms, coordinates, agent name + phone, tenure, images, and dates — all in the one per-listing price. No add-on charges.

Integrations

Built for UK property investors, PropTech teams, and agents tracking daily listing data across the UK's largest portal — the JSON/dataset output drops into the tools you already run, no glue code:

• n8n / Make / Zapier — trigger a run or pipe every new dataset item into 500+ apps (Google Sheets, Airtable, Slack, HubSpot, your database) with no code: n8n, Make, Zapier.
• Webhooks — fire your own endpoint the moment a run finishes, to push results straight into your pipeline (docs).
• MCP server — expose this actor as a tool to Claude, Cursor, or any MCP client so an AI agent can pull this data mid-conversation (guide).
• API & SDKs — fetch the dataset as JSON, CSV, or Excel through the Apify REST API or the Python / JS SDKs.

See all Apify integrations.

Disclaimer

This actor is not affiliated with Rightmove. Use in accordance with Rightmove's Terms of Service.

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• Dubai Property Scraper
• Onthemarket Properties Scraper
• Realtor Scraper
• Redfin Scraper
• Zillow Scraper
• Zoopla Properties Scraper

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.