janvier 3, 2016
obtenue depuis www.lequateur.fr
qui renvoie vers lequateur.fr
janvier 3, 2016
<meta name= »google-site-verification » content= »iZe-tLBwRUNIYo6Giq4gm5qUhcMhrRfFmFZ6tJUhe0Q » />
Now go to Settings » Insert Headers and Footers and paste the meta tag line into the header field. Save your changes and go back to Google Webmaster tools website and click on Verify site button.
Alternately if you are using WordPress SEO plugin, then you can copy the verification key in content part of the meta tag and paste it in WordPress SEO plugin. Click on SEO in your WordPress admin sidebar and then scroll down to webmaster tools section to paste the unique key in the Google Webmaster Tools field. Save your changes and go back to Google Webmaster tools website to verify your website.
What is Google Webmaster Tools
Google’s Webmaster tools is a set of tools offered by Google to give publishers a look at how their website is seen by the search engine. It provides reports and data that can help you understand how different pages on your website are appearing in search results. It shows you the search queries where a page from your website appears in the results and how often it is clicked. This data can help you improve your older articles, write new content, and formulate a content strategy for your website. Google webmaster tools also allows you to submit XML sitemap of your website, exclude URLs, and help Google display the most important content of your website. It also notifies you if there is a problem with your site which is stopping Google from crawling and indexing your pages.
janvier 3, 2016
Use hreflang for language and regional URLs
Many websites serve users from around the world with content translated or targeted to users in a certain region. Google uses the
rel="alternate" hreflang="x" attributes to serve the correct language or regional URL in Search results.
Using language annotations
Imagine you have an English language page hosted at
http://www.example.com/, with a Spanish alternative at
http://es.example.com/. You can indicate to Google that the Spanish URL is the Spanish-language equivalent of the English page in one of three ways:
- HTML link element in header. In the HTML
<head>section of http://www.example.com/, add a
linkelement pointing to the Spanish version of that webpage at http://es.example.com/, like this:
<link rel="alternate" hreflang="es" href="http://es.example.com/" />
- HTTP header. If you publish non-HTML files (like PDFs), you can use an HTTP header to indicate a different language version of a URL:
Link: <http://es.example.com/>; rel="alternate"; hreflang="es"
To specify multiple hreflang values in a Link HTTP header, separate the values with commas like so:
Link: <http://es.example.com/>; rel="alternate"; hreflang="es",<http://de.example.com/>; rel="alternate"; hreflang="de"
- Sitemap. Instead of using markup, you can submit language version information in a Sitemap.
If you have multiple language versions of a URL, each language page must identify all language versions, including itself. For example, if your site provides content in French, English, and Spanish, the Spanish version must include a
rel="alternate" hreflang="x" link for itself in addition to links to the French and English versions. Similarly, the English and French versions must each include the same references to the French, English, and Spanish versions.
You can specify multi-language URLs in the same domain as a given URL, or use URLs from a different domain.
It’s a good idea to provide a generic URL for geographically unspecified users if you have several alternate URLs targeted at users with the same language, but in different locales. For example, you may have specific URLs for English speakers in Ireland (
en-ie), Canada (
en-ca), and Australia (
en-au), but want all other English speakers to see your generic English (
en) page, and everyone else to see the homepage. In this case you should specify the generic English-language (
en) page for searchers in, say, the UK. You can annotate this cluster of pages using aSitemap file or using HTML link tags like this:
<link rel="alternate" href="http://example.com/en-ie" hreflang="en-ie" />
<link rel="alternate" href="http://example.com/en-ca" hreflang="en-ca" />
<link rel="alternate" href="http://example.com/en-au" hreflang="en-au" />
<link rel="alternate" href="http://example.com/en" hreflang="en" />
For language/country selectors or auto-redirecting homepages, you should add an annotation for the hreflang value « x-default » as well:
<link rel="alternate" href="http://example.com/" hreflang="x-default" />
Supported language values
de: German content, independent of region
en-GB: English content, for GB users
de-ES: German content, for users in Spain
Do not specify a country code by itself! Google does not automatically derive the language from the country code. You can specify a language code by itself if you want to simplify your tagging. Adding the country code after the language to restrict the page to a specific region. Examples:
be: Belarusian language, independent of region (not Belgium French)
nl-be: Dutch for Belgium
fr-be: French for Belgium
For language script variations, the proper script is derived from the country. For example, when using zh-TW for users
zh-TW, the language script is automatically derived (in this example: Chinese-Traditional). You can also specify the script itself explicitly using ISO 15924, like this:
zh-Hant: Chinese (Traditional)
zh-Hans: Chinese (Simplified)
Alternatively, you can also specify a combination of script and region—for example, use
zh-Hans-TW to specify Chinese (Simplified) for Taiwanese users.
Finally, the reserved value « x-default » is used for indicating language selectors/redirectors which are not specific to one language or region, e.g. your homepage showing a clickable map of the world.
Important: Make sure that your provided
hreflang value is actually valid. Take special care in regard to the two most common mistakes:
- Missing confirmation links: If page A links to page B, page B must link back to page A. If this is not the case for all pages that use hreflang annotations, those annotations may be ignored or not interpreted correctly.
- Incorrect language codes: Make sure that all language codes you use identify the language (in ISO 639-1 format) and optionally the region (in ISO 3166-1 Alpha 2 format) of an alternate URL. Specifying the region alone is not valid.
- Module 1: Make a great site
- Module 2: Learn how Google understands your site
- Module 3: Use our resources