Geek Answers Handbook

HTML5: should hreflang always point to direct translation?

It is good practice to place such links in multilingual sites:

<head>
    <link rel="alternate" hreflang="en" href="/en">
</head>

But, in accordance with the answer to the question Semantic markup for language switch , the language switch should look something like:

<nav>
  <h1>Translations of this page</h1> <!-- could be omitted → usability question -->
  <ul>
    <li>English</li> <!-- could be omitted → usability question -->
    <li><a rel="alternate" href="/pl" hreflang="pl" lang="pl">Polski</a></li>
    <li><a rel="alternate" href="/de" hreflang="de" lang="de">Deutsch</a></li>
  </ul>
</nav>

I have a few semantic markup questions according to this:

  • Are both rules required for SEO? Or, if I have a language switch on my site, are the links headno longer needed?

  • Let's say that I'm on the page: example.com/pl/kontakt. If the translation links inside head(or nav) indicate: example.com/en/contact(direct translation) or only example.com/en(main page in English)?

  • : example.com/pl/aktualnosci/id/101. "aktualnosci" . , . URL, . , , link ( nav) URL-: example.com/pl/artykul/id/101, :

    • , ?
    • URL ?
    • 100% ?

, . : - example.com/en/news/2015/03/02/stackoverflow-rules, , . :

<link rel="alternate" hreflang="pl" href="/pl/aktualnosci">

? , , , , .

, , , UX, , .

0
2

alternate + hreflang: link vs. a

, . .

, (, ) alternate + hreflang a, , . head, alternate + hreflang link head.

, :

  • , , body (a)
  • , head (link)

An alternate + hreflang , , .

/pl/artykul/id/101 ( , , URL), alternate + hreflang.

, : /pl/aktualnosci /en/news/2015/03/02/stackoverflow-rules.

, ​​ , alternate + hreflang .

+1
  • rel , , .
  • , (pl/kontakt → en/contact).
  • , (, ). URL- , URL- ( , , ).

UX, , , , , , , , ( ) . , , UX.

+1

More articles:


All Articles