Research

Naver Blog Measurement

Read your own Naver blog views, top posts, traffic sources and search words read-only, and pick the next 3 posts. Requires Aside.

Naver Blog Measurement
Works with Claude, GPT and GeminiInstall any one of them in VS Code →ClaudeClaude CodeGPTCodexGeminiAntigravity

How to use

  1. 1

    Download the ZIP

    Get the skill file with the button below. No sign-up.

  2. 2

    Unzip and open

    Unzip it into a folder and open that folder in VS Code.

  3. 3

    Just ask

    Tell your AI agent ‘Run the automation pipeline in this folder’.

When to use it

Try saying

“내 블로그 지난주 통계 정리해줘”Summarize my blog statistics for last week
“검색어 보고 다음에 쓸 글 3개 골라줘”Pick 3 next posts from my search words

What you get

  1. 01A summary of views and traffic sources
  2. 02Top posts and top search words
  3. 03Three posts to write next

Tips

Get it free now

No sign-up, just one ZIP. Edit it freely for personal or commercial use.

Download ZIP (3KB)

Installation

Claude.ai / Desktop app (ZIP upload)

  1. Download the ZIP below.
  2. Upload it under Settings → Capabilities → Skills.
  3. Turn the skill on and start a chat with one of the "Try saying" lines.

Claude Code (copy the folder)

  1. Unzip it. You'll get a folder named after the skill.
  2. Put that folder inside ~/.claude/skills/ (or .claude/skills/ for a single project).
  3. Restart Claude Code.

Menu names may differ slightly depending on your environment. If you can't see the menu, check that skills are enabled on your plan.

Files and preview

Included files

SKILL.md
references/stats_helpers.js
README.txt

Preview of SKILL.md

---
name: naver-blog-measurement
description: Read your own Naver blog stats read-only with Aside (views, top posts, sources, search words) and pick the next 3 posts. Requires Aside and a Naver login. 네이버 블로그 통계 읽기.
---

# Naver Blog Measurement (needs Aside, read-only)

Use this once a week (or 3-7 days after a post goes public) to learn what is working and decide what to write next. It only reads statistics; it changes nothing on the blog.

## Requirements
- **Aside** with a browser profile logged in to the blog owner's Naver account. If the statistics call returns 401, ask the user to log in again; never enter a password.
- Open a tab on `https://blog.naver.com` statistics (`https://blog.stat.naver.com/`) so requests are same-origin.

## Steps
1. Set `globalThis.P = page` (the statistics tab) and run `references/stats_helpers.js` with `(0,eval)(source)`.
2. `const s = await dayStats("YYYY-MM-DD")` gives, for that date: the last 15 days of views (`cv15`), the top 6 posts of the day, the traffic sources, and about 20 search queries. **Use yesterday or earlier**; today is still being counted.
3. `await queryTotals("YYYY-MM-DD", 7, 15)` adds up search queries over a week and returns the top ones.
4. Look at four things:
   - **Trend**: are the 15-day views going up, flat or down? Compare with the number of posts that went public.
   - **Sources**: how much comes from search versus the Naver home feed versus other blogs. Home-feed visits come and go; do not plan around them.
   - **Top posts**: which 3 posts bring the most views, and what they have in common (a question title? a series?).
   - **Search words**: which queries bring visitors. Phrases that ask a question ("why", "when", "difference") are the ones to split further.
5. Write the next step: pick 3 queries that already bring visitors and have no dedicated post; use `naver-blog-topic-picker` to expand them and `naver-ai-briefing-writing` to write them. Add a link from the new post to the post that already ranks for the parent phrase.
6. Record the numbers in a small table (date, views, top 3 posts, top 5 queries) so next week can be compared.

## Honest limits
- Search-query statistics are for the whole blog, not per post; match a query to a post by its title.
- Small counts (1-3 visits) are noise. One phrase can dominate a small blog, so do not over-read a single week.
- The statistics API is not an official public API and may change; if a field disappears, say so instead of guessing.
- Never share the raw statistics output publicly: it contains your blog address.

## Output
A one-page weekly note: views trend, source split, top posts, top queries, the 3 posts to write next, and what to try differently.

---
만든이: sphereai.work (https://sphereai.work)

You may also like

This skill is a set of instructions Claude loads on its own. You are responsible for how you use the results. The instructions inside the ZIP are written in Korean. Terms of Use