After Naver cut off its data: Korea's top blog-index site switches to reading bloggers' own logged-in data
What it is It uses each blogger's own Naver login to pull the statistics Naver shows only to the blogger, displays them on the 블덱스 website, and each month uses Gemini to generate an AI settlement report and a plan for next month's posts.
Why it took off Naver cut off external tools' access to the data used to estimate blog ratings at the end of 2025, forcing 블덱스, Korea's top blog-index site, to shut down its service and redesign; 3.0 moved to the route of reading the blogger's own backend data. The extension's 4,000 users are older users of the parent site's self-reported 1.9M base, pulled over by the "내 블로그 분석" (my blog analysis) feature.
CHow you could follow suit Don't copy it as-is in Korea. Do the same thing on a platform where creator dashboards have data but the platform gives no interpretation (RedNote/Xiaohongshu, Douyin Creator Center, Tistory, etc.): website as the main interface, extension only uses the user's logged-in session to pull stats, sell a monthly AI report, and move in to take users when the platform shuts APIs or the old tools go down.
4,000 users
"Blogdex: Naver Blog Analysis" is a Korean-only Chrome extension, listed for 5 months with 4,000 users and not a single rating. It isn't a product that grew on its own: almost everyone who installed it is an old user of the parent site Blogdex (블덱스), who was told to install it to use a site feature. What's worth looking at is the move behind it: when the platform shut off public data, how does a tool that lived on that data find a path the platform can't easily block and keep charging subscriptions?
A shutdown notice, and a year-end recommendation post
On 2025 Dec 4, Blogdex announced it was stopping blog index lookups, and paid users were refunded by month end. Korean marketing outlet Mobiinside later reconstructed the timeline, calling it at the time "the top external blog index tool." The direct cause: a month earlier, on Nov 5, Naver's RSS service dropped HTTP/1.0 support, and the old channel external tools depended on broke. Several other index sites shut down in the same period.
On Dec 31, a Naver blogger who had just started writing posted a year-end list of the sites they now use to check rankings, mentioning in passing: "블덱스는 네이버 API 연동이 중단되면서 기존 서비스를 제공할 수 없게 되어" (Blogdex's Naver API integration was discontinued, so it could no longer offer its existing service). Everyone moved to 판다랭크, 블로그차트, and 웨어이즈포스트.
Half a year later, in 2026 Jun 13, blogdex.space posted an "extension privacy policy"; on Jun 15, the extension was listed. Around July, Blogdex 3.0 went live, and one blogger wrote: "Recently, starting from July, Blogdex developed version 3.0 and began offering new services."
What it is
The extension's store description opens with: "내 네이버 블로그, 감(感)이 아니라 데이터로 운영하세요。" (Run your Naver blog on data, not gut feeling.)
What it does is narrow: it reads your browser's Naver login cookie, uses your identity to call the stats APIs of Naver's creator dashboard (Creator Advisor), pulls page views, unique visitors, age/gender/device breakdown, search terms that brought traffic, top posts, and average time on page, and uploads them to the "내 블로그 분석" page on the Blogdex website. On the 1th of each month, it passes the stats summary to Google Gemini to generate an AI monthly report: why the last month rose or fell, what to write next month, plus a 4-week posting plan.
The extension is only 38 KiB; the entire interface lives on the website. Its privacy policy is carefully written, and a few lines are worth recording verbatim: single purpose; before collecting, it checks whether the currently logged-in person is the blog's owner, and collects nothing if not; the cookie is used only to request naver.com and "is never sent to any external party, including Blogdex servers"; only statistical figures are uploaded. Last line: "This extension is not an official Naver product and has no partnership with Naver."
Why this path
Naver closed the channel external tools used to estimate bloggers' levels. Mobiinside's post includes a fact check: Naver didn't abolish the "index"; it closed the route outsiders used to estimate it. The grade labels people often cite, like "준최적, 최적," were never official Naver concepts; they were labels external tools made up themselves.
With public data shut off, external tools have only two routes: one is to scrape the public pages and estimate (Bludex's 3.0 "self-computed index" takes this route, and the free version of the same blog can only refresh once every 48 hours); the other is to get the blogger's authorization and read the backend that Naver already shows to the blogger. The data from the second route is real and outsiders can't scrape it, and platforms can hardly block it on the grounds of "protecting the API": it's users looking at their own data. The plugin takes the second route.
Where the 4,000 users came from
| Date | users | Rating |
|---|---|---|
| 2026-06-15 | Launched | |
| 2026-11-01 | 4,000 | 0 |
| 2026-11-06 | 4,000 | 0 |
Chrome Web Store, 11-01 to 11-06: no movement for a week.
Almost all of it was imported from the parent site. Blogdex's login page reads "지금까지 190만명의 블로거들이 사용중이에요" (1.9M bloggers have used it so far; self-reported cumulative figure, unverified). From 2023 on, hundreds of "blog index lookup site recommendation" posts on Naver Blog and Tistory list it. The usage steps in the store description: install the extension → log into blogdex.space → click "분석하기" in the "내 블로그" menu. Without the extension, this page doesn't work.
Almost nothing about it outside the platform: no articles dedicated to this extension; searching "블덱스" or "blogdex" on X over the past ~90 days returned 0 posts; the store shows 0 ratings; no sign of paid acquisition. 4,000 out of 1.9M, roughly 0.2% penetration: even within the parent site, this feature hasn't taken off.
Where the money comes from
The extension charges nothing; the money is on the parent site:
- Premium monthly subscription ₩47,000 (about $33, estimated), auto-renewing, blogdex.space/limits, 11-06. 2024 year(s) ago, bloggers wrote about a "30-day pass" at the same price, now converted to a subscription. The paid hooks the extension brings are in the same table: the free AI monthly report only shows the latest issue, while paid unlocks "all monthly reports + historical archive"; post ranking tracking is free for 3 posts, paid for 30 posts.
- Blogdex 체험단 (Blogdex Review) (blogdexreview.space): advertisers recruit trial-group bloggers here. Choose bloggers rated "index 8 and above"; each costs 2 credits (₩20k); the premium package is 20 credits, one-time. The grade the parent site calculates turns directly into a price here.
- Blogdex Writer: AI writing, with a matching posting extension listed in May; 1,000 users; marked as having in-app purchases (Chrome Web Store).
So this extension's role is: lock bloggers' most private, most real data inside a Blogdex account, then use a monthly report to build a habit of returning each month, holding up subscription and trial-group revenue on both sides. How much revenue that brings hasn't been disclosed.
Who it's competing with
| Name | Form | Scale | How it differs |
|---|---|---|---|
| Naver Creator Advisor | Official dashboard | Free for all Naver bloggers | It's the data source. What Blogdex adds is AI interpretation, next-month plans, and placing them in the same interface as index and keyword rankings |
| 판다랭크 + 판다랭크 크리에이터 도구 | Web + browser extension | Extension 30k users / 23 rating | The main channel that picked up users when Blogdex shut down; the extension does writing assistance, the website sends a weekly blog report; whether it reads the user's own dashboard is unverified |
| 리뷰언즈 엔서포터 | Add-ons | 100k users | In-editor keyword, word count, and SEO tools; doesn't read the dashboard |
| 늑대플(블라이) | Extension + web | 5,000 users / 39 reviews | Full writing suite; the website also estimates index; doesn't read the dashboard |
| 로워드 어드바이저 | Add-ons | 4,000 users, with in-app purchases | Keyword analysis + AI automatic posting |
| Blog Chart, Where Is Post, etc. | Web | Not verified | Estimates grades and rankings from public data only |
User counts from the Chrome Web Store, 11-06.
The specific method of "using the user's own logged-in session to pull Creator Advisor data into a third-party platform, then adding an AI monthly report" wasn't seen in a second Chrome Web Store listing. But it hasn't grown outside the platform as a result: the differentiation here is defensive, giving Blogdex something compliant and billable to keep after the index was blocked, not a growth engine.
If it were you
C: You can learn from it, but copying it isn't worth it. This extension's 4,000 users came from 1.9M legacy users exported over; followers can't get them. In this Korean market, a rival like 판다랭크 with 30k extension users could copy it within weeks. The move worth learning: when the platform shuts public data, switch to user-authorized reading of the creator's own dashboard, then collect subscriptions with an AI monthly report.
Who it suits: tools that already have a base of creator users (ranking sites, topic-idea sites, MCN dashboards, managed-service SaaS) and are being squeezed by platform data restrictions; people who know a single platform's creator ecosystem well.
Who it doesn't suit: people starting from zero who hope to get users through store search. Nobody searches for this kind of extension; it's just a data connector for your website and has no entry point without a parent site. Also not for people who can't tolerate platform-terms risk: if Naver tightens internal dashboard APIs someday, or deems this usage a violation, the whole thing stops.
How to build it: Pick a creator-backend platform where the analytics are useful but the official tools only show numbers, not interpretation. Think Xiaohongshu Creator Center and Pugongying, Douyin Creator Center, Bilibili, Tistory, Coupang Partners. Make the website the main interface and the extension do just one thing: pull stats using the user's own login session. Write the privacy page the way 블덱스 does: single purpose, verify the user is the account owner first, cookies never leave the device, only the stats get uploaded, and state clearly that it's unofficial. The selling point is the AI monthly report: on day 1 of each month, send "last month's settlement + what to create next month + a 4-week plan." The latest issue is free, the history archive is paid. Where you go one step beyond 블덱스: use the real data for matchmaking. Like 블덱스체험단, charge advertisers based on each creator's actual performance, not on estimated grades.
How to get users: build the tool site first, then the extension. Writing on the target platform about "how to read your dashboard data" or "why traffic dropped this month" is itself SEO inside the platform; enter in the weeks when the platform changes its rules and old tools shut down, catching churned users. That's how 판다랭크 took Blogdex's users.
When to move: the next time the target platform shuts a data API. Every tool shutdown is a window in which a new tool can pick up a batch of ready-made users.
Signs you've read it wrong: ① the extension is still stuck around 4,000 half a year later, meaning even the parent site's own users don't care much about their own dashboard data, and the AI monthly report can't hold up a subscription; ② Naver blocks Creator Advisor's internal APIs, or the Chrome Web Store delists extensions that read login cookies like this, and the path is closed; ③ rivals like 판다랭크 ship the same feature and quickly pass it on user count, showing that the game is just who has more users and the method has no barrier.
Data and sources
- Store page: chromewebstore.google.com/detail/bibmcbmicbdfcicpajfgkiejlcpmdpij (11-06 reads, v1.1.2,10-07 update, Korean only); user counts and ratings from 11-01 to 11-06 come from the Chrome Web Store daily scrape; competitor user counts likewise.
- Extension privacy policy: blogdex.space/extension-privacy (effective 2026-06-13); pricing and quotas: blogdex.space/limits (11-06); 1.9M: blogdex.space/login.
- Shutdown timeline: Mobiinside / brunch, 2026-05-18 (brunch.co.kr/@mobiinside/7384).
- Blogger posts: m.blog.naver.com/chanjoopark1004/224128585317 (2025-12-31); m.blog.naver.com/tmdtjq80/224364815643 (3.0 redesign); blog.naver.com/isdn2721/223517181824 (2024 year 30-day pass).
- Trial group pricing: blogdexreview.space/pricing.
- Discussion on X: keyword search over the past ~90 days, 0 posts.
Research notes: competitor table, acquisition evidence, full research report
- Competitors
Name Where Launched Scale How it differs from this one Naver Creator Advisor Big-company features Years Free for all Naver bloggers It's the data source; what Blogdex adds is AI interpretation, next-month plans, and placing them alongside index / keyword rankings 판다랭크 + 판다랭크 크리에이터 도구 Web + Chrome Extension 2025-08-19 Extension 30,000 users / 23 rating The main channel that picked up churned users after Blogdex shut down; the extension adds writing assistance plus weekly reports; whether it reads the user's own dashboard is unverified 리뷰언즈 엔서포터 Chrome 2021-03 100,000 users In-editor keyword / SEO / word count tools; doesn't read the user's own stats 늑대플 / 블라이 Chrome + web 2026-01-16 5,000 users / 39 reviews Full writing suite; estimates index on the website, doesn't read the dashboard 로워드 어드바이저 Chrome 2026-04-28 4,000 users / 11 rating, with in-app purchases Keyword analysis + AI automatic posting NAEO Chrome 2026-04-27 899 users Single-post SEO analysis 블로그차트 / 웨어이즈포스트 / 블스피 Web Mixed Not verified Estimates index and rankings from public data only - Where users come from
- Verified Parent-site in-product prompts / legacy user migration: "내 블로그 분석" on blogdex.space requires the extension to work; store rating 0; the parent site self-reports 1.9M cumulative users
- Verified Platform events: 2025-11-05 Naver RSS dropped HTTP/1.0,2025-12-04; Blogdex stopped index lookups and refunded users (brunch/Mobiinside 2026-05-18); 2026-07 before/after 3.0 redesign
- Verified Naver Blog / Tistory word of mouth and SEO (parent-site level): a large number of "blog index check site" recommendation posts; no dedicated articles about the extension itself
- Confirmed Cross-promotion from the main site's App: a homepage popup pushes the App at space.blogdex.app, 500+ downloads
- Inferred X / media / paid acquisition: x-radar shows 0 posts, no rating signal, user count flat
Blogdex — Naver Blog analytics (Chrome extension, bibmcbmicbdfcicpajfgkiejlcpmdpij)
In one line: this isn't an independently grown extension. It's a "data connector" that Korea's leading Naver blog index site, Blogdex (블덱스), built during its 3.0 revamp after Naver cut off external data access in 2025-12. 4,000 Its users are almost all long-time users of the main site, pulled over by in-site prompts. What it really shows is a way around platform lockdowns: when a platform stops offering public data, switch to the blogger's own logged-in session and pull the stats only the blogger can see, then sell a monthly AI report on top to collect subscription fees.
1. Basic data
| items | value | Source |
|---|---|---|
| First published | 2026-06-15 | Chrome Web Store / chromestore library |
| Recent updates | 2026-10-07, v1.1.2,38 KiB, Korean only | Store listing page (read 2026-11-06) |
| Users | Daily from 4,000,2026-11-01 to 11-07 was 4,000, unchanged | chromestore.item_snap |
| Rating | 0 reviews | Same as above |
| Developer | Not a trader. Contact email [email protected]. The sister developer account "블덱스라이터 발행" also lists the developer name as 블덱스, with the email domain jgluna.com | chromestore.item |
| Parent company | (주)더씨커 (The Seeker), CEO 연준, Chuncheon, Gangwon-do. Site footer reads "©2023-2026 더씨커 & 제이지루나" | Footer of blogdex.space/ |
| Paid | The extension is free. Main-site Premium is ₩47,000/month (the earlier single-purchase pass sold through Smart Store has been discontinued). The free AI report tier shows only the latest issue; the paid tier unlocks the full history. | blogdex.space/limits |
What the extension does (store description + blogdex.space/extension-privacy):
- It reads the Naver login cookies (NID_AUT / NID_SES) and, with the blogger's own permissions, calls Naver Creator Advisor's stats endpoints to get page views, unique visitors, age/gender/device breakdown, search terms and traffic channels, top posts, and average time on page.
- Before collecting, it checks that the logged-in account owns the blog and skips otherwise. Cookies are used only for requests to naver.com and are not sent to Blogdex servers.
- Stats are sent to Blogdex servers and shown on the site's "내 블로그 분석" page. On day 1 each month, a stats summary goes to Google Gemini, which generates the AI report: "last month's review + next month's strategy (what to write, a 4-week posting plan)".
2. Why it took off
2.1 Timing: a platform event forced the pivot
- 2025-11-05: Naver's RSS service stopped supporting HTTP/1.0, breaking the legacy channel external tools relied on. 2025-12-04: Blogdex, then the top external blog index tool, announced it would stop index lookups and refund users before year-end (Mobiinside / brunch 2026-05-18, brunch.co.kr/@mobiinside/7384). Around the same time, other index sites like 리뷰 (리드뷰) and 블연플 also shut down (https://m.blog.naver.com/kim-hyunhak/224101523081; a YouTube video titled "네이버 블로그 지수 없어지나 블덱스 블연플 사용 중지 사태").
- After the shutdown, bloggers said "Blogdex can no longer provide its existing service because the Naver API integration was discontinued" and moved to 판다랭크, 블로그차트, and 웨어이즈포스트 (https://m.blog.naver.com/chanjoopark1004/224128585317, 2025-12-31).
- 2026 around July: Blogdex relaunched as 3.0, switching to its own in-house index and adding "own blog analytics" (https://m.blog.naver.com/tmdtjq80/224364815643 says "since the 7 month, Blogdex 3.0 version has been developed"; a mepix.ai tutorial uses the 2026-07-16 interface, 3.0). The extension was released a month earlier (2026-06-15), and exists to feed data into the "내 블로그 분석" page on 3.0.
- The logic: once Naver turned off public data, external tools had two options. They could scrape public pages and estimate (Blogdex's in-house index, 3.0), or they could use the blogger's authorization to read their own backend data. Backend data (Creator Advisor) is shown to the blogger, so it's real. Outsiders can't scrape it, and Naver would find it hard to block it under the banner of "protecting the API." This extension takes the second route.
Where 2.2 users come from: mostly migrated from the parent site's existing users
- The Blogdex login page says "190 bloggers are using it so far" (https://blogdex.space/login). This is a self-reported cumulative figure and unverified. Since 2023, the main site has been the default "blog index lookup" tool in Korea's blogger community. Hundreds of "블로그 지수 확인 사이트" recommendation posts on Naver Blog and Tistory mention it (search results include johblack.tistory.com/613, m.blog.naver.com/sonovember/223135053421, blog.naver.com/wl2134/223381854081, and others).
- The in-site "내 블로그" page (https://blogdex.space/my-blog) requires login, and clicking "분석하기" requires the extension to be installed first. The usage steps in the store description are: "확장 설치 → blogdex.space 로그인 → '내 블로그' 메뉴에서 [분석하기]" (Install extension → log in at blogdex.space → click [분석하기] in the "내 블로그" menu).
- Evidence chain: the store has 0 ratings and 4,000 users, and hasn't been updated in 7 days. No articles specifically about this extension turn up online, only mirror sites like extension.vn. An X search (x-radar, "blogdex" / "블덱스", 90 days) returned 0. This suggests most installers come from inside the main site, not from store search or content. Against the self-reported 1.9M users on the main site, 4,000 is only about 0.2%, meaning penetration of this feature is still low.
- The main site's own traffic sources: word-of-mouth and SEO within the Naver blog ecosystem (bloggers write "index lookup site recommendation" posts, which are themselves Naver content), "blog index site roundup" videos on Instagram and YouTube, plus a TWA Android app (space.blogdex.twa) and a new native app (space.blogdex.app, developer SAIPAY.IO, 500+ downloads, Google Play 2026-11-06).
Why 2.3 users are willing to pay
- The main site has been charging for Premium for a while. Back in 2024, a blogger wrote about a "30-day pass for 47,000 won" (https://blog.naver.com/isdn2721/223517181824). The same price now sits on a monthly auto-renewing subscription. The extension adds the AI report (paid users can see the full history) and post-ranking tracking (3 free posts / 30 paid), value added to keep paying users, 3.0.
- Only two other parts of the ecosystem actually make money:
- 블덱스체험단 (blogdexreview.space): advertisers run free review campaigns. Choosing "top bloggers with index 8 and above" costs 2 credits per blogger (₩20,000); the premium package is 20 credits (₩200,000) per campaign (https://blogdexreview.space/pricing). The main site's blogger index now directly sets the price.
- 블덱스라이터 (write.blogdex.space): AI writing tool with a companion publishing extension, 「블덱스라이터 발행」, listed in 2026-05-14 with 1,000 users and 10 ratings. The store lists in-app purchases (chromestore library).
- There is also biz.blogdex.space, aimed at merchants.
- So the extension doesn't charge directly. Its role is to lock users' most private, most real data into the Blogdex account, then pair it with the AI report to build a habit of coming back each month. That supports two revenue lines: subscriptions and the review campaigns.
3. Competitors
| Product | Where | Launched | Scale | How it differs from the Blogdex extension |
|---|---|---|---|---|
| Naver Creator Advisor (official) | Big-company features | Years | Free for all Naver bloggers | It's the data source. Blogdex adds AI interpretation and next-month writing plans, all in the same interface as the index and keyword rankings |
| 판다랭크 (pandarank.net) + the "판다랭크 크리에이터 도구" extension | Web + Chrome | Site is older; extension 2025-08-19 | Extension 30,000 users / 23 ratings (chromestore) | The main player that caught Blogdex's churned users after the index shutdown. The extension is for writing (keywords, titles), and it sends a weekly "블로그 리포트" (mentioned in blogger reviews, e.g. m.blog.naver.com/ellyfly/224234424269, which discloses sponsorship). Whether it reads backend stats is unverified |
| 리뷰언즈 엔서포터 | Chrome | 2021-03 | 100,000 users | In-editor keyword / character count / SEO aids; does not read backend stats |
| 늑대플(blai.co.kr 블라이) | Chrome + web | 2026-01-16 | 5,000 users / 39 reviews | Writing toolkit (character count, banned words, morpheme analysis, AI writing). The site also offers a "blog index" but does not read the blogger's stats |
| 로워드 어드바이저 | Chrome | 2026-04-28 | 4,000 / 11 ratings, has in-app purchases | Keyword analysis + AI auto-posting; does not touch the blogger's own stats |
| 황금비서 | Chrome | 2025-01 | 10,000 | Keyword lookup + shortcuts |
| NAEO - 네이버 블로그 분석 도구 | Chrome | 2026-04-27 | 899 (11-01 is 810) | Per-post SEO analysis |
| 블로그차트, 웨어이즈포스트, 블스피 (blrank.co.kr), 블로그지수닷컴 | Web | Mixed | Not verified | External index / ranking estimates, public data only |
| 모아 블로그 지수 | Chrome | 2026-11-02 | 1 | Recently launched real-time writing diagnostics, very small |
Conclusion: the specific approach of "using the blogger's session to pull Creator Advisor data into a third-party platform, then adding an AI monthly report" has not been seen in a second Chrome Store listing. A search of the chromestore library for Korean Naver blog and Creator Advisor extensions turned up only Blogdex describing itself this way. The closest is 판다랭크's weekly report.
4. Growth tactics broken down
| Channel | Evidence | Confirmed? |
|---|---|---|
| In-site prompts / migration of old users from the main site | "내 블로그 분석" requires the extension; store 0 ratings; main site self-reports 1.9M cumulative users | Confirmed |
| Platform event (Naver cut off external index channel) | Brunch timeline (2025-11-05 RSS, 2025-12-04 Blogdex shutdown); multiple blogger posts | Confirmed (as the reason for the shift) |
| Naver Blog / Tistory word-of-mouth and SEO (at the main-site level) | Many "index lookup site recommendation" posts | Confirmed (main site); no dedicated articles found for the extension itself |
| Cross-promotion from the main site's App | Homepage popup pushes the App, App 500+ downloads | Confirmed, contributes little to the extension |
| X / media | x-radar 0 posts; media only wrote about 블덱스 shutting down, not this extension | Not found |
| paid acquisition / fake reviews | 0 rating, steady user count, no sign of paid acquisition | Not found |
5. Differentiation
- Different data source: competitors either use public data (index estimates, keyword rankings) or are writing assistants; the 블덱스 extension pulls real analytics that only the blogger can see. Naver can't block this the way it blocked public APIs, and that's the technical reason it could keep running through 2026.
- AI monthly report: turns the scattered numbers in Creator Advisor into "why traffic went up or down last month, what to write next month, 4-week posting plan," released monthly with paid access to history, a bit like a subscription magazine.
- Bundled ecosystem: one account covers index, keywords, missing-post detection, AI writing, posting extension, and an experience team. Once a blogger's own data is connected, switching costs are high.
- Is this why it took off? Only half. 4,000 users came from the parent site's longtime users and in-site prompts. The differentiation itself didn't drive outside growth (no reviews, no organic word of mouth). Its role was to give 블덱스 a compliant, real, monetizable anchor after the index business was blocked. That's defense, not a growth engine.
6. Visibility
- The extension itself: almost unknown outside the circle, no media coverage, nothing on X, no store reviews.
- Parent site: well known in Korean blogger circles; when it shut down it got discussed on Mobiinside / brunch, YouTube, and Instagram. Revenue is not public (no TrustMRR, no founder posting numbers).
- So the call is "spreading in a small circle": the parent site is known to everyone in Korean blogger circles, but the new extension angle is unknown outside it.
- Copycats: no extension found that copies the "own session + AI monthly report" approach.
7. Takeaways
- When platforms block public data, switch to "user authorizes reading their own data": use a browser extension to reuse the user's logged-in session and read the back-end dashboards platforms show creators. This maps to creator back-ends on every platform: Xiaohongshu Pugongying / Creator Center, Douyin Creator Center, Naver, Tistory, Coupang Partners. Copy its privacy page for compliant wording: single purpose, verify account ownership first, cookies stay local, only aggregated stats get uploaded.
- Use an AI monthly report for subscription retention: publish a "settlement + next month's plan" on day 1 each month; the free tier gets only the latest issue, paid unlocks the history archive, building a habit of coming back monthly.
- Full suite in a small-language, single-platform creator ecosystem: tools (index / analytics) bring in bloggers, the experience team sells credits to advertisers by blogger quality, so both sides pay; creator data itself is the pricing basis for matching deals.
- Extension only handles data access, the main interface lives elsewhere: 38 KiB, all features on the website. Low review risk, and iterating doesn't require going through the store.
8. Uncertain
- 1.9M is self-reported cumulative signups; active and paying users are unknown, and subscription revenue is unknown.
- The extension's 4,000 is an approximate figure from the store, with no 90-day curve (extops doesn't index it), so it's unknown whether it grew gradually from 6 to October or jumped all at once.
- Whether 판다랭크's weekly report also reads the blogger's own back-end: not verified.
- Platform risk: Naver may later block Creator Advisor's internal endpoints too, or rule the approach violates terms.
- Operator: the footer says 더씨커 & 제이지루나, the extension uses a personal gmail, the posting extension uses jgluna.com; how the two split the work is unclear.
Sources
- Chrome Web Store listing: chromewebstore.google.com/detail/bibmcbmicbdfcicpajfgkiejlcp…
- Extension privacy policy: blogdex.space/extension-privacy
- Pricing and quotas: blogdex.space/limits; login page 1.9M: blogdex.space/login
- Shutdown timeline: brunch.co.kr/@mobiinside/7384 (2026-05-18)
- User migration after shutdown: m.blog.naver.com/chanjoopark1004/224128585317; m.blog.naver.com/kim-hyunhak/224101523081
- 3.0 redesign: m.blog.naver.com/tmdtjq80/224364815643; mepix.ai/insights/bldex-blog-index-ai-visibility
- 2024 year 47,000 KRW 30-day pass: blog.naver.com/isdn2721/223517181824
- Experience team pricing: blogdexreview.space/pricing
- App:play.google.com/store/apps/details?id=space.blogdex.app
- chromestore library (item / item_snap, 2026-11-01 to 11-07): user counts, review counts, and publish dates for this extension and competitors
- x-radar: "blogdex" "블덱스" 90 days 0 posts