Our pages will probably load faster if we include Hreflang tags in the XML Sitemaps rather than in HTML, so that hreflangs do not need to be generated when a website URL is requested.
Success Criteria
[ ] Web pages do not contain hreflang tags
[ ] A sitemap is no more than 50MB (uncompressed) and contains fewer than 50,000 URLs
[ ] The language selection page at http://www.mozilla.org/ uses hreflang="x-default" and is grouped with the hreflang tags for the localized home pages
[ ] Each URL in a sitemap much include hreflang tags, and each URL's hreflang tags must list itself as well as all other language versions
[ ] Alternate URLs must be fully-qualified, including the transport method (http/https), so: https://example.com/foo, not //example.com/foo or /foo
[ ] All language-specific URLs should be targeted at a specific country, e.g. hreflang="en-ca" or hreflang="en-gb"
[ ] The hreflang tags should also include one URL for each language that is also geographically unspecified, e.g. hreflang="en" or hreflang="fr" (this is new feature in our hreflangs)
According to Google, “it's a good idea to also provide a catchall URL for geographically unspecified users of that language…It can be one of the specific pages, if you choose.”
Description
Our pages will probably load faster if we include Hreflang tags in the XML Sitemaps rather than in HTML, so that hreflangs do not need to be generated when a website URL is requested.
Success Criteria
hreflang="x-default"
and is grouped with the hreflang tags for the localized home pageshttps://example.com/foo
, not//example.com/foo
or/foo
hreflang="en-ca"
orhreflang="en-gb"
hreflang="en"
orhreflang="fr"
(this is new feature in our hreflangs)Example: