Naver Shopping Scraper: Korea Products & Prices avatar

Naver Shopping Scraper: Korea Products & Prices

Pricing

from $1.30 / 1,000 products

Go to Apify Store
Naver Shopping Scraper: Korea Products & Prices

Naver Shopping Scraper: Korea Products & Prices

Search Naver Shopping (Korea) by keyword and get products with price, lowest price, seller count, mall, brand, reviews, rating, category IDs, ad flag and links. Price range filter, sorting, up to 1,000 products per keyword. No login.

Pricing

from $1.30 / 1,000 products

Rating

0.0

(0)

Developer

Cliqto Media

Cliqto Media

Maintained by Community

Actor stats

1

Bookmarked

3

Total users

2

Monthly active users

7 days ago

Last modified

Share

Search Naver Shopping (네이버 쇼핑), Korea's largest shopping search, by keyword and get one row per product with price, lowest price, seller count, mall, brand, reviews, rating, ad flag and links.

Use it for Korean price research, competitor and brand tracking, or product lists. The smallest run is one keyword: 무선 이어폰 gives 20 products in about 15 seconds. No login, no cookies, no API key.

Naver Shopping Scraper: a Korean keyword goes in, product rows with price, lowest price, sellers, reviews and ad flag come out as JSON or CSV

Table of contents

What it does

The Actor opens the public Naver Shopping search results for each keyword, the same list a shopper sees on a phone. It reads every product card and saves one clean row per product. It can go deeper than the first page: up to 1,000 products per keyword.

  • Catalog cards (price comparison pages) give the shown price, the lowest price and the number of sellers.
  • Single-seller cards give the price, the list price before discount, the discount, the mall name and the purchase count.
  • Sponsored listings are kept and marked with isAd: true. You can turn them off.
  • Each row has the keyword, its position, the source and the time we read it.

Good fit

  • Check the market price of a product in Korea, with the lowest price across sellers.
  • Watch which brands, malls and ads show up for your keywords.
  • Build a product list for a category keyword with reviews and ratings.

Not a fit / limits

  • Search results only. Product detail pages (options, stock, full review text, seller lists) are not included.
  • Naver's ranking is personal and changes during the day. Two runs can show a different order.
  • This is not a drop-in replacement for scrapers that expand each catalog into all its sellers.

Quick start

  1. Open the Input tab.
  2. Add one keyword to Search keywords (queries), for example 무선 이어폰. Korean keywords give the best results.
  3. Keep Products per keyword (maxItems) at 20 for a first test.
  4. Click Start.
  5. Open the Products view in the Output tab.

Expected result: 20 product rows for the keyword, each with title, price, reviewCount and url.

Use cases

Buyer jobInput pathOutput entityKey fieldsNext step
Price check for a productqueries + minPrice/maxPriceproductprice, lowPrice, sellerCount, mallExport to a sheet, convert KRW
Brand and ad watchqueries, includeAds: trueproductbrand, maker, isAd, positionSchedule a daily run
Category product listqueries, maxItems: 1000producttitle, reviewCount, rating, categoryIdLoad the dataset by API

Input

Input fields

FieldPlain nameTypeRequiredDefault / prefillAllowed valuesEffectExampleRecommendation
queriesSearch keywordsarray of stringsyesprefill ["무선 이어폰"]1–20 keywords, each up to 100 charactersOne search per keyword["선풍기", "립스틱"]Use Korean words. Duplicates are run once.
maxItemsProducts per keywordintegernodefault 50, prefill 201–1,000Stops each keyword after this many products300More products means more requests and a longer run.
minPriceMinimum priceinteger (KRW)noempty0–1,000,000,000Naver filters by price10000Use with maxPrice to skip accessories.
maxPriceMaximum priceinteger (KRW)noempty0–1,000,000,000Naver filters by price300000Must be ≥ minPrice.
sortSortstringnorelevancerelevance, price_asc, price_desc, review_count, ratingOrders the collected productsprice_ascSee the note below.
includeAdsInclude sponsored listingsbooleannotruetrue / falsefalse drops ad cardsfalseKeep true for ad research.
addBrandNamesAdd brand and makerbooleannotruetrue / falseFills brand and maker from Naver's filterstrueTurn off for slightly faster runs.

Empty queries or a wrong range stops the run at once with a clear message and no charge for products.

Interacting settings

WhenInput AInput BEffective behaviorCost/result effect
Sort is not relevancesortmaxItemsThe Actor first collects maxItems products in Naver's order, then sorts them. price_asc gives the cheapest of those products, not the cheapest on all of Naver.None
Ads are offincludeAds: falsemaxItemsAd cards are skipped and organic products fill the list.Same price per product
Price range is setminPrice / maxPricequeriesNaver applies the range before the list is read.Fewer products if the range is narrow

Input examples

Price check with a price range

{
"queries": ["무선 이어폰"],
"maxItems": 100,
"minPrice": 10000,
"maxPrice": 300000,
"includeAds": false
}

Expected behavior: one search, sponsored cards removed, prices between ₩10,000 and ₩300,000. Expected output: up to 100 product rows with price, lowPrice, sellerCount, mall.

Several keywords, deep lists

{
"queries": ["선풍기", "강아지 사료", "립스틱"],
"maxItems": 300
}

Expected behavior: 900 rows in about 45 seconds (measured).

Output

Output example

A real row for 무선 이어폰 (some fields trimmed):

{
"recordType": "product",
"status": "complete",
"query": "무선 이어폰",
"position": 8,
"productId": "56796984706",
"title": "삼성전자 갤럭시 무선이어폰 버즈3 FE SM-R420N 노이즈 캔슬링 그레이",
"price": 143000,
"originalPrice": null,
"discountRate": null,
"lowPrice": 132990,
"currency": "KRW",
"listingType": "catalog",
"sellerCount": 71,
"mall": null,
"brand": "갤럭시",
"reviewCount": 8467,
"rating": 4.9,
"purchaseCount": null,
"isAd": false,
"url": "https://search.shopping.naver.com/catalog/56796984706",
"source": "naver_shopping_mobile_search",
"sourceUrl": "https://m.search.naver.com/search.naver?where=m_shop&query=%EB%AC%B4%EC%84%A0+%EC%9D%B4%EC%96%B4%ED%8F%B0",
"fetchedAt": "2026-10-14T12:35:23.121Z"
}

Empty values are null, never 0. A 0 means a real zero (for example, free delivery).

Output fields

FieldMeaningTypeCan be empty?Example / enum
recordTypeRow typestringnoproduct, query
statusRow qualitystringnocomplete, partial (some fields missing); query rows: not_found, error
queryYour keywordstringno무선 이어폰
positionPlace in the result list, starting at 1integerno8
productIdNaver product ID (nvMid), stablestringno56796984706
titleProduct name, HTML removedstringno필립스 ENC 블루투스 무선 오픈형 이어폰 TAQ4000
pricePrice the shopper sees first, KRWnumberyes59000
originalPricePrice before discountnumberyes115000
discountRateDiscount in %numberyes48
lowPriceLowest price shown by Naver; for catalogs, across sellersnumberyes132990
currencyAlways KRWstringnoKRW
listingTypeCatalog (price comparison) or one sellerstringnocatalog, single_seller
sellerCountSellers in the catalog; 1 for single-seller cardsintegeryes71
mallStore name (single-seller cards)stringyes필립스 오디오 공식몰
brand / makerBrand or manufacturer, from Naver's filtersstringyes삼성전자
categoryId / categoryIdsNaver category IDs, leaf and pathstring / arrayyes50002327
reviewCountNumber of reviews (catalogs: total across sellers)integeryes8467
ratingAverage rating 0–5numberyes4.9
purchaseCountPurchases shown by Naver (single-seller only)integeryes1200
wishlistCountWishlist (찜) countintegeryes340
deliveryFeeDelivery fee, KRW; 0 = freeintegeryes0
isAdSponsored listingbooleannotrue
isSmartStore / isBrandStore / isOverseasStore flagsbooleanyestrue
smartStoreProductIdSmart Store product numberstringyes11223344556
url / mobileUrlProduct or catalog linkstringyeshttps://search.shopping.naver.com/catalog/...
imageMain imagestringyeshttps://shopping-phinf.pstatic.net/...
missingFieldsWhich key fields were missingarrayno["mall"]
sourceWhere the row came fromstringnonaver_shopping_mobile_search
sourceUrlSearch page for the keyword (without your filters)stringnohttps://m.search.naver.com/...
fetchedAtWhen we read it (UTC)stringno2026-10-14T12:35:23.121Z
message / errorCodeQuery rows only: what happenedstringyesNaver Shopping has no products for this keyword and filters

Output entities and surfaces

SituationWhereResult shapeWhat to do
Normal productDataset, view Productsone product row per productExport or use by API
Keyword with no productsDatasetone free query row, status: not_foundCheck the spelling or the price range
Keyword failed (block, timeout)Dataset + RUN_SUMMARYone free query row, status: error, errorCodeRun that keyword again later
Run summaryKey-value store RUN_SUMMARYstatus, counts, per-keyword depth, warningsCheck status and message

RUN_SUMMARY → status tells you the result: COMPLETE, NO_RESULTS, PARTIAL or CAPPED (your spending limit was reached). When a run stops early (PARTIAL or CAPPED), the run status message in Console also says why.

Pricing and limits

Pricing unit

Pay per event. You pay for each product row saved, plus a small start fee per run. not_found and error rows are free. Platform usage is included: you do not pay for compute.

EventFree planBronzeSilverGold and higher
Product (one row)$0.0015$0.0014$0.00135$0.0013
Run start$0.004$0.004$0.004$0.004

A run with no products (all keywords not found, or a price range with no matches) costs only the start fee, $0.004. A partial run pays only for the rows it saved.

Cost examples (Free plan)

ScenarioInput scopeProductsCost
First test1 keyword × 2020$0.034
Normal3 keywords × 300900$1.354
Large5 keywords × 1,0005,000$7.504
No results20 unknown keywords0$0.004

If you set a maximum cost per run, the Actor stops before it goes over, keeps the rows it saved and ends with status CAPPED.

Limits

  • Up to 20 keywords and 1,000 products per keyword per run.
  • Speed: about 1,000 products in 20 seconds. Each keyword takes at least 3–15 seconds, even for a few products, because brand names need extra requests (20 keywords × 1 product took about 3 minutes). Set addBrandNames to false for faster small runs. 20 keywords × 1,000 products took 350 seconds. The default timeout is 300 seconds, so for more than about 15,000 products set a longer timeout (for example 600 seconds) in the run options. If time runs out, the run keeps what it saved, ends as PARTIAL and lists the keywords it did not start.
  • A few keywords show a short list on Naver (for example hotel or travel words). Then you may get fewer products than maxItems.

API, export and integrations

  • Export: download the dataset as JSON, CSV, Excel or HTML from the Output tab.
  • API: start runs and read the dataset with the Apify API or the Apify client.
  • Scheduling: run the same keywords every day with Apify schedules and compare price and position over time.
  • No-code: connect the dataset to Google Sheets, Make or Zapier through Apify integrations.

Use with AI agents (MCP)

  • MCP server URL with only this Actor: https://mcp.apify.com?tools=cliqtomedia/naver-shopping-scraper
  • Smallest useful input:
{ "queries": ["무선 이어폰"], "maxItems": 20 }
  • Key output fields: title (product name), price and lowPrice (KRW), reviewCount and rating, isAd, url.
  • A 20-product call takes about 15 seconds and costs $0.034 on the Free plan. Keep to 20 keywords and 1,000 products per keyword.

Troubleshooting

I got fewer products than maxItems

Symptom: the keyword has fewer rows than you asked for. Likely reason: Naver shows a short list for this keyword or price range. Check: RUN_SUMMARY → the keyword's depth, and the price range. Action: widen the price range or use a broader keyword.

The run ended as PARTIAL with "reached the run time limit"

Symptom: some keywords are missing and the message says to give the run more time. Likely reason: many keywords × 1,000 products need more than the 300-second default. Action: set the run timeout to 600 seconds, or split the keywords over several runs.

A keyword has a row with status: error

Symptom: one query row with errorCode such as RATE_LIMITED or SOURCE_UNAVAILABLE. Likely reason: Naver did not answer in time or blocked the request. This is not an empty result. Action: run that keyword again later. Error rows are free.

The run status is FAILED

Symptom: the run is red and the message says how many products were saved. Likely reason: Naver stopped answering during the run, so some or all keywords failed. Check: the dataset still has the products saved before the failure, and you pay only for those rows (plus the start fee). RUN_SUMMARY lists which keywords failed. Action: run the failed keywords again later.

brand and maker are empty

Likely reason: for some keywords (for example fashion), Naver shows no brand filter, so there is nothing to read. Action: none needed; the rest of the row is complete.

FAQ

Do I need a Naver account or API key?

No. The Actor reads public search pages. No login, no cookies.

Why is a catalog price sometimes very low?

For catalog cards, Naver shows the lowest offer across all sellers. Sometimes that offer is a rental, a used item or an accessory (we saw rentals at ₩1). The Actor keeps Naver's number as shown; check sellerCount and listingType, or set minPrice.

Is the data the same as on Naver?

Yes, it is the order and prices that Naver's mobile search shows at fetchedAt. Naver personalises ranking and updates prices all the time, so runs at different times can differ. Reviews on catalog cards are Naver's total across sellers.

Can I use the data?

The Actor reads public pages. Naver's terms and robots.txt limit automated access, and you are responsible for how you use the data. If you need an official channel, Naver offers a Shopping Search API with your own developer key and a daily quota. This Actor is independent and not affiliated with Naver.

Support

Use the Issues tab of this Actor. Add the run ID, your keywords and the status or errorCode you saw. Do not send API tokens or private data.