<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Bubbleloglynn</title>
    <description>The latest articles on DEV Community by Bubbleloglynn (@bubbleloglynn).</description>
    <link>https://dev.to/bubbleloglynn</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fthepracticaldev.s3.amazonaws.com%2Fi%2F99mvlsfu5tfj9m7ku25d.png</url>
      <title>DEV Community: Bubbleloglynn</title>
      <link>https://dev.to/bubbleloglynn</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/bubbleloglynn"/>
    <language>en</language>
    <item>
      <title>Analyzing Naver Blog Indexing and Home-Feed Exposure: What I Built and What the Data Showed</title>
      <dc:creator>Bubbleloglynn</dc:creator>
      <pubDate>Fri, 20 Nov 2026 13:39:51 +0000</pubDate>
      <link>https://dev.to/bubbleloglynn/analyzing-naver-blog-indexing-and-home-feed-exposure-what-i-built-and-what-the-data-showed-445g</link>
      <guid>https://dev.to/bubbleloglynn/analyzing-naver-blog-indexing-and-home-feed-exposure-what-i-built-and-what-the-data-showed-445g</guid>
      <description>&lt;p&gt;If you run a blog on Naver — Korea's dominant search portal — you eventually hit a question that has no dashboard behind it:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Is this post actually being shown in search right now?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Naver does not publish a "blog score." Third-party services used to sell one, but those were estimates, and some of them stopped being provided. What is left is the tedious manual check: take the post title, paste it into Naver search, open the blog tab, and look for your own post.&lt;/p&gt;

&lt;p&gt;Do that for 10 posts and it takes 10 minutes. Do it every week for 30 posts and it becomes a chore nobody keeps up with. So I automated it, and in the process I learned that "missing" is a much less obvious word than it looks. This is a write-up of the measurement model behind &lt;a href="https://www.bubbleloglynn.com/" rel="noopener noreferrer"&gt;Bubbleloglynn&lt;/a&gt; (Korean name: &lt;a href="https://www.bubbleloglynn.com/" rel="noopener noreferrer"&gt;버블로그린&lt;/a&gt;) and of the practical problems that came up while building it.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Define the word before measuring it
&lt;/h2&gt;

&lt;p&gt;"Missing" (누락 in Korean) is not a value Naver hands you. It is our label for:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;the state where searching the exact post title does not return that post.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That definition hides three parameters, and each one changes the result:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Which query?&lt;/strong&gt; The full title, a leading fragment, or a keyword combination.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Where?&lt;/strong&gt; Top of the integrated results, the blog tab, or inside the "more" area.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;When?&lt;/strong&gt; Ten minutes after publishing, a day later, or a week later.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Vary any of these and the same post flips between "missing" and "fine." The third one matters most: a post published ten minutes ago may simply not be reflected yet. Counting it as missing inflates the loss rate and produces panic for no reason. So the very first design decision was to give that state its own bucket — pending — instead of folding it into missing.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. What the automated check actually does
&lt;/h2&gt;

&lt;p&gt;The pipeline is the human procedure, written down. The interesting parts are the corrections a human does unconsciously and a script does not.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1) Collect titles first.&lt;/strong&gt; Read the latest posts from the blog's public listing or RSS, and keep a stable ordering. Thirty posts is a good window: a hundred takes too long to check, ten gets buried by two days of new posts.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2) Normalize the title into a searchable form.&lt;/strong&gt; Emoji, quotes, doubled spaces, and decorative brackets perturb search results. A human eyeballs past that; code does not. Keep a normalization rule set — and store the original string next to the normalized one, because later you will have to explain why a particular cell came out the way it did.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3) Query one title at a time, with spacing.&lt;/strong&gt; Firing thirty requests in parallel is fast, but from the other server's point of view the traffic is indistinguishable from a scraper. Sequential processing, a delay between requests, and a cache are the baseline. With those, a personal blog takes under ten seconds and a heavy blog finishes within a minute. Being blocked silently is far worse than being slow; the whole point is that the check can run every day.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4) Reduce the result to a small set of states.&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Your post sits in the top group of results → &lt;strong&gt;strong&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;It appears mid-list → &lt;strong&gt;medium&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;It is only found far down or inside the "more" area → &lt;strong&gt;weak&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;It is nowhere → &lt;strong&gt;missing&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;It was published very recently → &lt;strong&gt;pending&lt;/strong&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Rendered as colored cells, thirty of these read at a glance. Faster than any table of numbers, and it answers the real question: where did the gap appear this week.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5) Keep a human in the loop for the ambiguous ones.&lt;/strong&gt; Automated classification is a filter, not a verdict. Clicking a red cell opens a Naver blog-tab search for that exact title, so a suspect cell can be verified by hand in one click. The goal of automation is not to remove the human; it is to narrow what the human has to look at.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. What is actually observable, once you drop the score
&lt;/h2&gt;

&lt;p&gt;A loss check is the entry point. The rest of the measurement model is built from things that can be observed, not inferred.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Competitor comparison, side by side.&lt;/strong&gt; Add up to three blogs and the view aligns loss, neighbour counts, visitors, views of each blog's public top-10 posts, likes and comments per post, and posting days and hours. Alone, a number tells you nothing ("am I doing badly?"). Next to three peers, it establishes what normal looks like for that topic.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Home-feed exposure.&lt;/strong&gt; Naver's home feed (홈판) follows a different distribution rule from search. Plenty of blogs that index perfectly in search never appear in the feed; blogs that appear often usually also run a separate feed-participation activity. Tracking the last seven days of exposure separately from search keeps the two signals from contaminating each other.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Keyword saturation instead of keyword volume.&lt;/strong&gt; A high-volume keyword is not a good keyword. What matters is how many posts are published against that demand in the same period. Comparing monthly search volume to monthly post volume yields a grade, where the favourable end means "demand exists and supply is thin," and the crowded end means "there are far more posts than searches." Beginners are better off starting from the thin end.&lt;/p&gt;

&lt;p&gt;Adding the composition of the integrated results — whether blogs, influencers, or cafés rank above — shows where a new post can actually fit for a given keyword.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Limits that survived the automation
&lt;/h2&gt;

&lt;p&gt;Worth stating plainly, because they shape how the numbers should be read:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Integrated ranking is not a fixed value.&lt;/strong&gt; It shifts with viewer, time, and location. A reported position describes the screen at the moment of the check, not an absolute rank.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Home-feed figures are relative, not absolute.&lt;/strong&gt; They compare who appears often; they are not Naver's overall impression counts.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The result screen itself changes.&lt;/strong&gt; When Naver restructures its result areas, the same post moves. Which is why a daily series recorded the same way is more useful than any single measurement.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The final judgement stays human.&lt;/strong&gt; Automation narrows the search space.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  5. Stack notes
&lt;/h2&gt;

&lt;p&gt;The service is a web app with a per-request budget rather than a free-for-all: checks are cached, per-user quotas are reset on the Korean day boundary, and the analysis path is limited by design so that a single account cannot hammer Naver. Free usage covers a few checks a day without signing in, more with a Google account; paid plans are being prepared and are not on sale yet. Naver credentials are never requested — only a public blog ID or URL, because everything the tool reads is already public.&lt;/p&gt;

&lt;p&gt;If you maintain a Naver blog and want to try the same measurement, start small: pick ten recent posts, search each title exactly, and mark whether it appears in the blog tab. Three empty cells out of ten is your current state, and it already tells you more than any published score did.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.bubbleloglynn.com/" rel="noopener noreferrer"&gt;버블로그린&lt;/a&gt; is the implementation of this model. I built it because I needed it, and the numbers above are the ones I ended up trusting.&lt;/p&gt;

</description>
      <category>seo</category>
      <category>analytics</category>
      <category>marketing</category>
      <category>saas</category>
    </item>
  </channel>
</rss>
