Naver Land Listings

Naver Land Listings collects structured records from Naver Land. Search by keyword (the same search the site's own box performs: complex and region names such as 잠실 or 래미안) and/or paste any new.land.naver.com link: a map search URL (the map area, property types, and transaction filters you set on the site are all encoded in the URL), a single complex page such as new.land.naver.com/complexes/111380, a single listing page such as new.land.naver.com/article/2651481309, or a keyword results URL such as new.land.naver.com/complexes?sk=잠실. Keywords run first, every source is read independently, and results are merged and deduplicated, with identity, transaction, price, area, address, coordinates, and source links. Optional detail retrieval adds fields supplied by the source page.

Why This Scraper?

• Keyword search built in, using the site's own search mechanism.
• Reads any Naver Land URL shape: map search views, complex pages, listing pages, and keyword result URLs.
• Returns stable identifiers for downstream deduplication.
• Includes source labels when the page provides them.
• Preserves the source object in raw for later fields.
• Supports multiple keywords and URLs in one run.
• Supports resumable runs and recurring change detection.

Data You Get

Field	Description	Example
id	Source-derived id field	Sample id
articleNo	Source-derived articleNo field	Sample articleNo
complexNo	Source-derived complexNo field	Sample complexNo
title	Source-derived title field	Sample title
propertyType	Source-derived propertyType field	Sample propertyType
tradeType	Source-derived tradeType field	Sample tradeType
price	Source-derived price field	Sample price
area	Source-derived area field	Sample area
floor	Source-derived floor field	Sample floor
direction	Source-derived direction field	Sample direction
address	Source-derived address field	Sample address
latitude	Source-derived latitude field	Sample latitude
longitude	Source-derived longitude field	Sample longitude
thumbnailUrl	Source-derived thumbnailUrl field	Sample thumbnailUrl
articleUrl	Source-derived articleUrl field	Sample articleUrl
sourceUrl	Source-derived sourceUrl field	Sample sourceUrl
crawledAt	Source-derived crawledAt field	Sample crawledAt
rank	Source-derived rank field	Sample rank
changeType	Source-derived changeType field	Sample changeType
changedFields	Source-derived changedFields field	Sample changedFields
firstSeenAt	Source-derived firstSeenAt field	Sample firstSeenAt
lastSeenAt	Source-derived lastSeenAt field	Sample lastSeenAt
raw	Source-derived raw field	Sample raw

How to Use

Keyword search, URL reading, or both in one run. Keywords are resolved on the site exactly the way its search box resolves them, then read like any other source.

Search by keyword:

{
  "searchKeywords": ["잠실", "래미안"],
  "maxItems": 20
}

A map search URL (set the map area, property types, and transaction filters on the site first, then copy the URL from the browser address bar):

{
  "startUrls": ["https://new.land.naver.com/complexes?ms=2AM2Zq,3zhF96,16&a=APT:ABYG:JGC&e=RETAIL"],
  "maxItems": 20
}

A single complex page, with detail enrichment:

{
  "startUrls": ["https://new.land.naver.com/complexes/111380"],
  "fetchDetails": true,
  "maxItems": 10
}

Recurring monitoring with change detection:

{
  "searchKeywords": ["잠실"],
  "incrementalMode": true,
  "stateKey": "jamsil-watch",
  "emitExpired": true
}

Resume an interrupted collection by supplying resumeFromRunId. Resume and Incremental mode are separate controls.

Send results into your apps (MCP connectors)

Results can also be piped into the apps you already use through Model Context Protocol (MCP) connectors. This is optional and never changes the dataset output.

1. Authorize a connector once under Apify → Settings → API & Integrations (Notion, Linear, Airtable, or Apify).
2. Select it in the mcpConnectors input.
3. For Notion, set notionParentPageUrl to the page under which one page per listing is created.
4. Optionally cap the export with maxNotifyListings (default 50 items per connector per run).

Each connector receives a condensed, human-readable summary per listing: a title plus the key fields (property type, transaction type, price, area, location, and listing link) flattened to plain text. Nested objects collapse to their main value and arrays are trimmed. The complete record, including the full source payload, always stays in the Apify dataset.

Input Parameters

Parameter	Type	Default	Description
searchKeywords	array	prefill	Keyword search on Naver Land (complex and region names); runs before the URLs
startUrls	array	prefill	Naver Land URLs to read: map search URLs, complex pages, listing pages, or keyword result URLs
maxItems	string or object	platform default	Naver Land run setting
fetchDetails	string or object	platform default	Naver Land run setting
resumeFromRunId	string or object	platform default	Naver Land run setting
incrementalMode	string or object	platform default	Naver Land run setting
stateKey	string or object	platform default	Naver Land run setting
emitUnchanged	string or object	platform default	Naver Land run setting
emitExpired	string or object	platform default	Naver Land run setting
mcpConnectors	array	empty	Optional MCP connectors to export results into
notionParentPageUrl	string	empty	Notion parent page for the Notion connector export
maxNotifyListings	integer	50	Cap on items written to each connector per run
proxy	string or object	platform default	Naver Land run setting

Output Example

Sample shape: values are illustrative placeholders, not from a live listing.

{
  "id": "00000001",
  "articleNo": "00000001",
  "complexNo": "00000001",
  "title": "Sample Listing Title",
  "propertyType": "Apartment",
  "tradeType": "For sale",
  "price": "Sample price",
  "area": "84.00 square metres",
  "address": "Sample district",
  "latitude": 37.0000,
  "longitude": 127.0000,
  "articleUrl": "https://example.com/listing/00000001",
  "sourceUrl": "https://example.com/map",
  "changeType": "NEW",
  "changedFields": [],
  "firstSeenAt": "2026-01-01T00:00:00+00:00",
  "lastSeenAt": "2026-01-01T00:00:00+00:00",
  "raw": {}
}

Plan Requirement

An Apify account and a run connection that can reach the source are required. Keep the default input connection settings unless your account requires a different configuration.