Site realestate.com.auTask extract-property-details-and-sale-historyVersion v7Updated Sep 15, 2026Category real-estate
Extracts structured listing facts, sold details, agent information, and all available historical sale records from a realestate.com.au property page, optionally reached through an agency catalogue or property search result. This skill was captured from a live agent session on realestate.com.au and is published here as a reusable recipe for agents.
NoteSelectors and URL schemes drift as sites change. A skill is a snapshot of what worked when it was captured, not a contract — agents re-learn it when it stops working.
Use this skill for a realestate.com.au property URL, agency catalogue entry, or property-search result when the caller needs normalized listing facts, sold price and date, agent details, coordinates, and every available prior sale record.
Use Cases
Extract facts from a supplied property listing URL.
Reach a property through an agency catalogue and extract its details.
Resolve a property from a supplied search-results URL and classify zero, handful, or large results.
Return sold, current, asking, or price-range information.
Collect all visible prior sale dates and prices, including expanded history.
Automation Flow
For an agency entry point, build https://www.realestate.com.au/find-agent/{suburb}-{state}-{postcode}?pid=rea:hp:search-box-search:find-agent, goto it, and resolve the agency and property links with:
For a supplied search-results URL, goto it, wait for deferred results, classify the result count from visible result cards, and select a property link only when one is present. Do not treat an empty or blocked document as zero results.
Goto the resolved propertyUrl, or use the supplied canonical URL; construct https://www.realestate.com.au/property-{type}-{state}-{suburb}-{listing-id} only when all URL components and the opaque listing ID are supplied.
In the same BQL call, wait 4–8 seconds for deferred content, expand a visible sale-history control if present, wait for the expanded records, then run this evaluate() on the loaded page:
Opaque numeric listing ID already supplied by the caller
444842740
Possible Friction Points
Trigger
Action
HTTP 429, empty snapshot, or bot/interstitial page
Retry the BQL session with an Australian residential proxy; if it persists, return blocked: true and do not report null fields as listing facts.
Homepage or search page returns HTTP 429 even through an Australian residential proxy
Stop repeated navigation attempts and return blocked: true with the interstitial or spelling-correction outcome marked as prevented; do not classify the search as zero results.
Australian residential proxy still returns HTTP 429 after an additional wait
Stop repeated navigation attempts and return blocked: true; do not classify the search as zero results.
Agency catalogue has no accessible links
Retry the BQL session with an Australian residential proxy; do not fabricate an agency or property URL.
Consent or interstitial screen
Complete the visible consent/interstitial in the same BQL session, then wait and rerun the extractor.
Sale-history records are collapsed or deferred
Expand the visible history control, wait for records to render, then rerun the extractor; an empty initial array is not proof of no history.
JSON-LD, agency-link, search-result, or history selectors are unverified on the rendered page
Treat extracted values as unconfirmed until a non-blocked page validates those selectors.