Naver Blog Scraper: Search, Posts, Comments & Likes

Naver Blog Scraper helps you research Korean blog content and the authors behind it. Search posts or bloggers, collect a blog’s post listings and export comments or reacting users for content discovery, creator shortlists and a closer look at audience engagement around selected posts.

Find blog posts around a topic, compare the authors publishing them and review comments or reactions. Build a source-linked research dataset for Korean content, consumer and influencer campaigns.

At a glance	Details
📥 Input	Search fields or links to the selected items; see the examples below
📤 Output	One row per post listing, comment, blog profile or post reactor, depending on the mode
📄 Pagination	Automatic up to maxResults for each input, when more results are available
🔐 Login required	No
⚡ Processing	Multiple inputs per run with automatic retries for temporary errors
💾 Delivery	One complete Apify dataset table; CSV, JSON and Excel export

What the Naver Blog scraper collects 📱

Search posts and bloggers; collect post listings, blog profiles, comments and individual post reactors.

Collection	What you receive
Naver Blog post search scraper	Search Naver Blog posts by keyword and export titles, snippets, authors, publication dates, and thumbnail URLs.
Naver Blog post comments scraper	Collect public Naver Blog post comments with author profiles, text, timestamps, reaction counts, and reply counts.
Naver Blog post likes scraper	Extract users who liked or reacted to Naver Blog posts, including blog URLs, nicknames, profile images, and reaction types.
Naver Blog blog posts scraper	Collect public Naver Blog post listings with titles, URLs, dates, categories, and comment counts.
Naver Blog blog profiles scraper	Extract public Naver Blog profiles with blog names, nicknames, descriptions, IDs, URLs, and profile images.
Naver Blog blogger search scraper	Search Naver Blog authors by keyword and extract blog IDs, names, nicknames, profile images, and public badges.

Data can include:

• Post discovery: Titles, search snippets, source links and thumbnails.
• Blog catalogs: Post listing dates, categories and visible comment counts.
• Bloggers: Blog IDs, names, nicknames, descriptions and profile images.
• Comments: Text, author profiles, timestamps and reply counts.
• Reactions: Reacting users, blog links and available reaction types.
• Profile indicators: Public blog badges and other displayed profile information.

How to scrape Naver Blog 🚀

1. Choose Post Search in What to collect, or select another collection mode.
2. Fill in the search fields, or paste links to the items you want to collect.
3. Set the maximum results and any optional filters.
4. Start the Actor and review the collected rows.
5. Export the dataset or connect it to your application.

Naver Blog post search scraper — input example

{
  "mode": "post_search",
  "searchQueries": [
    "여행"
  ],
  "selection": "sim",
  "maxResults": 10
}

maxResults: 10 means up to 10 results for each input. It does not guarantee that the website has that many matches. You can set the limit as low as 1.

Naver Blog post comments scraper — input example

{
  "mode": "post_comments",
  "postUrls": [
    "https://blog.naver.com/naverofficial/224385311793"
  ],
  "maxResults": 10
}

Naver Blog post likes scraper — input example

{
  "mode": "post_likes",
  "postUrls": [
    "https://blog.naver.com/naverofficial/224385311793"
  ],
  "maxResults": 10
}

Naver Blog blog posts scraper — input example

{
  "mode": "blog_posts",
  "profileUrls": [
    "https://blog.naver.com/naverofficial"
  ],
  "maxResults": 10
}

Naver Blog blog profiles scraper — input example

{
  "mode": "profile",
  "profileUrls": [
    "https://blog.naver.com/naverofficial"
  ],
  "maxResults": 10
}

Naver Blog blogger search scraper — input example

{
  "mode": "blog_search",
  "searchQueries": [
    "여행"
  ],
  "maxResults": 10
}

Naver Blog data fields and complete output 📦

Field group	Included data
Post discovery	Titles, search snippets, source links and thumbnails.
Blog catalogs	Post listing dates, categories and visible comment counts.
Bloggers	Blog IDs, names, nicknames, descriptions and profile images.
Comments	Text, author profiles, timestamps and reply counts.
Reactions	Reacting users, blog links and available reaction types.
Profile indicators	Public blog badges and other displayed profile information.

Each collected item is a separate row. input identifies the submitted value and result_type identifies the selected mode. All returned fields appear in one table; columns that do not apply to a mode can be empty.

A complete JSON result is shown for every collection mode below, in the same order as the input examples. Each example includes every field for its mode; text and lists are not shortened. Values are representative and can change.

Naver Blog post search scraper — complete JSON result

{
  "result_type": "post_search",
  "input": "여행",
  "status": "success",
  "type": "post",
  "id": "224395233705",
  "blog_id": "rsrs0930",
  "author_avatar_url": "https://blogpfthumb-phinf.pstatic.net/MjAyNjA0MjBfMjAw/MDAxNzc2NjY3MDEzNjU2.40PSB17JmcjBQEHsasiz35kyFIf3VvIkehrwXFnGmnQg.sGSM6cuu9ffD15Y6OrxFElVYRtZOFVxR_E3aS_1dde4g.PNG/%25EC%258D%25B8%25EB%2584%25A4%25EC%259D%25BC.png/%25EC%258D%25B8%25EB%2584%25A4%25EC%259D%25BC.png?type=s1",
  "blog_name": "일편이여행로드맵",
  "url": "https://blog.naver.com/rsrs0930/224395233705",
  "search_query": "여행",
  "author_nickname": "일편이",
  "title": "치앙마이 여행 준비 실패 없는 코스 일정 계획",
  "snippet": "치앙마이 여행 준비 실패 없는 코스 일정 계획 태국 치앙마이는 여행 난이도가 높지 않고, 물가와 치안이 안정적이라 자유여행으로도 인기가 높은 도시예요. 작년까지 현지에 머물며 틈틈이 오가면서 찾아 다녀본 경험을 바탕으로 여행에 필요한 준비나 일정 정리 가볼만한곳들을 소개해...",
  "published_at": "2026-08-31T00:18:00Z",
  "is_self_purchased": false,
  "is_market_post": false,
  "thumbnails.url": [
    "https://blogthumb.pstatic.net/MjAyNjA4MzBfNyAg/MDAxNzg4MDgwNjM0ODU2.fUrjlI8pM9e0Pe6UEHbcr6f5x9E1HgF231BoPtqlmIQg.p8qHa8sXFD1jhz3_Wzfnwy-aSluQXca5GlHHF3hils4g.PNG/%BD%E6%B3%D7%C0%CF.png?type=s2",
    "https://blogthumb.pstatic.net/MjAyNjA4MzBfMjIy/MDAxNzg4MDgwNjc2NDQy.gU-9EDAC54mF31R_v2AE0wZxvr_9twQl0GhBekH3QYog.6yCB-6US6GlT_7DiAKEGDtJzANC0kXE8TDgv2cJdyyMg.JPEG/20251101_112354.jpg?type=s2",
    "https://blogthumb.pstatic.net/MjAyNjA4MzBfMjIz/MDAxNzg4MDgxMTY1NTY5.ZL_Pw8GohbiAYT4X5EtH_1-zAR-xRUEkAzlrjncUxwUg.iO6TRb5BdUriEYCiJHC3TgKs2VE1XByDA2v7QwN16acg.JPEG/20250725_092425.jpg?type=s2",
    "https://blogthumb.pstatic.net/MjAyNjA4MzBfMjA1/MDAxNzg4MDgxMTk4NjA4.gymMRs9JQj9bEjvjt556kcT79e26t_oPBORfmvkLi8sg.AfH9b8fQWKKM2CdbsXUkfUlSkmQJ2jUUJaq1N91_huMg.JPEG/20251101_234604.jpg?type=s2"
  ],
  "thumbnails.is_video": [
    false,
    false,
    false,
    false
  ],
  "thumbnails.is_vr": [
    false,
    false,
    false,
    false
  ]
}

Naver Blog post comments scraper — complete JSON result

{
  "result_type": "post_comments",
  "input": "https://blog.naver.com/naverofficial/224385311793",
  "status": "success",
  "type": "comment",
  "id": "902833430528524307",
  "parent_id": "902833430528524307",
  "blog_id": "naverofficial",
  "post_id": "224385311793",
  "post_url": "https://blog.naver.com/naverofficial/224385311793",
  "text": "망디의 먹로그 님의 블로그 운영 방식이 정말 인상적이네요! 오픈런을 통해 신제품을 직접 경험하고, 솔직한 후기를 공유하는 모습이 진정한 크리에이터의 자세인 것 같아요. 프랜차이즈와 편의점 신상 리뷰를 통해 많은 이들에게 유용한 정보를 제공해 주셔서 감사합니다. 앞으로도 응원할게요!",
  "author_id": "dasun_n",
  "author_name": "다순이",
  "author_url": "https://blog.naver.com/dasun_n",
  "author_avatar_url": "https://blogpfthumb-phinf.pstatic.net/MjAyNjA1MDhfMjE5/MDAxNzc4MTc5NzM2MDc1.WNUTbIt0WdXKlfGupEh-54s-f9Ak8miPtdWqzT6Wp2Eg.Gn6SIi-g6qQHQM0TpeW5-iOC1LopRbknuqErp7RXEIcg.PNG/1.png/1.png",
  "created_at": "2026-08-24T04:39:14+0900",
  "updated_at": "2026-08-24T04:39:14+0900",
  "likes_count": 1,
  "replies_count": 0,
  "reply_level": 1,
  "is_deleted": false,
  "is_secret": false,
  "is_visible": true,
  "sticker_id": null,
  "image_urls": []
}

Naver Blog post likes scraper — complete JSON result

{
  "result_type": "post_likes",
  "input": "https://blog.naver.com/naverofficial/224385311793",
  "status": "success",
  "type": "reaction",
  "blog_id": "naverofficial",
  "post_id": "224385311793",
  "post_url": "https://blog.naver.com/naverofficial/224385311793",
  "user_id": "skysea010",
  "user_url": "https://blog.naver.com/skysea010",
  "blog_name": "자몽스러운 아카이브",
  "nickname": "남자몽",
  "avatar_url": "https://blogpfthumb-phinf.pstatic.net/MjAyNjA3MTJfMTYx/MDAxNzgzNzgyODU1MDEw.vTTfIN_WqhKxr2XE0uwModhn4uGFGDhReQ6ztrZTIrQg._sWH1IdpFQKN2ZzF4e0mlHFIGoiWkuAp2PGjCvBqDqwg.JPEG/profileImage.jpg?type=s1",
  "reaction_type": "like",
  "is_deleted_blog": false
}

Naver Blog blog posts scraper — complete JSON result

{
  "result_type": "blog_posts",
  "input": "naverofficial",
  "status": "success",
  "type": "post",
  "id": "224416403552",
  "blog_id": "naverofficial",
  "url": "https://blog.naver.com/naverofficial/224416403552",
  "title": "클립 댓글 캠페인 시작 📢 센스 있는 댓글에 장려금을 드립니다!",
  "published_at": "2026. 9. 18.",
  "category_id": "105",
  "parent_category_id": "105",
  "comments_count": 3,
  "source_code": "0",
  "is_searchable": true
}

Naver Blog blog profiles scraper — complete JSON result

{
  "result_type": "profile",
  "input": "naverofficial",
  "status": "success",
  "type": "blog",
  "blog_id": "naverofficial",
  "nickname": "naverofficial",
  "avatar_url": "https://blogpfthumb-phinf.pstatic.net/MjAyMjAxMTlfMzUg/MDAxNjQyNTUzNzgzNDYw.jdhCkBBFGYJyrnyuHtf1qqqqnLiKKw8aIaWqFvpeixcg.uy2YoZsakoinNOSSDOlxopn2Q-0uYnA1MZdNA09DDTQg.PNG.naver_diary/Profile.png/Profile.png",
  "url": "https://blog.naver.com/naverofficial",
  "blog_no": "42609743",
  "name": "네이버 공식블로그",
  "description": "차곡차곡 쌓인 네이버 소식의 모든 것, 네이버 다이어리입니다."
}

Naver Blog blogger search scraper — complete JSON result

{
  "result_type": "blog_search",
  "input": "여행",
  "status": "success",
  "type": "blog",
  "blog_id": "the_trip",
  "nickname": "여행플러스",
  "avatar_url": "https://blogpfthumb-phinf.pstatic.net/MjAxNzAzMjhfMTU0/MDAxNDkwNjY1NDE2NDE2.eHZn4BXVjxhi_v9wppBfZi5R_QuWT5SVVhuAhFfj6sQg.AsH_GgtZrW3zkh-AP4zS8AS4OpWkpESkE_981je1s8Eg.PNG.the_trip/1.png",
  "url": "https://blog.naver.com/the_trip",
  "search_query": "여행",
  "blog_no": "112743438",
  "name": "네이버 여행+",
  "profile_badge.text": "",
  "profile_badge.icon_url": null,
  "nickname_badge.text": "공식 블로그",
  "nickname_badge.icon_url": "https://ssl.pstatic.net/static/blog/badge/officialblog.png",
  "activity_description": "최근 게시물 12건"
}

Images, tags and other lists stay with their parent result instead of creating extra rows. Invalid or unavailable inputs, inputs with no results, and requests that fail after all retries produce a row with status: failed. At most one failed row is saved per input; it includes error_code and error_message explaining the outcome. A normal end of pagination after collected results does not add a failed row.

Input requirements and collection settings ⚙️

Setting	What to enter
What to collect (mode)	Choose the information to collect.
Maximum results per search or link (maxResults)	Collect up to this many results for each search or link. Minimum: 1.
Search keywords (searchQueries)	Enter one search phrase per line. For Post Search, Search.
Sort by (selection)	Choose the order of matching posts. For Post Search.
Post links (postUrls)	Paste one link per line. Example: https://blog.naver.com/naverofficial/224385311793 For Post Comments, Post Likes.
Profile links (profileUrls)	Paste one link per line. Example: https://blog.naver.com/naverofficial For Posts, Profile.

Collection mode	Fields to use
Post Comments	Post links
Post Likes	Post links
Post Search	Search keywords, Sort by
Posts	Profile links
Profile	Profile links
Search	Search keywords

The result limit applies separately to each search or supplied link. Collection ends earlier when no more matching results are available.

Naver Blog scraping use cases 🎯

Korean content research

Find blog posts discussing a destination, product or consumer topic.

Blogger discovery

Search authors and compare their public profiles before influencer research.

Publishing benchmarks

Collect selected blog listings to compare topics and publishing activity.

Consumer feedback

Review comments beneath selected product or travel posts.

Audience engagement research

Collect the publicly shown profiles that reacted to a selected post.

Pricing and saved-result behavior 💰

See the Actor's Pricing tab for the active pricing model and current rate. Store settings may change, so this README does not claim a fixed cost.

Under dataset-item pricing:

• Each collected item saved in the dataset is one result.
• Images, tags and other values attached to that item do not create additional rows.
• Automatic retry attempts do not create extra dataset rows.
• A saved failed row is also one billable dataset item, including invalid inputs, unavailable items, no results, or exhausted retries. At most one failed row is saved per input, including when some results were already collected.
• maxResults caps all saved rows for each input, including its failed row. Repeated copies of the same input are processed once. More inputs or a higher limit can produce more saved results.

Naver Blog scraper API and integrations 🔌

Replace $ACTOR_ID with the ID shown in the Actor API tab and $APIFY_TOKEN with your token.

curl -X POST "https://api.apify.com/v2/acts/$ACTOR_ID/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"post_search","searchQueries":["여행"],"selection":"sim","maxResults":10}'

Use schedules for recurring collection, webhooks for completion notifications, and Apify integrations for Google Sheets, Make, Zapier, cloud storage, a CRM or your own application.

Reliability, retries, and public-data limits ⚠️

Temporary connection errors, timeouts and access restrictions are retried automatically, up to five attempts. Invalid inputs save a failed row without an HTTP request; confirmed unavailable items save a failed row without unnecessary retries. Exhausted retries also save a failed row. Results already collected remain available if a later request fails, and normal pagination completion adds no error row. Collection also stops after two consecutive fully processed pages add no new results, even if the website provides another cursor. Required detail lookups are completed before checking a page; new results reset the counter, and independent reply branches are checked separately. Failures while initializing the Actor, saving data or scheduling requests stop the run instead of being reported as a failed website result.

Post search and blog listings provide titles and previews; a full article-body mode is not included.

Naver Blog controls which information is publicly available. Removed, private or restricted items may be unavailable, and optional values can be null or empty. A run can still fail if the results cannot be saved.

Frequently asked questions ❓

Does it require an account on Naver Blog?

No. You do not need to provide an account, password or login cookies. Only publicly available information is collected.

How does maxResults work?

It limits the number of saved results separately for every input. The minimum is 1. With maxResults set to 10, each input returns at most 10 available results. A detail lookup normally returns one record per input.

Does post search include the complete article?

It exports the title, search snippet and other exposed listing information, not a full article-body extraction.

Can I collect profiles that liked a post?

Yes. Post Likes exports the users publicly shown as having reacted to the selected post.

Why are some fields empty?

The website may not publish that value, or the field may belong to a different collection mode. Missing values remain null or empty instead of being guessed.

Can I export the results to a spreadsheet?

Yes. Download CSV, Excel or JSON from the Apify dataset. All returned fields are included in the same results table.

Support and responsible use 🛟

For a reproducible issue, share the run ID, selected mode, result limit and a safe public example through the support channel. Never disclose access tokens, passwords or proxy credentials.

Use public Naver Blog information lawfully and responsibly. Follow applicable privacy, copyright, data-protection, contractual and platform requirements when storing, analyzing or redistributing results.