Download websites that use Naver Analytics

About Naver Analytics

An analytics tag usually says little about a company beyond the fact that somebody is watching the numbers. Naver Analytics is the exception, because choosing it is a statement about which market a site is trying to be found in.

The service is run by Naver Corporation, the Korean internet company whose search portal and surrounding services carry a large part of that country's web traffic, and the Proprietary tag is a JavaScript snippet that sites have been pasting into their pages since 2012. No theme ships it by default and nobody installs it by accident. A site carries the tag because somebody wanted to measure arrivals from a Korean-language search ecosystem and wanted those numbers next to their listings and campaigns.

As of October 2026 we detect the tag on 292,841 sites, and 207,130 of those sit in South Korea. The remainder is the part worth paying for. Exporters, tourism boards, universities, cosmetics and fashion brands, travel operators and inbound marketing shops based outside the country deploy the tag when they start courting Korean buyers, and no directory lists them, because from the outside those sites look like any other company in their home market.

The suffix column shows why a naive geographic filter fails here. The suffix that recurs across the population is .com rather than a national one, partly because Korean companies register generic domains for international reach and partly because foreign firms entering the market keep the domain they already have and simply add the tag. Filtering a domain list by country code alone would drop a large share of the businesses actually selling into that market, which is the specific failure this column corrects.

Pairing beats presence when qualifying these sites. A page carrying this tag alongside a Western analytics platform is running two markets at once and usually has the budget and the staff that implies, while a page carrying only the Korean tag is either a domestic business or a very narrow export play. Sorting the population that way costs nothing once the whole table is in front of you and it turns a single boolean column into a usable qualification.

Two limits apply. A tag outlives the campaign that justified it, so presence proves intent at some point in the past rather than current spending. And detection needs the snippet in the served markup, so instances injected through a tag manager at runtime are harder to see and the count should be read as a floor. Sites also drop the tag when they leave the market, and a departure leaves no trace at all in a single snapshot, so the table describes a standing population rather than a flow into or out of it. A per-domain check confirms one site at a time. The download turns the tag into a market-entry list: everyone measuring Korean traffic, sorted by where they actually are.