Naver Blog Profile Scraper (네이버 블로그)

Scrape any Naver Blog creator's profile and their complete post archive in one run. Give the Actor a blogger ID or blog URL and it returns the profile (blog name, nickname, subscriber count, total and daily visitor counts, official / power-blog badges, profile image) plus the full list of their posts crawled from the post directory (카테고리) — every post's title, URL, publish date, category, comment count and like (공감) count. Built for influencer and creator analysis, competitor research, and content auditing.

Because it runs on the Apify platform, you get scheduled runs, a REST API, webhooks and integrations (Google Sheets, Make, Zapier, Slack…), automatic proxy rotation through Korean IPs, and monitoring — no servers to manage.

Why use Naver Blog Profile Scraper?

• Influencer vetting — quantify a blogger's reach (subscribers, visitor totals) and posting cadence before a partnership.
• Competitor & market research — see exactly what topics a brand's blog publishes, how often, and how much engagement each post gets.
• Content auditing — export a creator's entire back catalogue with categories and dates for a content inventory.
• Trend tracking — schedule the Actor to re-run and watch subscriber growth and new posts over time.
• Bulk analysis — feed a list of many bloggers and get one tidy record per creator.

How to use Naver Blog Profile Scraper

1. Enter one or more bloggers — a bare ID (naverofficial), a @handle, or any blog URL (https://blog.naver.com/naverofficial, https://m.blog.naver.com/naverofficial, or even a link to a single post).
2. (Optional) Set Max posts per blog to cap how many posts are collected — defaults to 100 for a quick, cheap first run; set 0 for the entire archive.
3. (Optional) Turn Scrape posts off if you only want profiles + the category tree (fast and cheap).
4. Click Start. When the run finishes, open the Output tab and download the data as JSON, CSV, Excel, or HTML — or pull it from the API.

Input

Configure the run in the Input tab (or via JSON / API). Key fields:

Field	Description	Default
blogs	Blogger IDs or blog URLs, one per line. Required.	—
scrapePosts	Crawl the full post list from the post directory.	true
maxPosts	Cap posts collected per blog (newest first). 0 = entire archive.	100
includePostContent	Fetch each post's full body text (one extra request per post — slower).	false
outputMode	postItems = one item per post (+ a profile item); blogItem = one item per blog, posts nested.	postItems
categoryNo	Restrict posts to a single category by its Naver categoryNo. 0 = all posts.	0
includeCategories	Attach the blogger's category tree with per-category post counts.	true
language	Accept-Language hint. Korean is strongly recommended.	ko
maxConcurrency	Blogs processed in parallel.	3
proxyConfiguration	Proxy for every request. Korean residential IPs recommended.	Apify Proxy, RESIDENTIAL, KR

Example input:

{
    "blogs": ["naverofficial", "https://blog.naver.com/naver_diary"],
    "scrapePosts": true,
    "maxPosts": 100,
    "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"], "apifyProxyCountry": "KR" }
}

Output

Results are written to the dataset in one of two shapes, chosen by outputMode:

• postItems (default) — one dataset item per post ("type": "post", each stamped with its author's blogId / blogName / nickName), plus one profile item per blog ("type": "profile"). Best for spreadsheets and per-post analysis.
• blogItem — one item per blog ("type": "blog") with all posts nested under a posts array. Best when you want the profile and its whole archive as a single object.

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

Example profile item (postItems mode):

{
    "type": "profile",
    "blogId": "naverofficial",
    "blogUrl": "https://blog.naver.com/naverofficial",
    "blogName": "네이버 공식블로그",
    "nickName": "naverofficial",
    "officialBlog": true,
    "subscriberCount": 96330,
    "totalVisitorCount": 156848815,
    "postCount": 2595,
    "categoryCount": 13,
    "categories": [{ "categoryNo": 105, "categoryName": "서비스 인사이드", "postCnt": 1994, "isChild": false }]
}

Example post item (postItems mode; content present only when includePostContent is on):

{
    "type": "post",
    "blogId": "naverofficial",
    "blogName": "네이버 공식블로그",
    "logNo": "224342736839",
    "url": "https://blog.naver.com/naverofficial/224342736839",
    "title": "네이버 프라이버시 챌린지에 참여하세요!",
    "briefContents": "AI 시대의 개인정보 보호를 함께 고민할 …",
    "content": "AI 시대의 개인정보 보호를 함께 고민할 대학(원)생 여러분을 초대합니다. …",
    "contentLength": 516,
    "categoryName": "이벤트/캠페인.zip",
    "addedAt": "2026-07-13T00:30:00.000Z",
    "commentCount": 2,
    "sympathyCount": 61,
    "thumbnailUrl": "https://mblogthumb-phinf.pstatic.net/…/03_.png"
}

Data fields

Profile

Field	Description
blogId	Canonical Naver blog ID (resolved from aliases).
blogUrl / mobileBlogUrl	Desktop and mobile blog URLs.
blogName	The blog's title.
nickName / displayNickName	Author nickname(s).
officialBlog / powerBlog	Naver status badges.
subscriberCount	Number of neighbours / subscribers (이웃).
totalVisitorCount / dayVisitorCount	Lifetime and today's visitor counts.
postCount / momentCount	Total posts and moments (모먼트).
profileImageUrl / mobileTitleImageUrl	Profile and cover images.
categories	Category tree with per-category postCnt.

Each post

Field	Description
logNo	Naver's post ID.
url / mobileUrl	Links to the post.
title	Post title.
briefContents	Short text preview.
content / contentLength	Full body text + length (opt-in).
categoryNo / categoryName	The post's category.
addedAt / addDate	Publish time (ISO 8601 / epoch ms).
commentCount	Number of comments.
sympathyCount	Number of likes (공감).
shareCount	Number of shares.
thumbnailUrl / thumbnails	Post thumbnail image(s).
hasVideo	Whether the post has a video thumbnail.

How much does it cost to scrape Naver blogs?

This Actor uses pay-per-event pricing: a small charge per blog profile resolved, plus a charge per post scraped. Cost therefore scales with output — a profile-only run (scrapePosts off) is cheapest, and you can cap spend on prolific bloggers with Max posts per blog. See the Pricing tab for current per-event rates; the Apify free tier is enough to try it out.

Tips & advanced options

• Profile-only, fast & cheap: set scrapePosts to false to fetch just the profile and category tree.
• Cap large archives: some blogs have thousands of posts — set maxPosts to keep runs fast and predictable.
• Focus a topic: pass a categoryNo (find the values in each record's categories list) to scrape only one category.
• Use Korean residential proxies: Naver rate-limits datacenter and non-Korean IPs. The default (Apify Proxy, RESIDENTIAL, country KR) is strongly recommended; the Actor also self-throttles and retries on rate limits.

FAQ, disclaimers & support

Is scraping Naver Blog legal? This Actor collects only publicly available information that anyone can view without logging in. You are responsible for how you use the data, including compliance with Naver's Terms of Service and applicable laws (such as GDPR / PIPA) when handling any personal data. Do not use it to collect private or sensitive information.

Why is a blog missing from the output? Blogs that don't exist, are private, or have been blocked return a not-found response and are skipped with a warning — the rest of the run continues.

Does it fetch the full post body / images / comments? Turn on Include full post content to get each post's full body text (content). Images are returned as thumbnail URLs, and comment threads are not fetched (only the comment count). Full-content mode makes one extra request per post, so it's slower — pair it with Max posts per blog. Let us know via the Issues tab if you need comment threads or inline media.

Found a bug or need a custom solution? Open a ticket on the Issues tab — feedback and feature requests are welcome.