Naver Blog search scraper avatar

Naver Blog search scraper

Pricing

$1.00 / 1,000 results

Go to Apify Store
Naver Blog search scraper

Naver Blog search scraper

💰 $1.00 per 1000 searches❗ Search Naver Blog by keyword and date range, then collect structured post metadata, previews, engagement counts, and optional full content.

Pricing

$1.00 / 1,000 results

Rating

0.0

(0)

Developer

Data Dino

Data Dino

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

6 days ago

Last modified

Share

Search Naver Blog — South Korea's largest blogging platform — by keyword and date range, and save structured post records to the run dataset. Use it for content discovery, market research, brand and trend monitoring, competitor tracking, and collecting candidate posts for review or analysis.

Features

  • Searches Korean or English keywords across Naver Blog.
  • Restricts results to an inclusive YYYY-MM-DD date range.
  • Returns rich post metadata: title, desktop and mobile URLs, author, blog name, publish date, blog ID, and post number.
  • Supports three content modes — preview (fast, search snippet only), full (complete post text), or none (metadata only).
  • Captures like and comment counts in full-content mode.
  • Supports result and search-page limits for predictable, bounded runs.

Input

FieldTypeDescriptionDefault
keywordstringSearch keyword (Korean or English).맛집
startDatestringInclusive start date in YYYY-MM-DD format.2026-08-01
endDatestringInclusive end date in YYYY-MM-DD format.2026-08-12
maxItemsintegerMaximum posts to return; 0 means all found.20
maxPagesintegerMaximum search pages to request; 0 means all available.0
contentModestringpreview, full, or none.preview

Example input

{
"keyword": "맛집",
"startDate": "2026-08-01",
"endDate": "2026-08-12",
"maxItems": 5,
"maxPages": 1,
"contentMode": "preview"
}

Output

Each dataset item represents one matching post and contains:

FieldTypeDescription
titlestringPost title.
urlstringCanonical Naver Blog post URL.
mobile_urlstringMobile post URL used for detail extraction.
authorstringAuthor's display name.
blog_namestringBlog name.
datestringPublish date (YYYY.MM.DD).
blog_idstringBlog identifier (part of the URL).
log_nointegerNaver's internal post number.
snippetstringSearch-result snippet.
contentstringPreview or full post content, according to contentMode.
likesintegerLike count when available.
commentsintegerComment count when available.

Example dataset item:

{
"title": "청주 소금빵 맛집 우소빵율량점에서 소금빵 포장 후기",
"url": "https://blog.naver.com/soulmate1315/224376807675",
"mobile_url": "https://m.blog.naver.com/PostView.nhn?blogId=soulmate1315&logNo=224376807675",
"author": "먹깨비",
"blog_name": "깨비깨비 먹깨비의 일상❤️",
"date": "2026.08.12",
"blog_id": "soulmate1315",
"log_no": 224376807675,
"snippet": "깨비깨비 먹깨비 입니다 :) ...",
"content": "깨비깨비 먹깨비 입니다 :) ...",
"likes": 0,
"comments": 0
}

Notes and limitations

  • preview mode is the fastest and returns the search snippet without loading post pages; full mode loads each post page individually and takes longer.
  • Like and comment counts are captured in full mode only; preview and none modes return 0 for these fields.
  • Some posts may restrict access or not expose engagement counts; those fields are returned with the available value (0 when not available).
  • Results depend on what Naver's search index returns for the keyword and date range; the actor is not an exhaustive archive of all posts.