[wp-meta] [Making WordPress.org] #5108: Hreflang on the WordPress.org homepage

[Making WordPress.org]

#5108: Hreflang on the WordPress.org homepage
--------------------------------+--------------------
 Reporter:  bradleyt            |      Owner:  (none)
     Type:  enhancement         |     Status:  new
 Priority:  normal              |  Milestone:
Component:  WordPress.org Site  |   Keywords:  seo
--------------------------------+--------------------
 On most of the WordPress.org network, the hreflang configuration seems
 reasonably well setup. However, I have noticed this is not true of the
 wordpress.org homepage (not Rosetta homepages), where I have spotted
 various issues:

  - The list of sites do not match those shown in the hreflang of Rosetta
 sites. e.g.:
 Wordpress.org homepage lists https://ak.wordpress.org/ but not
 https://af.wordpress.org/
 The Rosetta sites list https://af.wordpress.org/ but not
 https://ak.wordpress.org/

  - The made up "emoji" language is shown on the homepage.

  - The WordPress.org homepage has no x-default hreflag. This should point
 to itself (i.e. https://wordpress.org)

  - The WordPress.org homepage incorrectly uses 3-letter character codes
 such as "bel" and "dzo". Hreflang languages need to be specified as a
 2-digit  ISO 639-1 code, with optional region, and on other parts of .org
 "bel" is mapped to "be-by" and "dzo" to "dz-bt". There are other examples
 of three letter codes in use, but I've just picked out a couple of
 examples.

 It seems that the hreflang logic is reimplemented for different parts of
 the .org network (Homepage, Rosetta, themes, plugins). Is there a reason
 why a central plugin cannot handle hreflang across the network? There are
 other improvements which could be made to the hreflang setup across the
 .org sites, but without a consistent implementation any fixes are going to
 have limited benefit.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5108>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org