Which pages to put hreflang on?
-
Hi,
we are running a site which is a directory consisting of numbers of phone spammers. It contains descriptions, comments and so on. We are currently present in 9 countries. The websites all have the same structure, but, of course, the spam numbers in each country are different ones. If I want to tell Google that our website is available is several locations/languages, do I only put my hreflang tag on the start page then?
Thanks
Thomas -
Yup, that makes sense to me.
It's a bit of a grey area and an unusual case, but I think that this approach makes more sense - otherwise you're actively trying to stop people who aren't in the 'correct' country for a phone number to find/access that page.
-
Hey Jono,
Thanks for coming back to me about this. I guess, we understood the concept of hreflang wrong. As I understand it now, a page in English on our US website cleverdialer.com would have to have a corresponding page with the same content but in German on our German site cleverdialer.de. This is not the case, as the spam numbers usually are active in one country.
If this is so, the hreflang on our phone number pages would not make sense as we have websites with the same general structure for different countries but the content differs.
-
Hey Thomas,
Did you have a chance to think about this?
-
Hmm. This is potentially a little complex.
It sounds like what you're describing _isn't _a case for hreflang / internationalisation.
If I understand correctly, you have one website, which has information about (things in) different regions, but your website isn't explicitly targeting users in different regions?
Where does language come into this?
What happens if I'm a user in Spain, who's Google'd a phone number from Germany? What does the current experience look like (what pages might they see, in what language), and what's the optimal experience look like?
-
Hi Igor,
Thanks for your reply.
I still would have one more question: The only pages which are really identical are the start pages, so there is no problem in placing a hreflang tag there. All the detail pages with phone numbers I have are different for every country. Would it make sense putting a hreflang on every detail page pointing to the start page or would it be better just not to put a hreflang on these pages?
-
All "international" pages. Specify language and country for each page you want to be shown in different countries.
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
-
Hreflang implementation via sitemap - don’t need canonical tags?
Hi, Quick easy question here I hope! An international site has hreflang and canonical tags in page head sections and also hreflang in the sitemap so I can see one version needs removing. The head section versions are relative URLs and need updating so think we will keep the sitemap hreflangs instead. If the sitemap implementation is going to be used (sitemap auto-updates when changes are made to pages so seems easier to do this way) am I right in thinking No canonical tags are needed at all (and can safely be removed from head section too?). Pretty sure links included in sitemap are assumed to be canonicals, or any issues with this approach? Will be using x-default for the default language version of homepage too.
International SEO | | MMcCalden0 -
Hreflang alternate as single-hop 301 - is this actually a problem?
First, this is not a question about whether 301 redirects pass page rank. My question is that if your hreflang alternative page URL is a 301 redirect*, are there any downsides. In all cases with our situation, the 301 redirect is single-hop and working. Tools, such as SEMRush seem to flag this as a non-canonical hreflang error, but I'm not able to find any cases where Google has suggested a redirecting hreflang is a problem. I'd appreciate any information on this issue before we invest extra time on a large international site. *In Drupal, there are scenarios where it's all but impossible to avoid having a 301 redirect in your hreflang alternate URL without significant custom work.
International SEO | | scottclark0 -
GeoIP Redirects & hreflang
Hello, We believe we've had some issues with hreflang tags not remaining validated due to the implementation of geoIP redirects. Previously, if a user clicked a landing page on Google search that was not targeted for their territory, they would instantly be redirected to a sub path that targets their territory using geoIP redirects. We're planning to remove the initial geoIP redirects and have messaging that prompts the user to either stay on the page they've landed on, or be redirected to page that is right for their territory. However, if a user has selected to be redirected to a sub path that is targeted for their territory, they will have a cookie preference set for the IP location they've selected, and will continue to be redirected to their chosen sub path. My question is, will a crawler follow and trigger the geo preference cookie, which could potentially cause complexities in validating hreflang tags and ranking of content for the right market. Thanks.
International SEO | | SEONOW1230 -
Hreflang for bilingual website in the same region/location
Hi everyone, got a quick question concerning the hreflang tag. I have a website with 2 different language versions targeting to the same region(Reason: The area is bilingual however not everyone speaks the other language fluently) Question:
International SEO | | ennovators
Can I use hreflang in that case like: Many thanks in advance0 -
/en-us/ Outranking Root Domain and other hreflang errors
I'm working with a new site that has a few regional sites in subdirectories /en-us/, /en-au/, etc and just noticed that some of our interior pages (ourdomain.com/en-us/interior-page1/ ) are outranking the equivalent ourdomain.com/interior-page1. This only occurs in some SERPS while others correctly display the non-regional result. I was told we have hreflang tags implemented correctly in the meta information of each of our pages but have yet to research deeply. Should we even have a /en-us/ version when our root domain is the default version, in english, and targeted to US primarily? Any help would be appreciated as I am a little lost. Cheers, Andrew
International SEO | | AndyMitty0 -
Hreflang tag on every page?
Hello Moz Community, I'm working with a client who has translated their top 50 landing pages into Spanish. It's a large website and we don't have the resources to properly translate all pages at once, so we started with the top 50. We've already translated the content, title tags, URLs, etc. and the content will live in it's own /es-us/ directory. The client's website is set up in a way that all content follows a URL structure such as: https://www.example.com/en-us/. For Page A, it will live in English at: https://www.example.com/en-us/page-a For Page A, it will live in Spanish at https://www.example.com/es-us/page-a ("page-a" may vary since that part of the URL is translated) From my research in the Moz forums and Webmaster Support Console, I've written the following hreflang tags: /> For Page B, it will follow the same structure as Page A, and I wrote the corresponding hreflang tags the same way. My question is, do both of these tags need to be on both the Spanish and English version of the page? Or, would I put the "en-us" hreflang tag on the Spanish page and the "es-us" hreflang tag on the English page? I'm thinking that both hreflang tags should be on both the Spanish and English pages, but would love some clarification/confirmation from someone that has implemented this successfully before.
International SEO | | DigitalThirdCoast0 -
International hreflang - will this handle duplicate content?
The title says it all - if i have duplicate content on my US and UK website, will adding the hreflang tag help google figure out that they are duplicate for a reason and avoid any penalties?
International SEO | | ALLee1 -
Ranking well internationally, usage of hreflang, duplicate country content
I'm trying to wrap my head around various options when it comes to international SEO, specifically how to rank well in countries that share a language, and the risk of duplicate content in these cases. We have a chance to start from scratch because we're switching to a new e-commerce platform, and we were looking into using hreflang. Let's assume an example of a .com webshop that targets both Austria and Germany. One option is to include both language and region in the URL, and mark these as such using hreflang: webshop.com/de-de/german-language-content (with hreflang de-de)
International SEO | | DocdataCommerce
webshop.com/de-at/german-language-content (with hreflang de-at) Another option would be to only include the language in the URL, not the region, and let Google figure out the rest: webshop.com/de/german-language-content (with hreflang de) Which would be better? The risk of inserting a country, of course, is that you're introducing duplicate content, especially since for webshops there are usually only minor differences in content (pricing, currency, a word here and there). If hreflang is an effective means to make sure that visitors from each country get the correct URL from the search engines, I don't see any reason not to use this way. But if search engines get it wrong, users will end up in the wrong page and will have to switch country, which could result in conversion loss. Also, if you only use language in the URL, is it useful at all to use hreflang? Aren't engines perfectly able to recognize language already? I don't mention ccTLDs here because most of the time we're required to use a .com domain owned by our customer. But if we did, would that be much better? And would it still be useful to use hreflang then? webshop.de/german-language-content (with hreflang de-de)
webshop.at/german-language-content (with hreflang de-at) Michel Hendriks
Docdata Commerce0