Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
Custom hreflang tags in WP & using with Yoast
-
Hi
My clients dev has added custom fields for adding hreflang tags to head of pages such as:
"Rel Type", "The URL", and "Language Code"
Am i right in thinking that until a different language/country version of the site is created these can remain empty or should they still be populated once added say with some sort of global reference or best left blank since will leave the head content global by default ?
Also how important is it to add charset to the language code ? since seems optional ?
Also this set up is on WP multi-site with Yoast and devs asked me the below:
_One thing to note is that Yoast generates its own "canonical" tags - so if _
_you are going to use hreflang tags and canonical tags then you don't need to _
_add a canonical using the custom fields I have set up - Yoast has that _
sorted._But if you are going down the route of NOT having any canonical tags - and _
_using a x-defult for the hreflang tags, I will need to try and suppress the _
_Yoast canonical tag so you can do this. Much depends on your approach and _
what you think is best.So how do i know if using canonicals or x-default, i take it best simplest to leverage Yoast and hence not add canonicals to custom fields ? Isnt x-default just for indicating language selectors/redirector not specific to 1 region? So long as havnt got those then good to proceed with Yoasts generated canonicals ?
Cheers
dan
-
Hello,
I have a Blog In Which I am Using Google Translate, Which Can Convert the Blog into Multilanguages. Is it Suggested to use Herflang Tags in My Blog. Thanks In Advance ( Blog I Have Mention is signature)
Ashish Sharma
-
Thanks again really is a big help
Ive read that correct charsets are important, i take it that plugin handles that correctly ?
Do you know if plugin should work fine in WP Multisite environment with network childs domain mapped with their cctlds ?
Re: "using x-default and removing the canonical is nonsense" The dev just meant if going down route of NOT using canonicals AND using x-default in the hreflang then would need to suppress Yoast in those instances.
Re: "In my example, I used two very similar (if not the same langs), however there are things that change, but those are minimal (take as an example a car "hood", in England a "bonnet"). As those are such minimal changes, I don't think a specific version for GB is needed if you are already serving a US version (that's up to you)." Would you say the same if phrases containing these regional variations (hood vs bonnet) were on your target kw list ? Since i find that whilst Google is getting better at semantic relationships between words i think that they do need to be specifically targeted/appear in content & meta data in order to rank for them, or at least increase chances of ranking for them.
Also re your final paragraph 'car repair centers' would be a logical target kw for such a page so i would have thought it would be beneficial to create 2 versions of this page, 1 for US targeting US spelling & 1 for UK targeting UK spelling (centers vs centres), rather than 1x English to serve both UK & US audiences
Also I would have thought it would be useless showing a list of US car repair centers to UK visitors ?
Sorry for more questions, think that should be it now & thanks again
All Best
Dan
-
Dan,
If you have an English page that is also available on Turkish (same content but rewritten/translated) then an hreflang tag is recommended, not mandatory, but recommended. Although as you said you are already writing in Turkish and geotargeting in GWT, there are other engines too, that regardless their market share, shouldn't be overlooked.
HOWEVER, if you have a page in English not matching a Turkish page, then you don't need the hreflang in that page. The tag is only used when the same content is available on other language/location to tell engines which version they should serve.
What you mention about using x-default and removing the canonical is nonsense. Those are 2 different things and one would not interfere with the other. The plugin I recommended does not mess with Yoast, leaving the canonicals as they should be and adding the hrefland tags as specifies. Check this example on my site English and Spanish using both Yoast and the hreflang Manager plugin:
- English: http://viberagency.com/blog/6-reasons-shouldnt-put-intern-charge-companys-social-media/
- Spanish: http://es.viberagency.com/blog/6-razones-por-las-que-debes-dejar-un-pasante-cargo-de-los-medios-sociales-de-tu-empresa/
Check the source code, both have their canonicals and hreflang tags just fine. We chose to use the English version as the default, as you can see in the x-default.
The hreflang tags should be used only when the content is the same (but targeted to a different audience). Of course of the translation from one language to the other some lines must be rewritten to make sense.
In my example, I used two very similar (if not the same langs), however there are things that change, but those are minimal (take as an example a car "hood", in England a "bonnet"). As those are such minimal changes, I don't think a specific version for GB is needed if you are already serving a US version (that's up to you). In that case (1 english version to all english speakers), you only specify the language, instead of the Language and Region:
<link rel="<a class="attribute-value">alternate</a>" href="http://www.example.com" hreflang="<a class="attribute-value">en</a>"/>
Now, just to make sure we have an example that DOES apply a different GEO in en-US and en-GB, could be a page that explains what are car repair centers, plus below it shows a list of repair centers. In these scenario, the content is the same, but the list of repair centers change, you would like to display those in GB to your GB audience (still, from my point of view, useless, but was just an example).
Hope that clears it up
-
Hi Apog
Thanks so much for all that great info !
First of all, the main default site is for general/global targeting so have instructed dev to put on network.domain.com/en (but mapped to tld domain.com) to signify english but not be country specific - global kw research has determined USA spelling to be used predominently with just one or two UK spelt target kw).
The next stage is a Turkish geotargeted site that will be in Turkish language on our WP MS network network.domain.com/tr but mapped with a tld such as www.domain.tr which will be geotargeted in GWT. Given these other geo signals such as gwt, native language in body copy etc is hreflang even needed for such a scenario or due to hreflang is overkill/not needed ?
Re your example (US/GB): You are saying use x-default but my dev says (copied in my question) that if we want to use x-default then would have to suppress Yoast re the canonical, so any ideas how to resolve that ? Does the plugin you linked to handle hreflang without requiring Yoast to be suppressed re having x-default or not applicable since only refers to scenario where not having canonicals.
Also you say your example set up is if the contents not exactly the same, do you mean if they have substantially different content ? And your second point (below the example set up) says if they have the same content - so here do you mean if the only difference is US/vsGB versions of english language/spelling but otherwise identical ? And if our target kw include the USvsGB spelling variations then i take it the en-gb version isnt expendable after all ?
Thanks for all your help and sorry for more questions but i really need to get to the bottom of this asap
Many Thanks
Dan
-
thanks Kristina !
-
Hey Dan,
If I understood correctly, you should use both. Canonical tags are used tell search engines that the content is located on the canonical content, while hreflang points which version should be served to each visitor depending on the user's location/language.
If you Yoast, then they already handle the canonical tags and there's nothing you need to do. For the hreflang, if you have at the moment only 1 version served to all visitors, then those shouldn't be used. However, if you have 2 versions quite similar, like en-US and en-GB then you will need to choose the one that's default, let's say the US version and have the following on each version:
en-US:
- Canonical pointing to it.
- Hreflang x-default pointing to it
- Hreflang en-US pointing to it
- Hreflang en-GB pointing to en-GB version
en-GB:
- Canonical pointing to it.
- Hreflang x-default pointing to en-US
- Hreflang en-US pointing to en-US
- Hreflang en-GB pointing to it
This applies if the en-US and en-GB versions are NOT exactly the same. If the language changes (that's why you create a specific version to each country) you need a canonical in each version pointing to itself.
If the en-US and en-GB have the same contents, then the canonical should point to the en-US version (but there's no need to have the en-GB version really, which makes it useless / expendable).
As you mention that at the moment you do not have any extra langs/regions, then you could leave the tags empty or better remove them.
There's a plugin for wordpress that handles hreflang tags (paid) hreflang Manager
Hope that helps!
-
No need to worry about hreflang (and therefore x-default) unless you're working with international versions of your sites! If Google doesn't see anything referencing international, it will figure out the language and country from the ccTLD and the language you're using on your site. Hreflang tells Google where the international versions of a page are, it isn't necessary to designate a language and location.
Best,
Kristina
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
-
Duplicate titles from hreflang variations
Hi, I am working on a large global site which has around 9 different language variations. We have setup the hreflang tags and referenced the corresponding content as follows: (We have not implemented a version X-default reference, as we felt it was not necessary) Using DeepCrawl and Search Console, we can see that these language variations are causing duplicate title issues. Many of them. My assumption was that the hreflang would have alleviated this issue and informed Google what is going on, however i wanted to see if anyone has any experience with this kind of thing before. It would be good to understand what the best practice approach is to deal with the problem. Is it even an issue at all, or just the tools being over-sensitive? Thank you in advance.
Technical SEO | | NickG-1230 -
Robots.txt in subfolders and hreflang issues
A client recently rolled out their UK business to the US. They decided to deploy with 2 WordPress installations: UK site - https://www.clientname.com/uk/ - robots.txt location: UK site - https://www.clientname.com/uk/robots.txt
Technical SEO | | lauralou82
US site - https://www.clientname.com/us/ - robots.txt location: UK site - https://www.clientname.com/us/robots.txt We've had various issues with /us/ pages being indexed in Google UK, and /uk/ pages being indexed in Google US. They have the following hreflang tags across all pages: We changed the x-default page to .com 2 weeks ago (we've tried both /uk/ and /us/ previously). Search Console says there are no hreflang tags at all. Additionally, we have a robots.txt file on each site which has a link to the corresponding sitemap files, but when viewing the robots.txt tester on Search Console, each property shows the robots.txt file for https://www.clientname.com only, even though when you actually navigate to this URL (https://www.clientname.com/robots.txt) you’ll get redirected to either https://www.clientname.com/uk/robots.txt or https://www.clientname.com/us/robots.txt depending on your location. Any suggestions how we can remove UK listings from Google US and vice versa?0 -
I am trying to generate GEO meta tag for my website where on one page there are multiple locations My question is, Can I add GEO tagging for every address?
Am I restricted to 1 geo tag per page or can i add multiple geo tags ?
Technical SEO | | lina_digital0 -
Yoast and wordpress duplicate meta
I'm using the Yoast plugin with wordpress and have noticed in my HTML I have duplicate meta data. For example my header starts with
Technical SEO | | simonatkinsphoto
<title>(title) </title<span><<br /><meta </span><span class="html-attribute-name">property</span><span>="</span><span class="html-attribute-value">og:site_name</span><span>" </span><span class="html-attribute-name">content</span><span>=<br /><span><meta </span><span class="html-attribute-name">property</span><span>="</span><span class="html-attribute-value">og:description</span><span>" </span><span class="html-attribute-name">content</span><span>=<br /><br /></span></span>Then I have the 'This site is optimised by Yoast" tagline followed by the same meta -<br /> <span><meta </span><span class="html-attribute-name">name</span><span>="</span><span class="html-attribute-value">description</span><span>" </span><span class="html-attribute-name">content=<br /><span> <meta </span><span class="html-attribute-name">property</span><span>="</span><span class="html-attribute-value">og:title</span><span>" content=<br /><span> <meta </span><span class="html-attribute-name">property</span><span>="</span><span class="html-attribute-value">og:description</span><span>" </span><span class="html-attribute-name">content=<br /><span> <meta </span><span class="html-attribute-name">property</span><span>="</span><span class="html-attribute-value">og:site_name</span><span>" </span><span class="html-attribute-name">content</span><span>=<br /><br /></span></span></span></span>Is this likely to cause problems with Google and is there a way to stop both wordpress and Yoast adding meta to the header. </p></title>0 -
Hiding h1 tags in Magento
Hi Moz Community, I know that hiding h1 tags isn't a good practice for SEO and google, but we have banners that look much nicer than the stock text Magento uses for its titles. The banners have the same text and the h1 is in the source code, just not visible on front end. The option Magento gives is "hide title on the page." So I'm not sure if this is actually the bad way to hide it or if it's fine for search engines. Thanks,
Technical SEO | | IceIcebaby
-Reed0 -
Special Characters in Title Tags & Meta Descriptions
Do special characters, such as the "&" symbol or a "," in title tags and meta descriptions negatively affect your ranking in search engines? Any feedback is much appreciated. Thank you!
Technical SEO | | ZAG1 -
H1 Tag as Logo on the Homepage.
So I was working on a Genesis theme website where they have the H1 Tag as the Logo on the homepage. I wanted this changed because I always use my H1 tag to include a keyword I want to rank for. I was told by the Genesis Forum Manager that Yoast said the Logo should be the H1 tag on the homepage. (Yoast has a WP SEO Plugin that is very popular) That makes no sense to me, so I was looking for Opinions. Thanks,
Technical SEO | | netviper0