Two search engines, one page

Companies entering Korea often ask whether they need a separate Naver strategy. For a company website the honest answer is that the page work is shared. Both Google Search Central and Naver's webmaster guide (Naver Search Advisor) ask for a Korean page that answers a real question, loads as standard HTML, has its own title and description, and is listed in a sitemap the robot can fetch. The differences are in registration, verification and a few reporting tools, and those are covered below.

Two facts frame everything else. Google states that it determines a page's language from 'the visible content of your page' and does not use hreflang or the HTML lang attribute for that purpose (checked 2026-09-16). Naver's guide describes search engine optimization as 'organizing the content on your site so that the search engine can understand it', and warns that a site whose entire content loads through JavaScript may not be reflected in search (checked 2026-09-16). A Korean page therefore has to be Korean in its body text and readable without executing scripts before any tag helps.

Make the Korean page useful before optimizing its metadata

Write down the questions Korean customers ask before they enquire, and answer them in the page body: what the product does, whether it is available to a customer in Korea, the billing currency and tax treatment, the support language, and the exact next step. Have the wording reviewed by a Korean speaker who understands the product, not only the language.

Google's self-assessment guidance for helpful content asks whether a page provides 'original information, reporting, research, or analysis' and whether it is 'created primarily to help people' rather than to attract search visits; it also asks whether the use of automation, including AI generation, is 'self-evident to visitors through disclosures or in other ways' (checked 2026-09-16). Google's spam policies separately list, as an example of scaled content abuse, generating many pages through 'automated transformations like synonymizing, translating, or other obfuscation techniques' where little value is provided (checked 2026-09-16). Translating your own pages is not the target of that policy; publishing hundreds of machine-translated pages without review is closer to it.

Avoid producing near-duplicate Korean pages that differ only by a city or industry name. Naver's guide warns that opening several sites with identical content to increase exposure 'may be disadvantaged in search exposure' (checked 2026-09-16).

Give the Korean version a stable, accessible URL

Google recommends 'using different URLs for each language version of a page rather than using cookies or browser settings to adjust the content language', and explains why: Googlebot generally crawls from the United States and does not send an Accept-Language header, so language switching based on browser settings may hide versions from it. Its comparison of URL structures lists country-code domains, subdomains and subdirectories as workable and marks URL parameters (site.com?loc=de) as not recommended (checked 2026-09-16).

Naver adds a constraint that affects the choice: Naver Search Advisor registers sites 'by host only' — www.mysite.com or blog.mysite.com can be registered, but www.mysite.com/myid cannot (checked 2026-09-16). A Korean subdomain (kr.example.com) therefore needs its own Naver registration and verification, while a subdirectory (example.com/ko/) is covered by the registration of the main host. Either works; decide knowingly.

Do not redirect visitors automatically based on browser language as the only way to reach the Korean page. Google advises against automatic redirection based on perceived language because it can prevent users and search engines from viewing all versions, and asks for links that let users choose a language. The W3C's guidance on language negotiation makes the same point from the user's side and asks for a visible override on every page (checked 2026-09-16).

Serve meaningful HTML without waiting for scripts

Google processes JavaScript pages in three phases — crawling, rendering and indexing — and notes that a page 'may stay on this queue for a few seconds, but it can take longer than that'. It adds that 'server-side or pre-rendering is still a great idea because it makes your website faster for users and crawlers, and not all bots can run JavaScript' (checked 2026-09-16).

Naver's guide is more categorical. If content is not appearing in search, it asks you to check 'whether the page is structured so that all content is loaded by JavaScript' and states that most search engines recommend serving content in standard HTML markup. It also shows that a link written as an a element with an href can be followed, while a link expressed only as a JavaScript onClick handler cannot be resolved by the robot (checked 2026-09-16). Naver further asks that redirects use HTTP redirects rather than JavaScript or meta refresh, and notes that site ownership verification is not supported when the main page redirects via JavaScript or meta refresh.

Practical test: open the Korean URL with JavaScript disabled. If the body text and the menu links are visible, you pass. Pages translated live in the browser by an API call do not pass this test.

Titles, descriptions and Open Graph, per page and in Korean

Google asks for 'distinct text that describes the content of the page in the title element for each page on your site', warns that keyword stuffing 'can make your results look spammy', and says descriptions should be unique because 'identical or similar descriptions on every page of a site aren't helpful'. It may rewrite a title link when it detects a problem, and lists a language mismatch as one such case (checked 2026-09-16).

Naver's content markup guide says the same in stronger terms. It asks that a title describe the topic of that specific page, warns that titles with 'keywords repeated two or more times, spam keywords, keywords unrelated to the content or promotional phrases' may be disadvantaged, and asks you not to give every page the same title or to change the main page title frequently for exposure. For the description it suggests 'a short paragraph of one or two sentences' and lists copying the whole body, duplicating the title, or listing keywords as patterns to avoid. It recommends adding Open Graph tags because Naver's robot may also use them in page analysis (checked 2026-09-16).

The most common translation defect here is a Korean body under an English title element. Check title, meta description and og:title on every Korean URL.

hreflang between true equivalents, canonical in the same language

If the Korean page is a translation of an English page, connect them with hreflang using one of Google's three methods — link elements in the head, HTTP Link headers, or xhtml:link entries in the sitemap. Google's rules (checked 2026-09-16): annotations must be reciprocal ('if page X links to page Y, page Y must link back to page X'), each version must list itself and every other version, URLs must be fully qualified with protocol, language codes follow ISO 639-1 and optional region codes ISO 3166-1 Alpha 2 (ko, ko-KR, en, en-US), a region code alone is not allowed, and x-default marks the fallback page for unmatched visitors.

Do not connect pages that are not equivalents. An English guide about entering Korea and a Korean guide about a different topic are different articles; linking them with hreflang tells search engines something false. This is why Foliroom's own English and Korean guides carry no hreflang between them.

Give each Korean page a canonical URL in Korean. Google states: 'if you're using hreflang elements, make sure to specify a canonical page in the same language, or the best possible substitute language if a canonical page doesn't exist for the same language' (checked 2026-09-16). Pointing a Korean page's canonical at the English original tells Google not to index the Korean page. Naver's site-creation guide likewise asks that duplicate addresses either declare a representative URL with rel=canonical or redirect to it with a 301.

Sitemaps, RSS, robots.txt and noindex

Sitemaps: Google limits a single sitemap to 50 MB uncompressed or 50,000 URLs, ignores priority and changefreq, and uses lastmod only when it is 'consistently and verifiably' accurate. Submission is through Search Console or a Sitemap line in robots.txt (checked 2026-09-16). Naver's guide asks you to submit an XML sitemap under 'Request – Sitemap submission' and an RSS feed under 'Request – RSS submission', treats both as content feeds it revisits periodically, asks that recent posts include the full body in RSS, and warns that links written as relative paths or pointing to a host other than the registered site are not collected (checked 2026-09-16). List only Korean URLs that actually exist.

robots.txt: Naver's robot is named Yeti. Naver asks that access be controlled through robots.txt rather than IP blocking, because robot IP ranges change, and gives the minimal allow rule as 'User-agent: Yeti' followed by 'Allow: /' (checked 2026-09-16). Confirm that your firewall or bot-protection layer does not block Yeti, and that the Korean path is not disallowed by mistake.

noindex: keep previews, staging and unapproved drafts out of both indexes with a robots noindex meta tag or X-Robots-Tag header. Google notes that for noindex to work the page 'must not be blocked by a robots.txt file' and must be reachable by the crawler; otherwise the directive is never read (checked 2026-09-16). Naver's guide states that pages marked noindex are excluded from search reflection, and asks you to remove a stray noindex from the main page if it is not appearing.

Structured data that matches what readers see

Naver's structured data introduction says Naver recommends schema.org markup in Microdata or JSON-LD (checked 2026-09-16). Google's structured data policies require that markup 'must be a true representation of the page content' and that you 'don't mark up content that is not visible to readers of the page' (checked 2026-09-16). Translate the values inside your structured data — organization description, product name, offer currency, opening hours — so they match the Korean body text, and keep them identical between the mobile and desktop versions.

Register, verify and submit in both tools

Google Search Console offers HTML file upload, HTML meta tag, Google Analytics, Google Tag Manager and DNS record verification. DNS verification is required for a Domain property and 'verifying ownership of a root domain automatically verifies ownership of all subdomains', while HTML file and meta tag methods work only for URL-prefix properties (checked 2026-09-16). If your Korean pages live on a subdomain, a Domain property keeps reporting in one place.

Naver Search Advisor verifies ownership with an HTML meta tag or an HTML file upload. Its guide lists conditions under which verification fails: a firewall blocking Naver's robot, a main page that redirects via JavaScript or meta refresh, or a verification tag placed inside a frame. It states that content is reflected in search 'within a maximum of one week' after the robot visits, that a site: query in Naver web search shows whether pages are reflected, and that its Site Diagnosis report classifies pages collected in the last 90 days as indexed, collection-restricted, index-excluded or needing SEO work (checked 2026-09-16). Its crawl request tool queues individual URLs by priority and does not visit them in real time.

The checklist below compares what each tool needs from you.

Item	Google	Naver
Registration unit	Domain property (all subdomains) or URL-prefix property	host only; each subdomain registered separately
Ownership verification	HTML file, meta tag, Analytics, Tag Manager, DNS	HTML meta tag or HTML file
Feeds accepted	XML sitemap, RSS/Atom, text sitemap	XML sitemap and RSS with full text
Crawler name	Googlebot	Yeti
Rendering expectation	renders JavaScript after a queue of unspecified length; recommends server-side rendering	recommends standard HTML; flags all-JavaScript content as a reason for non-reflection
Language signal	visible content; hreflang for equivalents; canonical in the same language	visible content and unique Korean titles; rel=canonical or 301 for duplicates

AI features need the same foundations, not new files

Google's documentation on AI Overviews and AI Mode states: 'There are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary.' A page must be indexed and eligible to be shown with a snippet, and 'you don't need to create new machine readable files, AI text files, or markup to appear in these features'. Existing controls — nosnippet, data-nosnippet, max-snippet and noindex — limit what is shown. Google adds that meeting every requirement 'doesn't mean that Google will crawl, index, or serve its content' (checked 2026-09-16).

Read that as permission to stop looking for a separate AI checklist. Make the business, the service scope, the conditions and the sources explicit in the Korean body text, and keep structured data consistent with it.

A measurement sheet for the first months

Track each Korean URL on one row: the customer question it answers, index status in Search Console and Naver Site Diagnosis, impressions and clicks, visits, and enquiries or bookings. An indexed page that produces no enquiries usually has an explanation problem rather than a metadata problem; fix the page before adding more pages. Naver's own guide says its robot's visit precedes reflection by up to a week, and Google says indexing is never guaranteed, so treat the first weeks as observation, not as a verdict.

How Foliroom fits

Foliroom serves approved Korean pages as stored HTML with a stable URL, a Korean title and description, hreflang only between genuine language equivalents, and a canonical in the page's own language; previews stay behind authentication with noindex. Registering and verifying your site in Google Search Console and Naver Search Advisor, submitting sitemaps and reading the reports remain your team's work. Foliroom does not promise rankings, traffic or AI citations. Its website, sign-up and customer workspace are available in English, Japanese and Korean.

Korean website SEO: a launch checklist for Google and Naver