• Geotargeting within a domain

  • von: samcherry hinzugefuegt: 04-02-20
  • Combining several languages ??on one domain and addressing different countries with them is no easy task. It becomes a real challenge when you are let go of such a monster as SEO. In this article I would like to point out some of the most common mistakes and give tips for the correct use of sitemaps for geotargeting.

    1. Language via parameters

     

    A popular mistake is to deliver all languages ??under the same URL and only add one parameter at the end. Why is this a bad idea? Because something like this comes out:

    Search for google.com for site: upjers.com

    Search for google.com for site: upjers.com

    Search on google for site: upjers.com

    Search on google for site: upjers.com

    Swell:

    http://www.google.de/search?hl=de&q=site%3Aupjers.com

    http://www.google.com/search?hl=en&q=site%3Aupjers.com

    As you can see, both site queries already show pages in the other language on the first result page, although all pages are available in German and English. In addition, hits from subdomains in other languages ??are displayed. If you can't imagine this without it, you can introduce a www to the site query.

    The reason for these results lies in the clever possibility of changing the language:

    [a href = "? PHPSESSID = 25ab14539ccc7e6b36c583c6c281f2d1 & p = & lang = de"] German [/ a]
    [a href = "? PHPSESSID = 25ab14539ccc7e6b36c583c6c281f2d1 & p = & / = a]"

    The link texts are actually graphics. For the sake of clarity, I have shortened them to their old attributes.

    If you click on an internal link after changing the language, the & lang = de / en parameter is no longer appended to the URL. Of course, this is completely confusing and, together with the p parameter and the dynamic session ID, ensures that every crawler is confused here.

    By the way, you can also repeat the game with upjers.de. However, .com ranks better in both US and DE and is also used for AdWords ads.

    2. Speaking URL in the mother tongue

     

    The web developer was taught to use speaking URL and then he takes the same URL structure for all languages.

    Firstly, the American customer cannot do anything free on itunes and secondly he reads the words best, fax, tel (e) and (e) mail. However, best is not an abbreviation of order for him, but an adjective. Just as you can from email even mail read what happens to mean post and may give the impression that one can order here by letter. If you think that this is wrong, you should talk to operators of online shops. There are actually people who send a letter with an order. Sometimes even only to the uninvolved affiliate who linked the shop. But that's material for another story ...

    3. Global or no content language tag

     

    Placing the simple content language tag appropriately still seems to be an impossible task for many multilingual websites. Two mistakes are often made here.

    NO CONTENT LANGUAGE TAG AT ALL

    You just don't put a content language tag at all. What is not a problem for Google on monolingual pages with a suitable ccTLD can lead to problems on multilingual pages.

    GLOBAL LANGAUGE TAG

    Also very popular. The content language tag of the mother tongue is hard-coded in the template and is delivered in all language versions. This saves performance on dynamic pages with only one language, but can lead to massive problems in the case of multilingual pages.

    The second error in particular can lead to the fact that [Translate this page] appears in the search results despite the correct language version. The likelihood of this increases as soon as text is hidden in images, JavaScript and Flash.

    4. No geotargeting via sitemap

     

    It is well known that you can set up subdomains like independent domains in Google Webmaster Tools. It is often forgotten that this also applies to subfolders. Since the procedure for subdomains does not differ from that for domains, I will explain step by step how to proceed for subfolders.

    1. CONTENTS

    I have the domain example.com and deliver the German version at example.com/de/ and the Spanish version at example.com/es/.

    2. SITEMAPS

    I generate two sitemaps. The sitemap for the German-language content is located at example.com/de/sitemap-de.xml and the sitemap with the Spanish subpages is located at example.com/es/sitemap-es.xml.

    3. GWT ACCOUNTS

    Add subfolders in Google Webmaster Tools

    Add subfolders in Google Webmaster Tools

    Each language subfolder is entered and verified as a separate page in the GWT. If you have already verified for example.com, the verification for the subfolders does not apply.

    Checked subfolders in Google Webmaster Tools.

    Checked subfolders in Google Webmaster Tools.

    4. SUBMIT SITEMAPS

    Set up a sitemap in Google Webmaster Tools.

    Set up a sitemap in Google Webmaster Tools.

    At example.com/es/ we submit the sitemap example.com/es/sitemap-es.xml.

    5. GEOGRAPHIC TARGET

    Set the geographic target in Google Webmaster Tools.

    Set the geographic target in Google Webmaster Tools.

    Finally, the geographic destination for the folder is set.

    Steps 4 and 5 must of course be repeated for all folders. When we are through, we have set correct geographic targeting within a domain.

     

     

     

     

     

     

     

  • (0) (0 Votes)
  • Antwort   |   melden
  • blink    digg    furl    furl    furl    furl    deli    BlogMarks    Magnolia    StumbleUpon    RSS Subscribe
 

Powered Free by PHPmotion - Video Script