Naver Land Scraper at a glance
Naver Land Scraper is a ready-to-run Apify actor from abotapi for collecting web data. Its documented output includes id, title, type, transaction and price, which you can export as JSON, CSV or Excel or read through the Apify API. It costs $2.40 per 1,000 results on the Apify Free plan and from $1.50 on paid plans, with smaller per-run or optional feature charges listed on Apify.
- Runs on
- Apify cloud: console, API, schedules and integrations
- Data type
- Web data
- Pricing
- $2.40 per 1,000 results (Free plan), from $1.50 on paid plans
- Output
- Documented below · JSON, CSV, Excel
- Inputs
- 21 options
Scrape structured property listings from Naver Land map URLs. Extract listing titles, prices, areas, addresses, GPS coordinates, property types, transaction types and source links for clean real estate datasets.
What Naver Land Scraper can do
- Keyword search built in. Search Naver Land the same way its own search box does, by complex or region name, with no need to reverse-engineer a URL.
- Reads any Naver Land link. Map search views, single complex pages, single listing pages, and keyword result pages all work from the same input field.
- Stable identifiers. Every record keeps the source's own article or complex number as its id, so downstream deduplication survives across runs.
- Optional detail enrichment. Turn on Fetch listing details to add fields drawn from a listing's own page, billed only for the listings that actually receive them.
- Nothing lost. The complete source record for every listing is preserved in raw, even for fields not broken out into their own columns.
- Multiple sources per run. Supply several keywords and links together; results are merged and deduplicated by id automatically.
Choose what to collect
These inputs let you configure Naver Land Scraper - Property Listings, Prices & Locations. Open the actor on Apify to enter your values and review the current options.
| Input | What it controls |
|---|---|
searchKeywordsarray | Keyword search on Naver Land, exactly as the site's own search box does it: complex and region names such as 잠실 or 래미안. Each keyword is resolved on the site and its matching complexes are returned. Keywords run before the URLs below, and all results are merged and deduplicated. If you give no keyword and no link at all, the run searches the example keyword 잠실 so it still returns listings. |
startUrlsarray | Any new.land.naver.com link works. Paste a map search URL (set the visible map area, property types, and transaction filters on the site, then copy 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=잠실. Each URL is read independently and results are merged. Links from fin.land.naver.com/articles/ and m.land.naver.com/article/info/ are converted to the listing page; any other unsupported link is skipped with a warning in the log. |
locationsarray | Korean region names such as 강남구 or 잠실. Same as Search keywords; both are accepted and merged. |
dealTypestring | Keep only this transaction type. Listings that do not match are not returned or billed. |
propertyTypesarray | Keep only these property types. Empty means all. |
minPriceinteger | Deposit or sale price, in won. 0 means no limit. |
maxPriceinteger | Deposit or sale price, in won. 0 means no limit. |
Show 14 more inputs
| Input | What it controls |
|---|---|
minAreainteger | Exclusive area. 0 means no limit. |
maxAreainteger | Exclusive area. 0 means no limit. |
onlyOwnersboolean | Keep only listings carrying Naver's owner-verified badge. |
maxItemsinteger | Maximum number of unique records returned across all URLs. |
fetchDetailsboolean | Fetch additional detail fields for article cards when available. |
resumeFromRunIdstring | Paste a previous run ID or dataset ID to skip records already collected. |
incrementalModeboolean | Track NEW, UPDATED, UNCHANGED, REAPPEARED, and EXPIRED records for this URL scope. |
stateKeystring | Optional name for the recurring monitoring scope. With your own State key and no keyword or link, the run stops with an input message instead of searching the example keyword. |
emitUnchangedboolean | Include records whose source-derived fields did not change. |
emitExpiredboolean | Include records absent from a complete incremental scan. |
ignoreFieldsForChangesarray | Field names (dotted paths allowed, e.g. raw.someKey) that never count as a change in incremental mode. They stay in the output. Thumbnail links are ignored by default. |
mcpConnectorsarray | Optionally send results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize one under Apify → Settings → API & Integrations, then select it here. Notion gets a rich page-per-item export; other connectors get a best-effort write/digest. Leave empty to skip: this never changes the dataset output. Supported: Notion (https://mcp.notion.com/mcp), Linear (https://mcp.linear.app/sse), Airtable (https://mcp.airtable.com/mcp), Apify (https://mcp.apify.com). |
notionParentPageUrlstring | URL (or id) of the Notion page under which item pages are created. Required to enable the Notion export; ignored by other connectors. |
maxNotifyListingsinteger | Cap on items written to each connector per run. Does not affect the dataset. |
Fields in the output
The documented dataset includes the fields below. Availability can depend on the source page and selected mode.
idID (text)titleTitle (text)propertyTypeType (text)tradeTypeTransaction (text)pricePrice (text)areaArea (text)floorFloor (text)addressAddress (text)latitudeLatitude (number)longitudeLongitude (number)articleUrlListing URL (link)listingIdlistingId (text)Show 42 more fields
buildingNamebuildingName (text)dealTypedealType (text)dealTypeKodealTypeKo (text)propertyTypeKopropertyTypeKo (text)rentPricerentPrice (text)managementFeemanagementFee (text)areaExclusiveareaExclusive (text)areaSupplyareaSupply (text)totalFloorstotalFloors (text)directiondirection (text)buildYearbuildYear (text)citycity (text)districtdistrict (text)neighbourhoodneighbourhood (text)isOwnerVerifiedisOwnerVerified (text)confirmedDateconfirmedDate (text)brokerageNamebrokerageName (text)brokerNamebrokerName (text)sameAddressCountsameAddressCount (text)photoCountphotoCount (text)thumbnailUrlthumbnailUrl (text)featureTextfeatureText (text)isDirectTradeisDirectTrade (text)roomCountroomCount (text)bathRoomCountbathRoomCount (text)parkingCountparkingCount (text)parkingPerHouseholdparkingPerHousehold (text)movingInTypemovingInType (text)movingInNegotiablemovingInNegotiable (text)priceLabelpriceLabel (text)regionCoderegionCode (text)detailUrldetailUrl (text)urlurl (text)complexNumbercomplexNumber (text)unitunit (text)priceChangeStatuspriceChangeStatus (text)areaSupplyLabelareaSupplyLabel (text)changeTypeChange (text)changedFieldsChanged fields (text)firstSeenAtFirst seen (text)lastSeenAtLast seen (text)detailFetchedDetails fetched (text)Example output
An example from this actor’s documentation. Values are illustrative; this is not a fresh live result.
{
"id": "9988770011",
"articleNo": "9988770011",
"complexNo": "700123",
"title": "샘플아파트 101동 84A타입",
"propertyType": "아파트",
"tradeType": "매매",
"price": "12억 5,000",
"area": "84.97",
"floor": "12/25",
"direction": "남향",
"address": "서울특별시 샘플구 샘플동 12-3",
"latitude": 37.5,
"longitude": 127,
"thumbnailUrl": "https://landthumb-phinf.pstatic.net/sample/sample_1.jpg",
"articleUrl": "https://new.land.naver.com/article/9988770011",
"sourceUrl": "https://new.land.naver.com/complexes?sk=샘플동",
"detailFetched": false,
"crawledAt": "2026-01-01T00:00:00+00:00",
"rank": 1,
"raw": {}
}Ways to use this data
- Property investors and analysts: track price and inventory changes for specific complexes or neighborhoods over time.
- PropTech tools and internal feeds: build a searchable, deduplicated feed of current listings without visiting the site by hand.
- Market researchers: compare a region's sale, jeonse and monthly-rent mix across scheduled runs.
- Relocation and site-selection planning: pull comparable listings for a target complex or district before a negotiation.
- Data and analytics teams: feed price and area history into a dashboard using Incremental mode's changedFields.
Before you run
Start with a small input and check the resulting records against your expected fields. Source content and actor options can change; the current Apify listing is the reference for availability and pricing.
Questions about this actor
What data does Naver Land Scraper return?
The documented output for Naver Land Scraper includes id, title, type, transaction, price, area, floor and address. Availability of each field depends on the source page and the selected mode.
How much does Naver Land Scraper cost?
It costs $2.40 per 1,000 results on the Apify Free plan and from $1.50 on paid plans, with smaller per-run or optional feature charges listed on Apify. The Apify listing shows the current rate for every plan.
Can I get only new, changed or removed listings on a schedule?
Yes. Schedule the actor from the Schedules tab and turn on Incremental mode with a State key you choose. To ever see a REAPPEARED listing later, also turn on Emit expired listings: that is the only setting that lets the actor record a listing as gone in the first place. Leaving it off means a listing that vanishes and later comes back is simply reported as UPDATED or UNCHANGED against its last known snapshot, never REAPPEARED.
What is the difference between Resume and Incremental mode?
Resume continues one specific interrupted run by its run or dataset ID, skipping listings that run already collected; it is a one-off catch-up. Incremental mode instead keeps a standing baseline for a whole scope (keywords, URLs, and the detail setting) across separate scheduled runs, and classifies each listing as new, updated, unchanged, reappeared or expired. The two cannot be used in the same run.
Why did my run fail instead of returning an empty dataset?
If every page in the run is refused, the run stops with a clear message so a genuine empty result (a rendered page with no listings) is never confused with a page that could not be read at all. If only some pages were refused, the run still finishes and delivers what it could read, with a status message naming how many pages were missed.
Can I use it with AI agents or MCP?
Yes. Call it from any Apify integration or MCP client, and use the connector field to push a summary of each listing into Notion, Linear or Airtable.
