Naver Search Scraper — Korean SERP, Powerlink & Rank Tracker
Pricing
from $1.69 / 1,000 search results
Naver Search Scraper — Korean SERP, Powerlink & Rank Tracker
Naver search scraper for Korean 통합검색 rank tracking. Extract Powerlink ads, blog, cafe, 지식iN, news, Place, shopping, and web as one row per result with block type and position. PC and mobile layouts, batch keywords, JSON export for Python, Node.js, and MCP.
Pricing
from $1.69 / 1,000 search results
Rating
0.0
(0)
Developer
Andrej Kiva
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Disclaimer: Unofficial tool — not affiliated with, sponsored by, or endorsed by NAVER Corp. Data is read from publicly accessible search pages only. No login. You are responsible for complying with applicable law (including Korean personal-data rules where Place cards include business contacts) and the site’s terms. No warranty on accuracy or availability. Provided for informational and research use.
Naver search scraper for 통합검색 rank tracking. Extract Powerlink ads, blog, cafe, 지식iN, news, Place, shopping, and web as one dataset row per result, with query, device, blockType, and position. Built for Korean SEO, AEO visibility, Powerlink monitoring, and scheduled rank jobs. Export JSON via the Apify API, Python / Node.js clients, or MCP.
Best for: SEO agencies, Korean-market teams, and data pipelines that need the real 통합검색 layout — not a vertical Open API dump.
Crawloop Marketplace & E-commerce Suite — keyword SERP scrapers for Naver, Amazon, Shopee, and Mercado Libre.
| Naver Search Scraper ◄── you are here | Amazon Search Scraper | Shopee Search Scraper | Mercado Libre Listings Scraper |
|---|---|---|---|
| Korean 통합검색 blocks, Powerlink, PC/mobile | Amazon keyword SERP, ASIN, badges | Shopee marketplace search cards | LATAM Mercado Libre search |
Also see: AliExpress Search Scraper · eBay Sold Listings Scraper · eBay Sold Price Intelligence
When to use this Actor
- Track Naver keyword rankings by block type (blog vs Place vs shopping vs Powerlink)
- Monitor Powerlink advertisers, titles, and destination URLs on a schedule
- Compare PC vs mobile 통합검색 layouts for the same query
- Snapshot Place visibility (id, rating, review count) for local / restaurant SEO
- Feed Korean SERP rows into Sheets, warehouses, or AI / MCP workflows
When not to use this Actor
- Official Naver Search API replacement — this Actor reads public 통합검색 HTML so you get block order the Open API does not return
- Shopping product detail pages — shopping cards on 통합검색 only, not full PDP specs
- Map reviews or Place full profiles — Place ids and ratings when shown on the SERP card; not a Map crawler
- Blog / cafe full-text — titles, URLs, and snippets, not post bodies
- US/EU Amazon keyword SERP — use Amazon Search Scraper
- SEA marketplace search — use Shopee Search Scraper
- AliExpress retail search — use AliExpress Search Scraper
- Completed-sale comps — use eBay Sold Listings Scraper
Key features
- 통합검색 layout — ranked blocks as they appear on Naver Search, not one isolated vertical
- One row per result —
query,device,blockType,position, title, URL, snippet, source - Powerlink ads — advertiser destination URL when Naver exposes it on the card
- PC and mobile —
device:pc,mobile, orboth - Batch keywords —
queryorqueries, optional pastedsearchUrls - Filters — drop ads, keep selected
blockTypes, cap withmaxItems - URL dedupe — optional unique destinations across a batch (
deduplicateUrls) - Fast HTTP —
curl_cffiChrome TLS impersonation; no headless browser - KR residential proxy — default Apify Proxy group + country KR
Input
| Field | Type | Default | Description |
|---|---|---|---|
query | string | — | Primary search keyword |
queries | string[] | — | Extra keywords, same settings |
searchUrls | string[] | — | Pasted Naver search URLs (query and PC/mobile read from the URL) |
device | enum | pc | pc, mobile, or both |
maxItems | integer | — | Cap rows per keyword and device |
includeAds | boolean | true | Keep Powerlink and shopping ads |
blockTypes | string[] | all | Optional: powerlink, blog, cafe, kin, news, place, shopping, web, influencer, video, ai_overview |
deduplicateUrls | boolean | true | Unique destination URLs across the run |
maxConcurrency | integer | 2 | Parallel keyword/device jobs (1–4) |
proxyConfiguration | object | KR residential | Apify Proxy |
Basic — one keyword, PC layout:
{"query": "아이폰","device": "pc","includeAds": true}
Rank tracker — PC + mobile, selected blocks:
{"queries": ["강남 맛집", "아이폰"],"device": "both","blockTypes": ["powerlink", "blog", "place", "shopping"],"maxItems": 40,"proxyConfiguration": {"useApifyProxy": true,"apifyProxyGroups": ["RESIDENTIAL"],"apifyProxyCountry": "KR"}}
Paste a Naver search URL:
{"searchUrls": ["https://search.naver.com/search.naver?where=nexearch&query=%EA%B0%95%EB%82%A8%20%EB%A7%9B%EC%A7%91"]}
Output
Each dataset item is one SERP row.
| Field | Description |
|---|---|
query | Keyword |
device | pc or mobile |
position | 1-based rank in the parsed layout |
blockType | powerlink, blog, cafe, kin, news, place, shopping, web, influencer, video, ai_overview |
isAd | Powerlink or shopping AD card |
title | Headline |
url | Destination (advertiser URL for Powerlink when available) |
displayUrl | Visible host / site |
snippet | Passage text |
sourceName | Blogger, publisher, shop, or advertiser |
dateText | Relative date on the card |
placeId / rating / reviewCount | Place cards |
priceValue / productId | Shopping cards |
scrapedAt | UTC ISO timestamp |
{"source": "naver_search","query": "아이폰","device": "pc","page": 1,"position": 1,"blockType": "powerlink","isAd": true,"title": "iPhone 18 Pro 요금할인 32%","url": "http://shop.kt.com","displayUrl": "shop.kt.com","snippet": "KT다이렉트샵 초이스더블 요금제","sourceName": "KT다이렉트샵","scrapedAt": "2026-09-20T13:00:00Z"}
Typical workflow
- Run a keyword (or batch) with KR residential proxy and
device: "pc"(or"both"). - Filter with
blockTypes/includeAdsif you only need Powerlink, blog, or Place. - Save as an Actor Task and attach an Apify Schedule for rank tracking.
- Pull the dataset as JSON/CSV, or call the Actor from Python, Node.js, or MCP.
Use cases
| Use case | What you get | Why it helps |
|---|---|---|
| Korean SEO rank tracking | position + blockType per keyword | See whether a brand ranks as blog, Place, or web |
| Powerlink monitoring | Ad titles, advertisers, destination URLs | Track paid competitors on Naver Search |
| Local / Place visibility | Place id, rating, review count | Restaurant and clinic SEO |
| Shopping SERP snapshot | Product id, price, ad vs organic | Compare shopping-block share |
| PC vs mobile | Two layouts for the same query | Catch device-specific ranking gaps |
| Naver API alternative | Layout-faithful rows, not a vertical dump | AEO and rank jobs that need block order |
Integration examples
Node.js
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('crawloop/naver-search-scraper').call({query: '아이폰',device: 'pc',proxyConfiguration: { useApifyProxy: true, apifyProxyGroups: ['RESIDENTIAL'], apifyProxyCountry: 'KR' },});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items.slice(0, 10));
Python
from apify_client import ApifyClientclient = ApifyClient(token)run = client.actor("crawloop/naver-search-scraper").call(run_input={"query": "아이폰","device": "pc","proxyConfiguration": {"useApifyProxy": True,"apifyProxyGroups": ["RESIDENTIAL"],"apifyProxyCountry": "KR",},})for item in client.dataset(run["defaultDatasetId"]).iterate_items():print(item.get("position"), item.get("blockType"), item.get("title"))
cURL
curl "https://api.apify.com/v2/acts/crawloop~naver-search-scraper/runs?token=$APIFY_TOKEN" \-H "Content-Type: application/json" \-d '{"query":"아이폰","device":"pc","proxyConfiguration":{"useApifyProxy":true,"apifyProxyGroups":["RESIDENTIAL"],"apifyProxyCountry":"KR"}}'
MCP and AI assistants
Use this Actor from AI tools via Apify MCP. Connect your Apify account, then call crawloop/naver-search-scraper.
Example prompts:
- "Run Naver Search Scraper for 강남 맛집 on PC and return position, blockType, title, isAd as JSON"
- "Scrape Naver Search for 아이폰 on PC and mobile, then summarize Powerlink advertisers"
- "Chain Naver Search Scraper then Amazon Search Scraper for the same keyword to compare KR vs US SERP"
Suite next step
After a Naver rank dump, run Amazon Search Scraper for the same keyword on US/DE SERP, AliExpress Search Scraper for China retail cards, or Shopee Search Scraper when the query is a product sold across SEA marketplaces. For completed-sale comps, use eBay Sold Listings Scraper.
FAQ
What input do I need?
A keyword in query (or a list in queries), or Naver search URLs in searchUrls. All other parameters are optional.
Is this a Naver API alternative?
Yes, for layout-faithful 통합검색. It is not the official Search API. You get Powerlink / blog / Place / shopping block order that a vertical API dump does not return.
Can I scrape Naver with Python or Node.js?
Yes. Use apify-client as in the examples above, or call the Actor from an AI assistant via Apify MCP.
Can I scrape only blog, Place, or Powerlink?
Yes — set blockTypes to the blocks you want. Powerlink is powerlink. 지식iN is kin.
PC vs mobile?
Naver layouts differ. Use device: "both" for rank jobs that need both.
What if the dataset is empty?
Naver likely blocked the IP. Use Apify KR residential proxy. Datacenter IPs often fail. A scheduled tick can also finish with 0 rows if filters match nothing.
Does it paginate beyond 통합검색 page 1?
v1 parses the main 통합검색 page (the layout Korean SEO actually ranks against). Use maxItems to cap rows on that page.
Troubleshooting
| Issue | Likely cause | What to try |
|---|---|---|
| Empty dataset | Datacenter IP or captcha | Enable KR residential proxy |
| Missing Place or shopping | Query has no local/shopping block | Expected — block mix depends on the keyword |
| Duplicate URLs in a batch | Dedupe disabled | Set deduplicateUrls: true |
| Slow runs | device: both plus many keywords | Lower maxConcurrency or split batches |
Limitations
- KR residential proxy strongly recommended
- 통합검색 page 1 — not vertical tab crawls (View / News / Shop tabs)
- Fields depend on the card — Place ratings and shopping prices appear only when Naver renders them
- Not a full-text blog or review scraper
Related Actors
| Actor | Best for |
|---|---|
| Amazon Search Scraper | US/EU Amazon keyword SERP |
| AliExpress Search Scraper | AliExpress retail search, sold count |
| Shopee Search Scraper | SEA Shopee search cards |
| Mercado Libre Listings Scraper | LATAM Mercado Libre search |
| eBay Sold Listings Scraper | Completed eBay sold comps |
| eBay Sold Price Intelligence | Recommended price, demand, CSV/report |
| 888lots Scraper | Wholesale ASIN lots |
Tags: naver search scraper, naver serp scraper, naver rank tracker, naver powerlink, 통합검색, korean seo scraper, naver blog search, naver place search, naver shopping search, naver api alternative, scrape naver with python, naver mcp