Naver Technical SEO: The Checklist for Yeti

A Korean website can pass every Google technical audit you own and still be close to invisible on Naver. Not underperforming. Not indexed. Naver's crawler will not find your site at all unless someone registers it manually, and there is no version of Googlebot behaviour that compensates for that.

This is the part of Korean SEO that gets skipped most often, because it is unglamorous and because most technical SEO training assumes Google-shaped defaults. Automatic discovery. hreflang. Pixel-width title limits. Reliable JavaScript rendering. Naver breaks or narrows all four.

What follows is the technical layer specifically, the work that has no Google equivalent or where the Google equivalent gives you the wrong answer. Content strategy, keyword research and the Naver ecosystem sit in separate articles. This one is for whoever owns the site.

Start with the crawler, because nothing works before it

Naver's crawler is called Yeti. It is documented, it respects robots.txt, and it behaves differently from Googlebot in one decisive way: discovery is not automatic in practice. You register the domain in Naver Search Advisor, verify ownership, submit a sitemap and an RSS or Atom feed, and request indexing. Skip that and you can wait indefinitely.

Three failure modes account for most of the cases we see.

robots.txt silently blocks Yeti. Plenty of sites allow Googlebot and Bingbot by name and then fall through to a restrictive default. Yeti hits the default and leaves. This is a one-line fix that nobody looks for because the site looks healthy in Search Console.

Content that only appears after interaction. Anything that loads on click, on scroll, or behind a tab tends to confuse Naver's crawler. If your product specifications live inside an accordion that fires on click, assume Naver may not see them. Server-side render or pre-render the content that matters.

Encoding. Most modern sites are already UTF-8, so this rarely bites. When it does, it bites hard, because Hangul rendered through the wrong encoding is not merely ugly to a reader, it is unparseable to the engine trying to categorise your page.

Naver Search Advisor is narrower than Google Search Console. It gives you crawl and indexing reports showing what was collected, blocked or skipped and why, HTML diagnostics for broken tags and structural problems, a search-appearance report for how your metadata renders on Naver, and a site-structure diagnosis covering HTML structure, link management and mobile usability. What it does not give you is the query-level performance depth you are used to. That is a real limitation and worth setting expectations about early, because it changes what reporting is possible.

The hreflang problem, and what to do instead

Naver does not support hreflang. That single fact breaks the standard international SEO playbook, because hreflang is how most multilingual sites tell a search engine which version of a page belongs to which audience.

The documented workaround has two parts. Use the HTML meta language tag in your page template, in the form of a content-language declaration set to Korean. And submit a Korean-language sitemap, covering only the Korean version of the site, through Naver Search Advisor.

The strategic consequence is bigger than the technical one, and it is worth sitting with. Without hreflang, you cannot simply signal to Naver that a Korean translation exists alongside an English original and let the engine sort out which to serve. You need genuine Korean-language pages, treated as pages in their own right, with their own metadata written in Korean, submitted in their own sitemap. In practice that pushes toward a real Korean subdirectory or subdomain rather than a machine-generated language switcher bolted onto an English site.

Which, incidentally, is the same conclusion the content side of Korean SEO reaches from a completely different direction. Naver's document-level ranking system rewards first-hand, experiential, original writing, and translated copy tends not to read that way. Two independent lines of reasoning arriving at the same architecture is usually a sign the architecture is right.

Metadata: shorter than you think, and in Korean

Naver Search Advisor guidance puts titles at roughly 40 characters and descriptions at roughly 80, sized for double-byte characters like Hangul rather than for Latin pixel widths. That is dramatically tighter than Google practice, and it is the kind of detail that a global CMS template will violate everywhere by default.

Two practical notes. First, these are long-standing best-practice figures rather than a hard technical cap, so treat them as targets and check how your pages actually render in Search Advisor's search-appearance report rather than trusting the number alone. Second, they need to be unique per page. Yeti uses title and description to differentiate and categorise pages, and duplicate metadata across a large site is a categorisation problem rather than merely a missed opportunity.

Write them in Korean. Not translated at the last minute from an English tag, written in Korean, because Naver uses them to understand what the page is about.

The two-section results page nobody plans for

Here is a structural point that changes how you scope technical work.

Naver separates website results from Naver property results on its organic results page. Those are, functionally, two different competitions. Your own domain competes in one. Naver Blog, Cafe, Knowledge iN, Shopping and Place content competes in the other. And Naver gives its own properties prominent placement.

Layered on top, Naver's results page is built from Smart Blocks, which replaced the older VIEW tab. Results are grouped by inferred intent rather than by content format, so the same query can produce a page composed of quite different modules depending on what Naver thinks the user wants.

What this means technically is that "we fixed the site, now we rank" is not a complete theory of Naver visibility. Fixing the site makes you eligible in one of the two sections. It does nothing for the other, which is a content-placement question rather than a technical one. Any Naver scope that promises visibility while only touching your own domain is under-scoped, and you should ask about it directly.

Structured data, and an honest caveat

Add structured data. Organization, Service, BreadcrumbList, FAQPage, Product where relevant. Do it properly and validate it.

Now the caveat: Naver does not publish how it uses schema markup, and we are not going to pretend to know. What we can say is that structured data is doing real work for the Google side of a Korean campaign, that Naver's HTML diagnostics reward clean, well-formed markup, and that AI answer systems on both engines draw on well-structured content. So the cost is low, the Google-side benefit is documented, and the Naver-side benefit is plausible but unproven. That is a reasonable bet, and it is a different claim from "schema is a Naver ranking factor," which we have not seen evidenced anywhere.

Treat any agency that gives you a confident Naver algorithm formula with suspicion. Naver publishes descriptions of what its systems value, not weights. C-Rank and D.I.A. have official help pages describing their intent. P-Rank, which covers external web documents, is discussed by practitioners with far less official documentation behind it. Precision beyond that is extrapolation.

Task	Why it is specific to Naver	Evidence level
Register and verify in Naver Search Advisor	Discovery is not automatic. Nothing downstream works without this	Documented by Naver
Submit sitemap plus RSS or Atom feed	Naver uses both. A sitemap alone is the common half-measure	Documented by Naver
Explicitly allow Yeti in robots.txt	Named allowances for Googlebot with a restrictive default will block Naver	Practitioner-documented
Replace hreflang with the meta language tag	Naver does not support hreflang. Pair with a Korean-only sitemap	Reported, named source
Rewrite titles to around 40 characters, in Korean	Search Advisor guidance, sized for double-byte Hangul	Reported, Naver guidance via secondary source
Server-side render click-to-load content	Content behind interaction is often missed by Yeti	Practitioner-documented
Confirm UTF-8 encoding end to end	Hangul in the wrong encoding is unparseable, not just ugly	Practitioner-documented
Plan for two organic sections, not one	Website results and Naver property results compete separately	Reported, multiple sources
Add and validate structured data	Documented benefit on Google, plausible but unproven on Naver	Uncertain for Naver specifically
Run Search Console and Search Advisor side by side	Neither tool sees the other engine. Both are needed for a baseline	Practitioner-documented

What runs remotely, and what does not

Since this comes up in every procurement conversation, the honest split.

Everything in the table above is deliverable by a competent technical team from anywhere. Yeti does not know or care where the person configuring robots.txt is sitting. Search Advisor is a web interface. Crawl diagnostics, architecture, structured data, encoding, rendering strategy and Core Web Vitals are all engine-facing rather than culture-facing work.

What does not run remotely is the writing. Naver Blog, Cafe and Knowledge iN performance depends on original Korean produced by people who write Korean natively, and we have not found a single independently audited case anywhere of a non-Korean agency sustaining performance in those properties without native Korean writers. Anything paid or commerce-facing has a harder constraint still: Naver Ads, Brand Search and Smart Store require a Korean business registration number, a Korean bank account and often a Korean address.

The market itself is the evidence for that split, and it is worth looking at rather than taking on trust. The agencies with published Naver and Google capability are either Korean or Korea-focused: InterAd and Asiance in Seoul, The Egg, Inquivix in Gangnam and Daegu, Next-T, Seoulful Connect, Punch Digital Marketing, Eastforte. Look at the ones headquartered outside Korea and the pattern holds from the other direction. Elite Asia and marketingagency.sg, both Singapore-based, market Korean services offshore and both state explicitly that they employ native Korean linguists and produce original Korean content rather than translated copies.

Nobody credible in this market is claiming the writing can be done without native Korean speakers. The offshore providers say so themselves, in their own marketing. So the workable model is hybrid, and it is worth being blunt about which half is which rather than blurring it in a capability slide.

One more thing about how Naver ranks, because it changes the brief

Naver's ranking appears to work in two steps rather than one. First it selects which content categories are relevant to the query, then it orders results within those categories. That is a different shape from a single ranked list, and it has a consequence for technical work that is easy to miss.

If your content is not categorised in a way Naver associates with the query, you are not competing badly, you are not in the competition. Ordering never gets a chance to apply. Which puts unusual weight on the things that tell Naver what a page is about: the Korean title and description, clean structure, the topical consistency of whatever property the content sits on.

It also explains a pattern that otherwise looks random. A page that seems technically stronger than a competitor's, and better written, can be absent while the competitor is present. Not because it was outranked. Because it was sorted into a different category, or into none.

Worth stating the evidence level plainly: this two-step description comes from practitioner analysis rather than from Naver documentation, and Naver publishes no ranking weights at all. Treat it as a useful model of observed behaviour, not as a specification.

What to ask before you sign anything

Five questions. They are short, and the answers are diagnostic.

Will you register and verify the site in Naver Search Advisor, and can you show me an anonymised crawl and indexing report from work you have done before? Who writes the Korean, and are they native Korean writers or are they translating from an English brief? How will you handle hreflang given that Naver does not support it? Which entity holds the Naver accounts, ours or yours, and what happens to them if we part ways? And what exactly are you promising, given that Naver publishes no ranking weights?

That last one is the tell. An agency willing to say "we commit to deliverables and quality standards, not to a position" is describing the actual state of the evidence. An agency that guarantees a Naver rank is describing something it cannot control.

For how the results page itself is changing, including what Naver's AI answer layer does to click behaviour beneath it, see our SEO service page for South Korea. For the citation question specifically, being surfaced inside generative answers rather than inside search results, that belongs to our GEO service for South Korea.

---

Frequently Asked Questions

Why is my site indexed on Google but not on Naver?

Almost always one of three causes. The domain was never registered and verified in Naver Search Advisor, and Naver discovery is not automatic in the way Googlebot discovery is. Or robots.txt names Googlebot and Bingbot as allowed but falls through to a restrictive default that blocks Yeti. Or the content that matters only loads after a click or a scroll, which Naver's crawler often misses. Check those three in that order before assuming anything more complicated.

Does Naver support hreflang?

No. The documented workaround is to use the HTML meta language tag set to Korean in your page template, and to submit a Korean-language XML sitemap covering only the Korean version of the site through Naver Search Advisor. The strategic consequence matters more than the technical one: you need genuine Korean-language pages treated as pages in their own right, rather than a translated layer that hreflang signals to the engine.

How long should a title tag be for Naver?

Naver Search Advisor guidance puts titles at roughly 40 characters and meta descriptions at roughly 80, sized for double-byte characters such as Hangul rather than for Latin pixel widths. That is considerably tighter than Google practice and most global CMS templates will breach it by default. Treat the figures as targets rather than hard caps, keep them unique per page because Yeti uses them to categorise, and check how your pages actually render in the search-appearance report.

Can a technical SEO team outside Korea do Naver work?

Yes for the technical layer, and this is worth separating clearly from the rest. Search Advisor registration, sitemap and feed submission, robots.txt configuration, crawl diagnostics, encoding, rendering strategy, architecture, structured data and Core Web Vitals are all engine-facing work that does not depend on location. What does not travel is the Korean writing, and anything paid or commerce-facing, since Naver Ads, Brand Search and Smart Store require a Korean business registration number, a Korean bank account and often a Korean address.

Is structured data a Naver ranking factor?

We have not seen that evidenced and will not claim it. Naver does not publish how it uses schema markup. What is documented is that structured data does real work on the Google side of a Korean campaign, that Naver's HTML diagnostics reward clean well-formed markup, and that AI answer systems on both engines draw on well-structured content. Low cost, proven Google benefit, plausible but unproven Naver benefit. That is a reasonable bet stated honestly rather than a ranking-factor claim.

What does Naver Search Advisor give me that Search Console does not, and vice versa?

Search Advisor gives you crawl and indexing reports showing what was collected, blocked or skipped and why, HTML diagnostics, a site-structure diagnosis covering structure, links and mobile usability, and a search-appearance report for how metadata renders on Naver. It gives you far less query-level performance depth than Search Console. Neither tool can see the other engine, so both are required for a real baseline, and GA4 on its own cannot see referrals that happen inside Naver's own perimeter.

Why does fixing my website not seem to move Naver visibility much?

Because Naver runs two organic competitions and your website only enters one of them. Naver separates website results from its own property results, giving Blog, Cafe, Knowledge iN, Shopping and Place content prominent placement, and it groups results into intent-based Smart Blocks rather than a single ranked list. Technical work makes you eligible in the website section. Presence in the property section is a content-placement question, which is why a Naver scope that only touches your own domain is under-scoped.

---