International targeting
-
-
I submitted each language URL as a separated website to google webmasters,
-
I've submitted Hreflang sitemap which has language codes only(without countries codes)
-
each page in my website has hreflang language and country code.
Should i use international target option for each language to target the countries? will that hurt the language targeting? or I have to leave international targeting option unchecked for each language?
My Goal to target by languages, not countries.
-
-
You're welcome. You do not want to include hreflang="x-default" tags for the specific language pages (whether in the sitemap or the code). You only want to include the x-default tag on non-language specific 'default' pages (for example, a default page that prompts the user to select a language or country).
Here is a description from Google on their use of this particular tag: "The new x-default hreflang attribute value signals to our algorithms that this page doesn’t target any specific language or locale and is the default page when no other page is better suited." [Source]
-
Thanks for your reply, if choose to use hreflang Sitemap, Should i include X-default hreflang ?
-
If you are only targeting different languages (not targeting a specific region) you should not use the international targeting feature in Google Search Console. You also should not include country codes in the hreflang tags, you will want to remove those.
Also, it is best practice to only use hreflang tags OR an hreflang sitemap, it is not recommended that you use both due to redundancy [source].
"There is no need to use multiple methods for hreflang implementation. Google recommends against it, since it would be redundant. You certainly can use both methods, and there is no clear advantage of one method over the other. Here are some considerations for when you are deciding whether to use the xml sitemaps or page tagging methods:
- Hreflang xml sitemaps can be difficult to create and update. You can use online tools or create it in Excel, but it is difficult to automate the process. If you have xml sitemaps that your CMS updates for you automatically, it would be better to continue to use those rather than create separate, static hreflang xml sitemaps.
- Page tagging leads to code bloat, especially when you are targeting several countries/languages. That can mean an additional 10+ lines of code to each geo-targeted page.
- Some content management systems, such as WordPress and Drupal, offer automatic hreflang page tagging solutions."
https://www.semrush.com/blog/7-common-hreflang-mistakes-and-how-to-fix-them/
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
-
International SEO Two Subdomains Showing Up in Google Search Results
Hi I have a client that is having two subdomains showing up SERP when you Google their name. Here are the details. They have two subdomains us.companyname.com and en.companyname.com us.companyname.com is for the US and has completely different products and content than en.companyname.com en.companyname.com is the site designed for Europe and it is in English. How can I make it so that only the us. version shows up in the search results? Thanks in advance!
International SEO | | JohnWeb120 -
International SEO - Targeting US and UK markets
Hi folks, i have a client who is based in italy and they set up a site that sells travel experiences in the sout of Italy (the site currently sit on a server in Italy). The site has been set up as gTLDs: www.example.com They only want to target the US and the UK market to promote their travel experiences and the site has only the english version (the site does not currently offer an italian version). If they decide to go for the gTLDs and not actually change to a ccTLDs (which would be ideal from my point of view) how are the steps to be taken to set this up correctly on GSC? They currently only have one property registered on GSC: www.exapmple.com therefore i guess the next steps are: Add new property - www.example.com/uk and and set up geo targeting for UK Existing property - www.example.com/ set up geo targeting for US In case the client does not have the budget to optimise the content for american and british languages, would still make sense to have 2 separate property in GSC (example.com for US market and example.com/uk for UK market)? Few considerations: Add canonical tag to avoid duplicate content across the two versions of the site (in the event there is no budget to optimise the content for US and UK market)? Thank you all in advance for looking into this David
International SEO | | Davide19840 -
International Targeting for Australia Problem
Hello Moz Community! I'm reaching out since I recently launched a UK and Australia version of my website. Now, each page on the website has 4 versions: 1. www.example.com 2. www.example.com/au 3. www.example.com/uk 4. www.example.com/en <-- this is a by-product of the plugin we're using, CMS is WP each page has the following 4 targeting tags on it: I looked in Webmaster Tools and we're getting an error on what appears to be every Australia page. The error states, ""au"- unknown language code. URLs for your site that have an unknown language code 'au' and their alternate URLs." In Google's own example, they have the language for Australia set as en-au [https://support.google.com/webmasters/answer/189077?hl=en} Has anyone run into this issue before? We had the alternate tag set to "au" at first, but edited the plugin so the alternate tag now says "en-au", but this still hasn't remedied the problem. Any insights into resolving this error are greatly appreciated!
International SEO | | DigitalThirdCoast0 -
Include mobile and international versions of pages to sitemap or not?
My pages already have alternate and hreflang references to point to international and mobile versions of the content. If I add 5 language desktop versions and 5 language mobile versions as https://support.google.com/webmasters/answer/2620865?hl=en explains, my sitemap will get bulky. What are the pros and cons for referencing all page versions in sitemap and for include just general (English/Desktop) version in sitemap?
International SEO | | poiseo0 -
International Site - Language Targetting
Hi Mozzers, I am currently conducting a technical site audit on a large website. Their main content and audience is in the US, but they have started to add translated versions of the content in different languages (about 30 different languages). Also, they are not using cookies or scripts to auto-populate the language on the page, and the pages seem to be getting indexed just fine. Currently, they have their language distinguished by sub-folder (i.e. example.org/blog/by-language/spanish/), which I plan to 301 redirect to example.org/blog/es/ for each language. However, they are not implementing any sitemaps or hreflang header tags. I have not dealt with this in the past as all of my work has been done on smaller US sites, so I wanted to verify the steps I plan to take to ensure this is a solid approach. 301 redirect example.org/language/spanish/blog/ to example.org/es/blog/ Recommend adding hreflang markup into the header for each language. (They have a lot of pages, so they may not implement this if it is too much work.) Highly recommend adding XML sitemaps for each content version of the site using the media flow HREFLANG Siitemap Tool. Setting up multiple Webmaster Tools accounts and geotargetting them by language. I would also add the XML sitemap for each language. Is this a solid approach, given the information above? I want to make sure I am fundamentally sound on this before suggesting so many large changes. Thank you in advance for any thoughts / wisdom you can instill! ---------------------additional information--------------------- If I am hearing you correctly, I would only submit one XML Sitemap for international content. It would look something like the below image. I would only use one GWT account to upload the file, and I would not need to add any additional markup on each page, as it will be located in the hreflang xml sitemap. Finally, would it be a good or bad idea to 301 redirect their naming convention to a new, shorter one? example.org/by-language/spanish/blog/this-is-an-example --> example.org/es/blog/this-is-an-example bpXAYlr.png
International SEO | | J-Banz0 -
Website Internal Search
Hi I'm looking for ‘location search’ functionality to cover an extensive range of global locations to help increase the visibility I have been looking to use Google Places functionality, which has an extremely broad list of locations Would anyone have any experience in using Google places to power their websites internal search as well as if there is a cost to integrate it and other factors to be aware of? Thanks Simon
International SEO | | simonsw0 -
International (foreign language) URL's best practices
I'm curious if there is a benefit or best practice with regards to using the localized language on international sites (with specific ccTLDs). For example, should my french site (site.fr) use the french language as keywords within the URLs or should they be in english? e.g. www.site.fr/nourriture vs. www.site.fr/food Is that considered best practice for SEO (or just for brand perception those markets?). Is there a tangible loss in SEO if we do not use the correct language for those URLs and just stick with English around the world? I recall seeing a Matt Cutts video on the topic and he said that google does support i18n URL's but other SE's might not support them as gracefully but he didn't come down with a hard recommendation to go with i18n URL's or just English. Would love a strong ruling in favor one direction based on best practices.
International SEO | | mongillo0 -
International SEO - auto geo-targetting
I read with interest the recent post on international SEO and the top level domain architecture approaches to local content: http://www.seomoz.org/ugc/folders-vs-subdomains-vs-cctld-in-international-seo-an-overview#jtc135670 The issue I have is a little more complex: The business sells a wide variety of products (37) but one is by far and away the biggest and most popular. This means that due to the link profile of the various country sites and HQ site, search engines categorise the site according to this product (this is easily seen with the Google Adplanner) and the other product lines suffer as a result. The current architecture is to have a .com site and then individual ccTLD country sites, again with all products on each site. This creates an issue as in most countries the brand is not strong (compared to the keyword names and search volumes of the products) and so it is not that effective in generating organic traffic. The .com hogs much of the inbound links and the country sites themselves are not that well optimised for a number of reasons. A proposed solution has been to leverage the strength of the .com and the search volume for the product names, and to produce thematic sites based on each product: productA.brand.com
International SEO | | StevieCC
productB.brand.com
productC.brand.com In this way, the sites, content and link profiles are aligned around the more desirable products and we can expect improved organic search performance as a result (or at least ensure relevant traffic finds the relevant content fast). In terms of providing localised content, the plan was to use content mirroring and to then assign each content mirror to a specific geo-location using the webmaster tools console (and other SE equivilents). This is shown I think in one of Rand's videos. ProductA.brand.com/de/de Germany site for product A with unique German content
ProductA.brand.com/fr/fr French site for product A with unique French content This makes economic sense to me as to utilise the ccTLDs would result in hundreds of separate sites with all the licence and server considerations that entails. For example, for product A alone we would have to produce: productA.brand.de
productA.brand.fr
productA.brand.cn
productA.brand.jp
ect ect ect This just would not be sustainable in license/server costs alone across 37 products and 24 countries. However, I saw in a recent presentation at SES London that (auto) geo-targeting is risky, often doesn't work well for SEO and can even be seen as cloaking. I think the above strategy could still work, but perhaps we should avoid the use of auto-geotargetting altogether and hope the search engines alone do their job in getting users to the right content as we optimise the unique content for each country (and if they don't, ensure our desgn, UX and country selectors do the job instead). SEO guru consensus is to use the ccTLD if you own it, but as described above, in the real world that just isn't possible or practical given the company's strategic position. Which leads to the final question- we do own the brand ccTLDs- if they are directed back to the content mirror for the country on the .com, is there any SEO benefit in doing so aside from directing back any link juice associated with the domain)?0