Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author John Clause

    (@johnclause)

    I knew about this line and was not sure, thought it does not hurt to keep it. Are you sure it is absolutely useless now in all browsers?

    Thread Starter jjbte

    (@jjbte)

    I don’t know about all browsers (past and current), but I think declaring the language in the html tag is sufficient, and it is the suggested method from W3C for declaring a site’s language.

    Plus you have the hreflang tags declaring the other available languages for any given page. On a side note, I just read a Google article stating a page should have hreflang tags for all languages, including the current language. This seems counter-intuitive to me because of the included rel=”alternate” portion of the hreflang tag. How can a page be an “alternate” to itself? I guess the point is to list ALL available languages for a page, regardless of which one is currently active.

    Plugin Author John Clause

    (@johnclause)

    I updated the code in 3.0 with this suggestions. Thank you very much.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Removing Content-Language tag’ is closed to new replies.