Are my language tags correct?
-
Hello,
I have a Spanish website for Spanish speaking people es.example.com. I also have example.com for all English speaking people across the world.
I want that users who go to google.es and search in English get our example.com site and others who search in Spanish on google.es get the Spanish site.
Should the tags be like this:
Or should we also have this tag aswell to specify? Otherwise we might only show the es.domain even for english queris? :
-
Both the hreflang looks correct if your site is targeting only :
- Spanish speaking users in Spain (hreflang="es-ES")
- English speaking users in Spain (hreflang="en-ES"
If you are targeting English speaking users no matter the country, then you should use the hreflang="en" and not "en-ES".
-
You can create an hreflang with codes "en-es", because "es" also is the iso code of Spain as country, so the hreflang "en-es" is English in Spain (albeit would be better writing en-ES, but Google is not caps sensitive from what I know).
Second... you don't need to use the hreflang in every page, only in the ones that really need it.
For instance, if a page is canonicalized to another, the best way to avoid potential hreflang implementation mistakes (for instance, for not using the canonical URLs in the hreflang annotations) is not implementing it at all... because for its same canonicalized nature.
-
Hi there!
Just to confirm (it was implied by the Google.es comment but international targeting was never specified) - are you looking to target Spanish speakers in Spain only? Or are you attempting to target Spanish speakers worldwide?
If you are looking to target Spanish speaks in Spain only, then yes, this would be correct.
If you are looking to target Spanish speakers globally, you would want the tag to be:
-
Hello!
yeap, those are correct.
And no, you should not create a hreflang tag with es-en. Remember that those tags must be in all pages, and have the self referential tag.Here a few resources to help you more:
Hreflang generator - Aleyda Solis International SEO - Moz Learning Center The Guide to International Website Expansion: Hreflang, ccTLDs, & More! - Moz Blog The International SEO Checklist - Moz BlogBest Luck!
GR.
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Should Schema.org Tags go on every page?
Happy Monday Moz World! I am just wondering what are some best practices when using Schema.org Tags. For Example, I have a client who provides multiple services and provides unique content on each webpage. The design of each of the webpagesare unique, and conveys information differently. My question is: If each page of a company's website has unique content that describes a service or product, could I essentially change the url & description of the Schema Tag so that each of my pages are indexable by relationship to that page's content? Thanks ahead of time for the great responses! B/R Will
Intermediate & Advanced SEO | | MarketingChimp100 -
Why does Moz recommend subdomains for language-specific websites?
In Moz's domain recommendations, they recommend subdirectories instead of subdomains (which agrees with my experience), but make an exception for language-specific websites: Since search engines keep different metrics for domains than they do subdomains, it is recommended that webmasters place link-worthy content like blogs in subfolders rather than subdomains. (i.e. www.example.com/blog/ rather than blog.example.com) The notable exceptions to this are language-specific websites. (i.e., en.example.com for the English version of the website). Why are language-specific websites excepted from this advice? Why are subdomains preferable for language-specific websites? Google's advice says subdirectories are fine for language-specific websites, and GSC allows geographic settings at the subdirectory level (which may or may not even be needed, since language-specific sites may not be geographic-specific), so I'm unsure why Moz would suggest using subdirectories in this case.
Intermediate & Advanced SEO | | AdamThompson0 -
Should the Title Tag and the H1 Tag not be the same or not anymore and can that be classed as over optimization?
Hi All, I am just evaluating my title tags, H1,H2's etc and wondered in light of the google algorithm changes over the last 12 months , we should look at more diversity as opposed to things possibly looking over optimized... Originally (18 months ago) my Title tags considered of 2/3 keyword phrases , then I reduced this to my keyword phrase | Brand Name but a majority of my H1's and H2's had the same keyword phrases. Historically this has served us very well and rankings for good but over the last 12 months, we were hit by panda, hummingbird etc...and which we are trying to recover from and from what I have read, the rules have changed with regards to good seo./ over optimized SEO. We have been writting unique content , making more of our links branded etc to sort things out from that perspective but on the page stuff is just as important so I would like to get this right. I am now thinking , that I may be getting penalized if my H1 and title's , H2 are the same ? and that they should be obviously related but different. H2's again , need to be related but not the same as either of the above. Is that how things should be these days ? from what I have read about this, most of the articles are not that recent so I don't what to do what is now redundant advice Any advice greatly appreciated. Thanks Pete
Intermediate & Advanced SEO | | PeteC120 -
Rel=prev/next and canonical tags on paginated pages?
Hi there, I'm using rel="prev" and rel="next" on paginated category pages. On 1st page I'm also setting a canonical tag, since that page happens to get hits to an URL with parameters. The site also uses mobile version of pages on a subdomain. Here's what markup the 1st desktop page has: Here's what markup the 2nd desktop page has: Here's what markup the 1st MOBILE page has: Here's what markup the 2nd MOBILE page has: Questions: 1. On desktop pages starting from page 2 to page X, if these pages get traffic to their versions with parameters, will I'll have duplicate issues or the canonical tag on 1st page makes me safe? 2. Should I use canonical tags on mobile pages starting from page 2 to page X? Are there any better solutions of avoiding duplicate content issues?
Intermediate & Advanced SEO | | poiseo1 -
How long until my correct url is in the serps?
We changed our website including urls. We setup 301 redirects for our pages. Some of the pages show up as the old url and some the new url. When does that change?
Intermediate & Advanced SEO | | EcommerceSite0 -
Canonical Meta Tag Best Practices
I've noticed that some website owners use canonical tags even when there may be no duplicate issues.For examplewww.examplesite.com has a canonical tag.......rel="canonical" href="http://www.examplesite.com/" />www.examplesite.com/bluewidget has a canonical tag.......rel="canonical" href="http://www.examplesite.com/bluewidget/" />Is this recommended or helpful to do this?
Intermediate & Advanced SEO | | webestate0 -
Is a separate title tags and description reqquired
is it a separate title tags and description for all pagination pages. We have common title tag and meta desciption of all pagination pages should we need to modify the same
Intermediate & Advanced SEO | | Modi0 -
What is the downside with having too long of a title tag?
With Google placing so much relevance on title tags, it seems to help if you mention local cities within your title tag. I'm wondering if the positive of having more keywords in a title tag outweighs the negative of having too long of one?
Intermediate & Advanced SEO | | TLSNET0