{"id":224,"date":"2026-07-11T21:55:02","date_gmt":"2026-07-11T12:55:02","guid":{"rendered":"https:\/\/www.studio-jt.co.kr\/seo-glossary\/hreflang\/"},"modified":"2026-11-15T18:46:50","modified_gmt":"2026-11-15T09:46:50","slug":"hreflang","status":"publish","type":"seo_glossary","link":"https:\/\/www.studio-jt.co.kr\/en\/seo-glossary\/hreflang\/","title":{"rendered":"hreflang"},"content":{"rendered":"<h2 class=\"wp-block-heading\">Definition and how it works<\/h2>\n<p class=\"wp-block-paragraph\">hreflang is an HTML attribute that tells search engines which language and region each URL on a multilingual or multi-regional site is meant for. Google\u2019s Localized Versions documentation says that if you have multiple language or regional versions of the same page, you should tell Google about them, because doing so helps Google Search point users to the most appropriate version for their language or region. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/specialty\/international\/localized-versions\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> The key requirement is a two-way declaration in which, for example, the Korean page and the English page reference each other.<\/p>\n<p class=\"wp-block-paragraph\">The reason this attribute is needed lies in how Google detects language. Google\u2019s documentation on managing multi-regional and multilingual sites states clearly that to determine a page\u2019s language, Google uses only the visible content, not code-level information such as the lang attribute or the URL. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/specialty\/international\/managing-multi-regional-sites\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> Content alone doesn\u2019t convey \u201cwhich users should see this version,\u201d and hreflang fills that gap.<\/p>\n<h2 class=\"wp-block-heading\">Why it matters<\/h2>\n<p class=\"wp-block-paragraph\">Implemented correctly, it sends Korean and English visitors to their own language versions accurately, but in practice this attribute is notoriously tricky. Google\u2019s John Mueller said: &#8220;hreflang is one of the most complex aspects of SEO. It looks easy like a meta tag, but it gets really hard quickly.&#8221; <a class=\"jt-src jt-src--official\" href=\"https:\/\/www.seroundtable.com\/google-hreflang-complex-seo-25261.html\" target=\"_blank\" rel=\"noopener\">Google (Mueller)<\/a> The Ahrefs guide explains that hreflang is a signal, not a directive, so Google may show a different version even when it is implemented perfectly. <a class=\"jt-src jt-src--data\" href=\"https:\/\/ahrefs.com\/blog\/hreflang-tags\/\" target=\"_blank\" rel=\"noopener\">Ahrefs (data)<\/a> So the benefit of accurate implementation is not higher rankings but fewer wrong-version results and duplicate judgments.<\/p>\n<p class=\"wp-block-paragraph\">The relationship with duplicate detection is also worth noting. Google says language versions are treated as duplicates only when the main content remains in the same language. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/consolidate-duplicate-urls\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> This applies to cases like US and UK English pages whose content is essentially the same, and the multi-regional documentation recommends using canonical tags and hreflang together in that case so the right version is shown to searchers. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/specialty\/international\/managing-multi-regional-sites\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n<h2 class=\"wp-block-heading\">How to write it<\/h2>\n<p class=\"wp-block-paragraph\">According to Google\u2019s documentation, the first code in an hreflang value is an ISO 639-1 language code (ko, en), optionally followed by an ISO 3166-1 Alpha 2 region code to narrow the target (en-US, en-GB). The same document states that specifying a country code alone is not valid, and that Google does not infer the language from a country code. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/specialty\/international\/localized-versions\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> There are three rules to follow: each language version must list every version, including itself; use fully qualified URLs that include the protocol (https); and specify x-default for users whose language doesn\u2019t match any version.<\/p>\n<pre class=\"wp-block-code\"><code>&lt;link rel=\"alternate\" hreflang=\"ko\" href=\"https:\/\/example.com\/\" \/&gt;\n&lt;link rel=\"alternate\" hreflang=\"en\" href=\"https:\/\/example.com\/en\/\" \/&gt;\n&lt;link rel=\"alternate\" hreflang=\"x-default\" href=\"https:\/\/example.com\/en\/\" \/&gt;<\/code><\/pre>\n<p class=\"wp-block-paragraph\">Put this same set in the head of both the Korean page and the English page. Google\u2019s documentation recommends x-default as the fallback page to show when a user\u2019s language settings don\u2019t match any version. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/specialty\/international\/localized-versions\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> The 2013 Google Search Central Blog post that introduced this value also gave the example of designating a homepage with a country selector as x-default, and noted that Google and Yandex supported the annotation at the time. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/blog\/2013\/04\/x-default-hreflang-for-international-pages\" target=\"_blank\" rel=\"noopener\">Google Blog<\/a> Choose one of three implementation locations; Google\u2019s documentation says all three are equivalent from Google\u2019s perspective, so pick whichever is most convenient for your site. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/specialty\/international\/managing-multi-regional-sites\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n<figure class=\"wp-block-table\"><table><thead><tr><th>Implementation location<\/th><th>Method<\/th><th>Google\u2019s guidance<\/th><\/tr><\/thead><tbody><tr><td>HTML head<\/td><td>&lt;link rel=&#8221;alternate&#8221;&gt; tag<\/td><td>Use when you can\u2019t configure the sitemap or HTTP response headers<\/td><\/tr><tr><td>HTTP header<\/td><td>Specify hreflang in the Link response header<\/td><td>Useful for non-HTML files such as PDFs<\/td><\/tr><tr><td>XML sitemap<\/td><td>Add an xhtml:link element for each URL entry<\/td><td>Declare everything in bulk in the sitemap without changing page markup<\/td><\/tr><\/tbody><\/table><\/figure>\n<h2 class=\"wp-block-heading\">Practical checkpoints from an agency\u2019s perspective<\/h2>\n<p class=\"wp-block-paragraph\">WordPress does not output hreflang by default. Multilingual plugins such as WPML and Polylang output it automatically, but with custom themes you often have to output it yourself via the wp_head hook. Either way, the basic step is to open the final rendered HTML source and check the actual output.<\/p>\n<ul class=\"wp-block-list\"><li>The URLs hreflang points to must match the canonical URLs specified by the <a href=\"\/en\/seo-glossary\/canonical-tag\/\">canonical tag<\/a>. Google\u2019s documentation on consolidating duplicate URLs advises specifying a canonical page in the same language when using hreflang <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/consolidate-duplicate-urls\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a>, and the Ahrefs guide warns that if an hreflang target is canonicalized to a different URL, the two signals conflict. <a class=\"jt-src jt-src--data\" href=\"https:\/\/ahrefs.com\/blog\/hreflang-tags\/\" target=\"_blank\" rel=\"noopener\">Ahrefs (data)<\/a><\/li><li>Each language version must be in a state search engines can <a href=\"\/en\/seo-glossary\/crawling-indexing\/\">crawl and index<\/a> normally, and the Ahrefs guide states explicitly not to put noindex on hreflang target pages. <a class=\"jt-src jt-src--data\" href=\"https:\/\/ahrefs.com\/blog\/hreflang-tags\/\" target=\"_blank\" rel=\"noopener\">Ahrefs (data)<\/a><\/li><li>Because Google\u2019s documentation requires absolute URLs, check that domains are replaced at deployment so the staging domain doesn\u2019t remain in hreflang when you deploy to the live server. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/specialty\/international\/localized-versions\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/li><li>As language versions grow, each page needs as many tags as there are versions. Since Google\u2019s documentation treats the three implementation methods as equivalent, you can move to the XML sitemap method and manage everything in one place. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/specialty\/international\/managing-multi-regional-sites\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/li><\/ul>\n<h2 class=\"wp-block-heading\">Common mistakes<\/h2>\n<p class=\"wp-block-paragraph\">The most common mistake is missing return links. Google\u2019s Localized Versions documentation states that if two pages don\u2019t point to each other, the tags are ignored, explaining that this prevents third-party sites from arbitrarily declaring themselves as alternate versions. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/specialty\/international\/localized-versions\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> In a 2017 Semrush study of 20,000 multilingual websites, 58% had hreflang conflicts in their page source code, and 96% of the pages with conflicts lacked a self-referencing hreflang. <a class=\"jt-src jt-src--data\" href=\"https:\/\/www.semrush.com\/blog\/the-most-common-hreflang-mistakes-infographic\/\" target=\"_blank\" rel=\"noopener\">Semrush (study)<\/a><\/p>\n<ul class=\"wp-block-list\"><li>Wrong language codes &#8211; Korean is ko. kr is a country code, and according to Google\u2019s documentation, a country code alone is not valid. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/specialty\/international\/localized-versions\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> To also specify the region, write ko-KR. The ISO 3166-1 code for the United Kingdom is GB, so British English is en-GB; the Semrush study found that writing UK is a common country code mistake. <a class=\"jt-src jt-src--data\" href=\"https:\/\/www.semrush.com\/blog\/the-most-common-hreflang-mistakes-infographic\/\" target=\"_blank\" rel=\"noopener\">Semrush (study)<\/a><\/li><li>Using relative URLs &#8211; Google\u2019s documentation requires fully qualified URLs including the protocol, so relative paths like \/en\/ don\u2019t meet this requirement. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/specialty\/international\/localized-versions\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/li><li>Missing self-reference &#8211; Google\u2019s documentation states that each language version must list all language versions, including itself. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/specialty\/international\/localized-versions\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/li><li>Missing x-default &#8211; It\u2019s not required, but Google\u2019s documentation recommends specifying a fallback page for users whose language doesn\u2019t match. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/specialty\/international\/localized-versions\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/li><\/ul>\n<p class=\"wp-block-paragraph\">In short, hreflang is a signal, not a mandatory rule, so Google may show a different version even if it\u2019s implemented perfectly. <a class=\"jt-src jt-src--data\" href=\"https:\/\/ahrefs.com\/blog\/hreflang-tags\/\" target=\"_blank\" rel=\"noopener\">Ahrefs (data)<\/a> That\u2019s why, as Google\u2019s multi-regional documentation recommends, the prerequisite is to provide each page\u2019s content and navigation consistently in a single language. <a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/specialty\/international\/managing-multi-regional-sites\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n<h2 class=\"wp-block-heading\">References<\/h2>\n<ul class=\"wp-block-list\"><li><a href=\"https:\/\/developers.google.com\/search\/docs\/specialty\/international\/localized-versions\" target=\"_blank\" rel=\"noopener\">Localized Versions of your Pages &#8211; Google Search Central<\/a><\/li><li><a href=\"https:\/\/developers.google.com\/search\/docs\/specialty\/international\/managing-multi-regional-sites\" target=\"_blank\" rel=\"noopener\">Managing Multi-regional and Multilingual Sites &#8211; Google Search Central<\/a><\/li><li><a href=\"https:\/\/developers.google.com\/search\/blog\/2013\/04\/x-default-hreflang-for-international-pages\" target=\"_blank\" rel=\"noopener\">Introducing x-default hreflang for international landing pages &#8211; Google Search Central Blog<\/a><\/li><li><a href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/consolidate-duplicate-urls\" target=\"_blank\" rel=\"noopener\">Consolidate Duplicate URLs with Canonicals &#8211; Google Search Central<\/a><\/li><li><a href=\"https:\/\/www.seroundtable.com\/google-hreflang-complex-seo-25261.html\" target=\"_blank\" rel=\"noopener\">Google: hreflang The Most Complex Aspect Of SEO (John Mueller, 2018) &#8211; Search Engine Roundtable<\/a><\/li><li><a href=\"https:\/\/ahrefs.com\/blog\/hreflang-tags\/\" target=\"_blank\" rel=\"noopener\">Hreflang: The Easy Guide for Beginners &#8211; Ahrefs<\/a><\/li><li><a href=\"https:\/\/www.semrush.com\/blog\/the-most-common-hreflang-mistakes-infographic\/\" target=\"_blank\" rel=\"noopener\">13 Most Common Hreflang Mistakes [Semrush Study, 2017] &#8211; Semrush<\/a><\/li><\/ul>","protected":false},"excerpt":{"rendered":"<p>hreflang (the hreflang attribute) is an HTML attribute that tells search engines which language and region each page on a multilingual or multi-regional site targets. Google Search Central documentation explains that declaring language and regional versions with hreflang helps Google Search show users the most appropriate version. The key requirement is a two-way declaration in which each version references the others.<\/p>\n","protected":false},"template":"","glossary_categories":[21],"class_list":["post-224","seo_glossary","type-seo_glossary","status-publish","hentry","glossary_categories-technical"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/224","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary"}],"about":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/types\/seo_glossary"}],"version-history":[{"count":1,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/224\/revisions"}],"predecessor-version":[{"id":2309,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/224\/revisions\/2309"}],"wp:attachment":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/media?parent=224"}],"wp:term":[{"taxonomy":"glossary_categories","embeddable":true,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/glossary_categories?post=224"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}