seo - HTML5: should hreflang always point to a direct translation? -
this practice place kind of links in head multilanguage sites:
<head> <link rel="alternate" hreflang="en" href="/en"> </head> but, according answer question semantic markup language switcher, language switcher should like:
<nav> <h1>translations of page</h1> <!-- omitted → usability question --> <ul> <li>english</li> <!-- 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've got few semantic markup questions according that:
are both of rules required seo? or, if i've got language switcher on site, links in
headnot needed anymore?let's i'm on page:
example.com/pl/kontakt. should translation links insidehead(ornav) point to:example.com/en/contact(direct translation), orexample.com/en(english mainpage)?what more specific situation:
example.com/pl/aktualnosci/id/101. 'aktualnosci' means news. can see not newses can translated every language. , hard predict perfect translation url, based on parameters. question is: should translationlink(ornav) point url:example.com/pl/artykul/id/101, when:- we not sure if resource translated?
- we don't know translation url?
- resource 100% not translated?
i hope question clear. put 1 more example: on page example.com/en/news/2015/03/02/stackoverflow-rules, and news not translated polish. mistake put:
<link rel="alternate" hreflang="pl" href="/pl/aktualnosci"> as translation? of course page not translation, example list of translated newses.
as me semantically mistake, not translation, ux side, great, because points nearest translated resource , make life easier user.
alternate+hreflang: link vs. a
semantically makes no difference 1 use. in both cases link links translation of page.
but it’s conceivable consumer (e.g., search engine) decides ignore alternate+hreflang on a elements, example because sites allow markup in user comments. it’s rare users edit head, might alternate+hreflang on link elements in head.
unless have strong reasons not this, provide both:
- a language switcher, human users, in
body(aelements) - translations links bots check
head(linkelements)
page vs. site
an alternate+hreflang link defined point translated document, not site.
pages not translated
if /pl/artykul/id/101 not translated other languages (or don’t know sure is, or don’t know url), don’t use alternate+hreflang.
and yes, wrong link translated parent page in case: /pl/aktualnosci not translation of /en/news/2015/03/02/stackoverflow-rules.
of course still provide such link usability reasons, should not use alternate+hreflang markup link.
Comments
Post a Comment