GSC vs Naver SearchAdvisor vs Cloudflare — Same Site, Three Datasets, Three Stories
TL;DR: For a Korean-targeted site, GSC (Google Search Console) shows only 10–20% of the real traffic. The real channels are Naver SearchAdvisor + Cloudflare Web Analytics. GSC is the side dish, not the main course.
The trigger — panic over GSC
One month after migrating a new domain (taystudios.com). Opened GSC:
Last 3 months:
- Total clicks: 2
- Total impressions: 777
- Avg CTR: 0.3%
- Avg position: 14.8
Impressions peaked 5/14, dropped to near zero by 5/24. "Is the site dead?"
Then Cloudflare Web Analytics:
Last 24 hours:
- Page views: 79
- Visits: 55
55 people a day. The data contradicts. And here's the truth — the two tools measure completely different things.
What each tool actually measures
| Tool | What it measures | Source |
|---|---|---|
| Google Search Console | Impressions/clicks on Google search results only | google.com → our site |
| Naver SearchAdvisor | Same, for Naver | naver.com → our site |
| Cloudflare Web Analytics | All traffic that hits the site | Direct · Bing · Naver · Daum · referral · social · LLM — everything |
= GSC ↓ + Cloudflare stable = traffic from non-Google sources is stable. No contradiction.
Actual numbers — same site, one month
Google Search Console (last 30 days)
Clicks: 2
Impressions: 777
CTR: 0.3%
Avg position: 14.8
Top 5 keywords surfacing the site:
- "image watermark" (impressions 2, clicks 1, position 8.5)
- "net salary 80M KRW" (impressions 4, position 6.8)
- "Local Tax Act housing property tax rate 2026" (impressions 3, position 10.3)
- "MOIS car acquisition tax 7%" (impressions 2, position 11.5)
- "background remover site" (impressions 2, position 48.5)
Naver SearchAdvisor (last 30 days)
Total clicks: 230 (= 115× GSC)
Total impressions: 26,000 (= 33× GSC)
Avg CTR: 0.9% (= 3× GSC)
Impressions spiked from 5/22 → averaged 2,000–3,000/day → peaked at 7,600 on 5/27.
Cloudflare Web Analytics (24 hours)
Page views: 79
Visits: 55
Country: Korea 53 / China 1 / US 1
Visits by source:
- m.search.naver.com: ~18
- search.naver.com: 16
- search.daum.net: 11
- chatgpt.com: (yes)
- Total Naver+Daum = 45 (79%)
Top page: /tools/baby-formula/ (16 visits)
Finding 1 — Google is a 20% channel for Korean sites
Naver = 33–115× GSC
Google's market share in Korea is 30–35%, but our Google traffic is even smaller. Reasons:
a. Google sandbox (the 6–12 week probation for new domains)
Migration 5/9 → 6/2 = week 3.5. 122 pages indexed but rankings are throttled.
b. AI Overview kills clicks
Searching "net salary 50M KRW" gets a direct AI answer from Google → no click. Google's Korean policy AI (Gemini) is stronger than Naver's.
c. Korean NLP
Queries like "parental leave benefits calculator" — Naver matches our pages more accurately. Google's Korean NLP is weaker than Naver's homegrown model.
→ Looking at GSC misses 80% of the channel mix.
Finding 2 — Cloudflare's real data is inside "Visits detail"
The main screen doesn't have it. Click the Visits card → detail view:
Visits by source (Referrers):
- m.search.naver.com
- search.naver.com
- search.daum.net
- chatgpt.com
Hosts:
- taystudios.com
Top paths:
- /tools/baby-formula/: 16
- /tools/salary/: ...
- /image/bg-remove/: ...
Browsers, OS, Country, Device types
This detail shows the real sources. Even with GSC at "0 Google clicks today," Naver mobile + desktop + Daum still bring 50+ visits.
Especially chatgpt.com referrer = LLM searches are starting to surface the site. Neither GSC nor Naver shows this.
Finding 3 — Top-page mismatch
| Measure | Top page |
|---|---|
| GSC top keyword → page | salary · property-tax · cartax · bg-remove |
| Cloudflare top visited page | /tools/baby-formula/ |
baby-formula doesn't show in GSC at all, yet it's #1 in Cloudflare. Why? Naver "infant formula amount" matches well. That traffic is invisible to GSC, so baby-formula is invisible from Google's angle.
→ To know the real top pages, look at Cloudflare. GSC data is just the tip of the iceberg.
How to use each tool
GSC — for Google evaluation + keyword discovery
- Which queries surface the site
- Indexing status (how many pages indexed)
- Average position
- Per-page index exclusion reasons
- Don't use it as a traffic gauge — Korean sites only see the tip
Naver SearchAdvisor — the main channel for Korean users
- Most important for Korean-targeted sites
- Sitemap submission, manual page collection requests
- Impression/click trends (covers almost all Korean traffic)
- robots and page diagnostics
- Without registration, the engine only finds the site by chance — very slow
Cloudflare Web Analytics — real traffic + sources
- All channels combined (Direct + every engine + referral)
- Sources detail — where visitors came from
- Top paths — the actually popular pages
- Country, device, browser breakdown
- LLM referrers (chatgpt.com · perplexity.ai) starting to appear
- Privacy-friendly — no personal tracking
Our action priorities
After combining all three:
- Register Naver Webmaster + submit sitemap — biggest ROI (79% of traffic)
- Request indexing via GSC URL Inspection on changed pages — partially route around sandbox
- Bing Webmaster (1-click GSC import) — +1–3%
- Daum Webmaster — +5–10%
- Check Cloudflare sources regularly — track the LLM-referrer trend
One-liner
Korean sites can't be evaluated on GSC alone. Naver + Cloudflare, side by side.
GSC shows "Google search data". The real traffic for a Korean-targeted site is Korean engines + AI search + Direct — that's the main current. Judging the site by one dataset misses the picture. The classic trap for new-domain operators.
Related
- 12 Core SEO·Search-Engine Concepts — sandbox · E-E-A-T · DA · CTR · AI Overview
- (Coming) Adding llms.txt — site metadata for the AI-search era
Comments