Multilingual Webpages, Meta, Twitter Tags, Search Engine Registration and SEO Writing Guide

Multilingual Page Strategy at a Glance

• Decide which language page to show first by referencing the visitor's browser language and location. If automatic detection is difficult, showing a language selection modal first is an option.

• For URL structure, either append language codes like /ko, /en or use subdomains like ko.example.com. It's important to stick consistently to one approach. A subdomain means a name placed at the front like blog.example.com.

• Even for language-specific pages, don't translate titles and descriptions word-for-word; refine them to phrases commonly used locally. Even with the same information, slightly different tones can improve click-through rates.

• Put repeated meta tags into layout components or build scripts as defaults, and load only the language-specific values from a CMS or translation files to reduce mistakes.

How to Write Title Tags

• Research search keywords and include words that match the page topic, keeping it within 50–60 characters. If too long, it will be truncated in search results.

• Put the brand name at the end; if the brand is well-known locally, placing it at the front is fine.

• Avoid duplicate titles by mixing core keywords and specific details for each path. For example, for a learning guide include the learning stage or difficulty.

• In Korean, shorten particles and endings for conciseness; in English, combinations of core keywords tend to perform better than full sentences for search visibility.

Tips for Description Meta Tags

• Keep the core message within 120–155 characters so it appears naturally in search previews.

• Include a suitable call-to-action once for each language. Example: Korean "지금 확인하세요" (Check now), English "Get started today."

• Write unique descriptions for each page and do not copy the same sentence across pages.

• After build, validate special characters and line breaks to ensure the HTML isn't broken.

Thumbnails and Open Graph

• A default image of at least 1200×630px and under 300KB will display clearly on most platforms.

• When putting text on images, prepare different language-specific versions or use icons and colors instead of text to differentiate.

• Translate og:title, og:description, and og:site_name to match the page language, and set og:locale to language and region like ko_KR, en_US. Add other language versions of the same page under og:locale:alternate.

• Put language-specific image descriptions in og:image:alt to improve accessibility and search readability.

Twitter Card Meta Tags

• twitter:card is usually set to summary_large_image to show a large thumbnail.

• Fill twitter:title, twitter:description, twitter:image, and twitter:site for each language, and keep descriptions around 70 characters as Twitter tends to truncate strictly.

• Twitter (X), Threads, and LinkedIn often read Open Graph values, so keep the information consistent when possible.

Essential Meta Tags to Include

• Put essential tags like charset, viewport, and theme-color on every page.

• If supporting PWA, load the manifest link and icon meta tags from a shared layout and use the manifest's multilingual fields to change the app name per language.

• Keep link rel="preload" or preconnect for only necessary resources regardless of language to maintain initial load speed.

Robots Meta and Indexing

• Public pages can use the default index, follow.

• For temporary pages or many similar pages, use noindex, follow to hide them from search results while allowing crawlers to follow links.

• For pages you want completely hidden (e.g., experiments), use noindex, nofollow or enforce blocking via the X-Robots-Tag header on the server.

Understanding robots.txt

• The robots.txt placed at the site root is like a sign that says "these paths are okay to crawl, these paths please skip."

• If language directories follow the same rules, list common allow/disallow paths under User-agent: *.

• To restrict only a specific language page, specify the exact path like Disallow: /ja/private.

• At the end, list all language sitemap addresses like Sitemap: https://example.com/sitemap-ko.xml.

Sitemap Management Tips

• For many pages, use a sitemap-index.xml to group language-specific sitemaps, e.g., sitemap-ko.xml, sitemap-en.xml.

• Separate frequently changing pages from nearly static pages so lastmod dates remain trustworthy.

• If you want to provide image or video information separately, create dedicated sitemaps and link them to the language pages.

Canonical URL Guidance

• Canonical is a signal that says "this URL is the original, please show this in search results."

• Even for multilingual pages, if each language page is perceived as unique content, set that page itself as canonical.

• If other languages temporarily show the original content during translation, set the original URL as canonical to prevent duplicate indexing.

• If you separate languages with query parameters like ?lang=ko, set a fixed canonical path and use alternate and hreflang to indicate actual language links.

Understanding Alternate and hreflang Easily

• link rel="alternate" hreflang="ko-KR" is a sign that says "the Korean version of this page is here."

• Include the same set of links on all language pages so search engines are not confused.

• Designate the global default page or language selection hub as hreflang="x-default" to indicate "please choose a language."

• Naver may require more than just hreflang; prepare naver-site-verification meta tags and structured data as well.

Using a Table of Contents to Help SEO

• Putting a table of contents at the top of long articles helps visitors jump directly to the part they want, increasing dwell time and lowering bounce rates.

• Anchor links in the table of contents help search engines better understand the document structure, increasing the chance of jump links or sitelinks on Google or Naver.

• On mobile, use collapsible components and shareable anchor links so you can link directly to a specific language section.

Registering Your Site with Major Search Engines

Google Search Console

• Register the root domain as a domain property and verify ownership via a DNS TXT record. Think of DNS like the domain's address book.

• Submit language-specific sitemaps and regularly check the International Targeting report for hreflang errors.

Naver Search Advisor

• After registering the site, verify ownership by uploading an HTML file or using a meta tag.

• Frequently check robot blocking status and sitemap submission, and preview titles and descriptions in both PC and mobile to ensure they appear as intended.

Kakao Business Registration

• Log in to business.kakao.com with a Kakao account, agree to the integrated terms, and create a business account.

• Open a KakaoTalk channel and convert it to a business channel to link exposure points like maps, chatbots, and ads at once.

• Submit business registration documents and customer center information in the admin center, and add optional features like Kakao Sync or talk-based consultation if needed.

DuckDuckGo and Yahoo Search Exposure

• These services have no separate webmaster tools. Adding your site to Bing Search Console and submitting sitemaps will usually be reflected automatically.

• Maintain structured data and a clear hreflang system so language versions appear across partner engines that share Bing's index.

• If a new page doesn't appear, use Bing URL submission or IndexNow to request rapid re-crawling.

Bing Webmaster Tools

• Log in with a Microsoft account to add your site and verify ownership via DNS or by importing from Google Search Console.

• Obtain an IndexNow key and submit newly created or updated pages immediately to speed up international exposure.

Brave Search

• Brave Search uses its own index and has no official submission form; participation in the Brave browser's Web Discovery Project can speed indexing.

• Re-check that robots.txt or noindex isn't blocking crawlers and meet basic exposure conditions.

• Introducing your content to the Brave user community can increase direct visits and naturally build indexing signals.

Yandex Webmaster

• Log in with a Yandex ID to add your site and verify ownership via an HTML file, meta tag, or DNS TXT record.

• It may take time for the site to appear in search, so regularly check indexing reports and error notifications.

• If you have Russian-language pages, set the region to Russia or CIS countries and consider additional tools like Turbo Pages and Yandex Metrica integration.

Baidu Search Resource Platform

• If targeting China, register your site at Baidu Search Resource Platform (ziyuan.baidu.com) and verify ownership.

• After verification, use link submission, sitemaps, and fast collection tools to actively notify frequently updated pages.

• If you have mobile-specific pages, register PC-mobile mapping and regularly check fast-crawling policy notices.

Adding JSON-LD Structured Data Easily

• JSON-LD tells search engines "what topic this page covers." Insert it once inside the <head>.

• Use inLanguage or @language fields to specify the page language so search engines detect it immediately.

• Choose a schema type that matches the page. Use Article for informative posts, Product for product pages, and FAQPage for FAQs.

• If the same product or service is presented in multiple languages, fill alternateName, description, etc., in each language and keep each language URL and @id unique.

• Use ISO 8601 for dates (e.g., 2025-09-26) and ISO 4217 currency codes for prices (e.g., KRW).

• For SPA architectures, ensure structured data is not lost when navigating and update the script on client render.

Accommodation JSON-LD Example

• The example below is a basic skeleton; replace the name, address, and review values with actual data as appropriate.

{ "url": "https://haniseoul.com/pages/seoul-mapo-haniseoul-house", "name": "Haniseoul House", "@type": "Accommodation", "image": [ "https://cdn.haniseoul.com/pages/7bfc2d4f-7248-43af-a2b4-d590eddd4c70/a058769c-2a34-476a-ad16-d0f0508f59cd.avif" ], "address": { "@type": "PostalAddress", "addressRegion": "Seoul", "streetAddress": "Hongik-ro", "addressCountry": "KR", "addressLocality": "Mapo-gu" }, "@context": "https://schema.org", "telephone": "+82-2-0000-0000", "priceRange": "$$", "description": "We offer a variety of options ranging from private studios with guaranteed privacy to shared houses where you can enjoy community living. All locations are near subway stations for convenient transportation and come fully furnished with high-speed internet so you can move in and start living right away.", "amenityFeature": [ { "name": "Free WiFi", "@type": "LocationFeatureSpecification" }, { "name": "Fully Furnished", "@type": "LocationFeatureSpecification" }, { "name": "Shared Kitchen", "@type": "LocationFeatureSpecification" } ] }

Multilingual Content Management Tips

• Store translation files in language-specific folders in version control so change history is easy to track. Use build scripts to automatically detect missing keys.

• Include checks in your QA checklist for date formats, currency, addresses, and culturally sensitive expressions.

• If fonts differ by language, split webfont subsets to reduce unnecessary size, and explicitly set language and direction attributes like <html lang="ko" dir="ltr">.