Hreflang:  Is it really still necessary and  how to use it successfully in 2023

#HREFLANGSUCCESS BY @ALEYDA FROM #ORAINTI
HREFLANG
Is it really still necessary and
how to use it successfully in 2023

Since long ago hreflang has been considered that
“necessary headache” when doing international SEO

But Google
deprecated the
GSC International
Targeting Report,
used to show
hreflang status &
give geolocation
feature! Is it really
necessary
nowadays?

Google says they still support hreflang while
dismissing the need for the geotargeting feature

This stance hasn’t changed since last year,
this tweet is from John just a few days ago

Because of this, I
asked for the
“official” hreflang
status back: Why not
show hreflang status
if it’s used? I didn’t
get an answer.

Also, do they really don’t need the geotargeting
feature anymore? What has changed? Let’s see…

Google added a note about hreflang used to identify
alternate content variations but not to detect language
Oct 2021 Now
vs

Google clarifies that to detect language,
they use their algorithms not hreflang
Oct 2021 Now
vs

Oct 2021 Now
The International Targeting info to geolocate gTLDs to a
country was eliminated from many sections too
vs

So maybe there’s no need for that feature bc of hreflang
and a better language understanding of BERT & MUM?

I’ve checked and G has become better at understanding
& targeting language versions to relevant markets
vs
vs
asana.com/es/
atlassian.com/fr/

What about country-targeted versions,
especially those w/ the same language tho?

eBay.com: Steady rankings for relevant US market while
drastic decrease since July 21 in non-relevant countries

Amazon.co.uk: Slight decrease for relevant UK market
while drastic decrease in non-relevant ones (US, CA)

Pinterest.es: Ups & Downs in relevant Spain market but
drastic decrease since July 21 in non-relevant ones

These sites are geolocating with ccTLDs though!
Let’s see gTLDs with subdirectories/subdomains

Samsung.com/es/: Steady rankings for Spain while
slight decreases in Argentina and a drastic drop in the US

Nike.com/gb/: Increased rankings for UK market while
slight decreases in Canada and a drop in France

uk.gymshark.com: Increased rankings for UK market
while mild decreases in AU and a drastic drop in France

Note how many of
the drastic decreases
in non-relevant
markets coincide
with Google Core
and Spam updates

So relevant
country targeting
has also improved
although not so
much for gTLDs as
for ccTLDs

Also, is better for
different
language markets
than for same
language ones

So yes, Hreflang is
still valuable to avoid
ranking in
non-relevant markets
by specifying
alternate pages,
especially when the
language is the same

X
But should be
executed with care
to avoid time-losing
mistakes, especially
now without the GSC
International Report

The hreflang challenge is caused by having to specify
pages lang/country & their alternates, & the same in each
https://www.site.com/en/
https://www.site.com/en-us/

Which can easily become chaotic for large Websites
with dozens of versions and a highly dynamic inventory

The reality is that most errors end up falling into
3 buckets that we should avoid at all costs
Featuring URLs in
hreflang that don’t
exist in certain
markets
Featuring
URLs that are not
indexable
(redirected,
noindexed,
canonicalized)
Generating
hreflang tags with
syntax or value
errors

1) Including as alternates pages that don’t exist in a market,
don’t make sense and would generate “no return” errors
<link rel="alternate" href="https://domain.com/us/page-a" hreflang="en-us" />
<link rel="alternate" href="https://domain.com/gb/page-a" hreflang="en-gb" />
<link rel="alternate" href="https://domain.com/au/page-a" hreflang="en-au" />
Page A for US
Page A for UK
Page A for AU
Page A doesn’t exist in
Australia, shouldn’t be
tagged as alternate
X
https://domain.com/us/page-a
https://domain.com/gb/page-a
https://domain.com/au/page-a

Page A for US
Page A for UK
Page A for AU
In Australia, Page A is redirected
to another URL, so that’s the one
that should be included instead
2) Including as alternates pages that exist but are not
indexable (redirected, noindexed, canonicalized URLs)
-
https://domain.com/au/page-a-new

Page A for US
Page A for UK
Page A for AU
<link rel="alternate" href="https://domain.com/au/page-a" hreflang=“en-au " />
There’s a space left after
the “en-au” value!
3) Including hreflang annotations with errors in syntax or
featured language or country values, careful with spaces!

This is why it’s fundamental to follow some do’s and dont’s
when implementing hreflang in your site pages

Don’t include
hreflang on pages
that don’t actually
need it, only do it in
those suffering from
overlay issues with
indexable alternates

This is the reason why large & dynamic sites, like
eCommerce, will tag categories but not/few products

If you’re using popular CMS like WP this can be done with
plugins (like WPML) automatically, but what if you’re not?
Adding a self-referring hreflang is
unnecessary if you don’t have alternates,
but at least won’t generate errors either

Semrush & Google Search Console
1. For your different
country Web versions:
Identify which pages
are getting traffic/
rankings from non-
relevant markets. Eg.
The pages from your
Spain version getting
traffic from Mexico
Which of these have a Mexican
indexable version that should be
getting this traffic instead?

2. Check which of
these pages getting
traffic from non-
relevant markets
have an indexable
alternate version in
the relevant ones
Check for alternate .co.uk URLS and check their
indexability and relevance, to verify they’re
really featuring the same content
.com URLs ranking in the UK
attracting the highest traffic
share

3. Select only those that are actual alternate pages in the
relevant market that are also indexable & create a sheet

4. Once you have all
of the pages with
international
misalignment issues
and indexable
alternates, identify
the relevant values
using Google
documentation
linking the ISO values
https://developers.google.com/search/docs/specialty/
international/localized-versions#language-codes

You can also get
them, as well as the
correct hreflang
tags patterns for
both HTML and
XML sitemap
implementation via
my free hreflang
tool
https://www.aleydasolis.com/english/international-seo-tools/hreflang-tags-generator/

Assign their relevant values
to each URL in the sheet

Careful when
trying to automate
hreflang
generation by
using GPTChat,
the values might
be incorrect
depending on the
prompt
Correct
Incorrect

Wait! But, should you use x-default too? Only if you want to
refer non-targeted users to a specific “fallback” page
https://developers.google.com/search/docs/specialty/
international/localized-versions#language-codes
For main
branded terms
Terms in the
same language

It’s ok to assign as an x-default a page that already
has its own language/country value as target too
<link rel="alternate" href="https://domain.com/us/page-b" hreflang="en-us" />
<link rel="alternate" href=“https://domain.com/us/page-b" hreflang="x-default" />
<link rel="alternate" href="https://domain.com/gb/page-b" hreflang="en-gb" />
<link rel="alternate" href=“https://domain.com/au/page-b" hreflang="en-au" />

It’s also ok to assign different values to the same URL
in general, as long as they make sense for its targeting
<link rel="alternate" href="https://domain.com/us/page-b" hreflang="en" />
<link rel="alternate" href="https://domain.com/gb/page-b" hreflang="en-gb" />

What doesn’t make sense and you shouldn’t do is
assign the same value to different URLs!
<link rel="alternate" href="https://domain.com/gb/page-b" hreflang=“en-us" />

5. Now it’s time to decide the method of hreflang
implementation, following this simple criteria
BETTER FOR SMALL
NUMBER OF VERSIONS
TO TAG AND WHEN
USING A PLATFORM
THAT ALLOWS TO EASILY
EDIT THE HTML HEAD
HTML Head
BETTER FOR BIGGER
SITES WITH A HIGH
NUMBER OF VERSIONS
(+3 VERSIONS OR +1K
PAGES) AND/OR WHEN
YOU CAN’T EDIT YOUR
HTML HEAD
XML Sitemap
WHEN SPECIFYING
HREFLANG FOR
NON-HTML
DOCUMENTS LIKE
PDFS, DOCS, ETC.
HTTP Header

BETTER FOR SMALL
NUMBER OF VERSIONS
TO TAG AND WHEN
USING A PLATFORM
THAT ALLOWS TO EASILY
EDIT THE HTML HEAD
HTML Head
BETTER FOR BIGGER
SITES WITH A HIGH
NUMBER OF VERSIONS
(+3 VERSIONS OR +1K
PAGES) AND/OR WHEN
YOU CAN’T EDIT YOUR
HTML HEAD
XML Sitemap
WHEN SPECIFYING
HREFLANG FOR
NON-HTML
DOCUMENTS LIKE
PDFS, DOCS, ETC.
HTTP Header
My preferred one, for flexibility, especially if there are no
dev resources, is the XML sitemap to tag static pages

For this, I like to use TechnicalSEO.com's XML sitemap
generator, that uses a CSV for which they give a template
https://technicalseo.com/tools/xml-sitemap/

You can replicate the template format by just adding the
loc for each URL included and lastmod in your own sheet

6. Export the sheet as a CSV and generate the
XML sitemap with the technicalseo.com generator

7. Validate if the XML sitemap is correctly generated by
using an SEO crawler supporting hreflang validation
Screaming Frog

8. Troubleshoot any remaining errors and once ready,
upload via the Google Search Console

9. Monitor that the tagged pages start ranking in their
relevant markets for their top targeted queries
Advanced Web Ranking

10. Profit! You should see the increase in traffic and
conversions in those markets from relevant audience
GSC & GA

● ccTLDs
● Country in metadata
● Country, Address and
Phone numbers in pages
copy
● Local language &
currency
● Backlinks from local sites
● Connected Business
Profile
● Hreflang specifying
alternates from stronger
same language country
version
Well aligned ccTLD Not Well aligned ccTLD
Finally, remember that good geolocation is a matter
of aligned signals not only hreflang, the more the better

Well aligned gTLDs
This is also true for subdirectories and subdomains too
● Country in metadata
● Country, Address and
Phone numbers in pages
copy
● Local language &
currency
● Backlinks from local sites
● Connected Business
Profile
● Hreflang specifying
alternates from stronger
same language country
version

#SEOReporting by @aleyda from @orainti
orainti.com
I’m Aleyda Solis
* SEO Consultant & Founder at Orainti
* SEO Speaker at +100 Events in +20 countries
* Author “SEO. Las Claves Esenciales.”
* Crawling Mondays Video & Podcast Series Host
* #SEOFOMO Newsletter Wrangler
* Maker LearningSEO.io
* European Search Personality of the Year in 2018
* remoters.net Co-Founder
Thanks

Hreflang:  Is it really still necessary and  how to use it successfully in 2023

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à Hreflang:  Is it really still necessary and  how to use it successfully in 2023

Similaire à Hreflang:  Is it really still necessary and  how to use it successfully in 2023 (20)

Plus de Aleyda Solís

Plus de Aleyda Solís (20)

Dernier

Dernier (20)