Les nouveautés et Tutoriels de Votre Codeur | SEO | Création de site web | Création de logiciel

Seo Master present to you:
Your URLs provide an opportunity to let search engines and people know what your page is about. Conversely, if you don't pay attention to your URLs, they may provide no value for your site's SEO (search engine optimization) or for your human visitors, either. Badly designed URLs may even trip up search engines or make them think you're spammy.
  • Include a few important keywords in your URLs.

A keyword-infused URL can:
  • Help visitors see that the page they're on is really what they're looking for. Would you rather see example.com/blog/219058 or example.com/blog/cute-puppies? People will see your URL in search results, at the top of their web browser while they're on your page, and any place where they may save the URL for themselves - like in bookmarks, or an email.
  • Give search engines one more indication of what your page is about, and what queries it should rank for. A URL without keywords won't hurt you, but it's a missed opportunity. A competitor who's placed
    relevant keywords in his URLs may rank higher than you for those keywords.

  • Keep your URLs to fewer than 115 characters.
  • Research shows that people click on short URLs in search results twice as often as long ones. Shorter URLs are also easier to share on social sites like Twitter and StumbleUpon.
  • Long URLs can look like spam. As the URL gets longer, the ranking weight given to each word in the URL gets spread thin, and becomes less valuable for any specific word.
You can manually check the character count of all your URLs to make sure they're not too long. The AboutUs Site Report can do it automatically, and point out any URLs that are longer than 115 characters.
  • Don't use more than a few query parameters in your URLs.

In a URL, a ? or & indicates that a parameter (like id=1234) will follow.
Here's an example of an okay URL (the kind you use to track your marketing in Google Analytics) with 1 query parameter:
http://www.example.com/page?source=facebook
Bad URL with too many query parameters:
http://www.example.com/product?id=1234567&foo=abc123def&color=yellow&sort=price
Too many query parameters can cause search engine robots to enter a loop and keep crawling the same pages over and over again. You could end up with search engines failing to index some of your most important pages.
  • Use hyphens instead of underscores in your URLs.
Search engines see underscores as a character. This means that your keywords will be seen as a single long keyword, and you'll lose any SEO benefit they could have incurred. A hyphen, however, is seen as a space that separates words. Hyphens are better for SEO because they allow search engines to interpret your web page as relevant for more keyword phrases. That said, Wikipedia's links have underscores, and they seem to be doing okay in search results :-)
Also, people can't see underscores in a URL when the link is underlined, as many links on the Web are. So hyphens are friendlier for people, and make your site more usable.
So... example.com/adorable-kitten-pics is better than example.com/adorable_kitten_pics
  • Keep all of your important content less than 3 subfolders deep.
A subfolder is a folder that is visible in a URL between two slashes. For example, in http://www.example.com/articles/name-of-page, articles is a subfolder and name-of-page is an article in that subfolder.
When it comes to subfolders, search engines assume that content living many folders away from the root domain (like example.com) is less important. So it's best to organize all of your important content so each URL has no more than two subfolders.

Here's another way to think about it: Make sure your URLs have 3 or fewer slashes (/) after the domain name. Here is an example URL that is a web page that is two subfolders deep:
http://www.example.com/articles/foo/page-name.htm
Bonus: Using subfolders allows you to use "content drilldown" in Google Analytics to easily view data for all the pages in a given subfolder.
  • Don't have too many subdomains.

A subdomain, or directory, is something that comes before the domain name in a URL. For example: http://blog.example.com Technically speaking, www. is actually a subdomain.
Too many subdomains can cause problems for search engine optimization. For more information, read Multiple Subdomains: Classic SEO Mistake.

How to Change Your URLs



Ideally, you'd set up a search-friendly URL structure when you first create your website. Then it just works for you without having to lift another finger.

Even if your website is already built, you should be able to change your URL structure - but it could be a pain in the neck. Most content management systems (CMS) allow you to change your default URL structure, or individual URLs for pages. You'll need to find that setting or option in your platform. If you use WordPress, see WordPress: Built for SEO for details on how to enable SEO-friendly URLs, or "permalinks," as WordPress calls them.

Warning! If you change existing URLs on your website, make sure to permanently redirect (using a 301 redirect) the old URL to the new one. You want to send people and search engines to the right place, not to a 404 error page. Keep in mind that while the 301 redirect will get people and search engine spiders to the right page, a small percentage of the PageRank or link juice from the linking page will be lost along the way.
Is it worth the effort to change your URLs? The above best practices for URLs can help your site's SEO, but as with other changes on your website, it's good to consider both the potential costs and benefits of the change. For example, the folks at SEOByTheSea.com know what they're doing, but opted to leave their URL structure as is - without keywords - because it would take a huge amount of work for a 6-year-old website with hundreds or thousands of pages to make the change. The site would also lose some link juice and PageRank due to so many redirects. In other words, there are tradeoffs.
Beyond changing the URLs on your website, you can sometimes change the URLs for your listings on other websites. For example, social sites like Facebook allow you to set a "vanity URL" to change a page with a URL like Facebook.com/pages/Company-Name/123456789 to Facebook.com/CompanyName. See 7 Simple Facebook Tricks for instructions. Keep an eye out for this option on other websites if you want to make it easier for people to find you there.







2013, By: Seo Master
salam every one, this is a topic from google web master centrale blog: Webmaster Level: Advanced

Update: This markup can now be used for multilingual and multi-regional content in general. More information.


If you have a global site containing pages where the:
  • template (i.e. side navigation, footer) is machine-translated into various languages,
  • main content remains unchanged, creating largely duplicate pages,
and sometimes search results direct users to the wrong language, we’d like to help you better target your international/multilingual audience through:

<link rel=”alternate” hreflang="a-different-language" href="http://url-of-the-different-language-page" />

As you know, when rel=”canonical” or a 301 response code is properly implemented, we become more precise in clustering information from duplicate URLs, such as consolidating their linking properties. Now, when rel=”alternate” hreflang=”x” is included in conjunction with rel=”canonical” or 301s, not only will our indexing and linking properties be more accurate, but we can better serve users the URL of their preferred language.

Sample configuration that’s prime for rel=”alternate” hreflang=”x”

How does this all work? Imagine that you’re the proud owner of example.com, a site called “The Network” where you allow users to create their very own profile. Let’s say Javier Lopez, a Spanish speaker, makes his page at http://es.example.com/javier-lopez:


Because you’re trying to target a multilingual audience, once Javier hits “Publish,” his profile becomes immediately available in other languages with the translated templates. Also, each of the new language versions is served on a separate URL.


Two localized versions, http://en.example.com/javier-lopez in English and http://fr.example.com/javier-lopez in French

Background on the old issue: duplicate content caused by language variations

The configuration above allowed visitors speaking different languages to more easily interpret the content, but for search engines it was slightly problematic: there are three URLs (English, French, and Spanish versions) for the same main content in Javier’s profile. Webmasters wanted to avoid duplicate content issues (such as PageRank dilution) from these multiple versions and still ensure that we would serve the appropriate version to the user.

A new solution for localized templates

First of all, just to be clear, the strategy we’re proposing isn’t appropriate for multilingual sites that completely translate each page’s content. We’re trying to specifically improve the situation where the template is localized but the main content of a page remains duplicate/identical across language/country variants.

Before we get into the specific steps, our prior advice remains applicable:
  • Have one URL associated with one piece of content. We recommend against using the same URL for multiple languages, such as serving both French and English versions on example.com/page.html based on user information (IP address, Accept-Language HTTP header).

  • When multiple languages are at play, it’s best to include the language or country indication in the URL, e.g., example.com/en/welcome.html and example.com/fr/accueil.html (which specify “en” and “fr”) rather than example.com/welcome.html and example.com/accueil.html (which don’t contain an explicit country/language specification). More suggestions can be found in our blog posts about designing localized URLs and multilingual sites.
For the new feature:
Step 1: Select the proper canonical.
The canonical designates the version of your content you’d like indexed and returned to users.
The first step towards making the right content indexable is to pick one canonical URL that best reflects the genuine locale of the page’s main content. In the example above, since Javier is a Spanish-speaking user and he created his profile on es.example.com, http://es.example.com/javier-lopez is the logical canonical. The title and snippet in all locales will be selected from the canonical URL.

Once you have the canonical URL picked out, you can either:
A. 301 (permanent redirect) from the language variants to the canonical

As an example, if a French speaker visits fr.example.com/javier-lopez (not the canonical), have this page include a cookie to remember the user's language preference of French. Then permanently redirect from fr.example.com/javier-lopez to the canonical at es.example.com/javier-lopez. Because of the cookie, es.example.com/javier-lopez will still render its boilerplate in French (even on the es.example.com subdomain!). Similarly, en.example.com/javier-lopez would set the value of this cookie to English and then 301 redirect to es.example.com/javier-lopez.

Including a language selection link is also helpful should a multilingual user prefer a different experience of your site.

B. Use rel=”canonical”

On the other language variants, include a link rel=”canonical” tag pointing to your chosen canonical. In our example, since the canonical for Javier’s profile is the Spanish version, the English and French pages (and optionally even the Spanish page itself) would include <link rel=”canonical” href="http://es.example.com/javier-lopez" />.

Cookies are not involved in this setup. Therefore, a French speaker will be served es.example.com/javier-lopez with a Spanish template. Implement step 2 if you want the French speakers to be served the French version at fr.example.com/javier-lopez in Google search results.
Step 2: In the canonical URL, specify the various language versions via the rel=”alternate” link tag, using its hreflang attribute.

rel=”alternate” URLs can be displayed in search results in accordance with a user’s language preference. The title and snippet, however, remain generated from the canonical URL (as is customary with rel=”canonical”), not from the content of any rel=”alternate”.
You can help Google display the correctly localized variant of your URL to our international users by adding the following tags to http://es.example.com/javier-lopez, the selected canonical:

<link rel=”alternate” hreflang="en" href="http://en.example.com/javier-lopez" />

<link rel=”alternate” hreflang="fr" href="http://fr.example.com/javier-lopez" />

rel=”alternate” indicates that the URL contains an alternate version located at the URI of the href value. hreflang identifies the language code of the alternate URL and can be specified with ISO-639.

Please note: If your site supports many languages and you’re worried about the increased file size when declaring numerous rel=”alternate” URLs, please see our Help Center article about configuring rel=”alternate” with file size constraints.
Once the steps are completed, the configuration on “The Network” would look like this:
  • http://en.example.com/javier-lopez
    either 301s with a language cookie or contains <link rel=”canonical” href=”http://es.example.com/javier-lopez” />
  • http://fr.example.com/javier-lopez
    either 301s with a language cookie or contains <link rel=”canonical” href=”http://es.example.com/javier-lopez” />
  • http://es.example.com/javier-lopez
    is the canonical and contains
    <link rel=”alternate” hreflang="en" href="http://en.example.com/javier-lopez" />
    and
    <link rel=”alternate” hreflang="fr" href="http://fr.example.com/javier-lopez" />

Results of the above implementation
  • When your content is returned in search results, users will likely see the URL that corresponds to their language preference, whether or not it’s the canonical. (Good news!) This is because with with rel=”canonical” or a 301 redirect, we can cluster the language variations with the canonical. With rel=”alternate” hreflang=”x” at serve-time we can deliver the URL of the most appropriate language to the user: English speakers will be served en.example.com/javier-lopez as the result for the URL in Javier’s profile, French speakers will see fr.example.com/javier-lopez, Spanish speakers will see es.example.com/javier-lopez.

  • By implementing step 1, only content from the canonical version will be available for users in search results (i.e. content from the duplicate versions won’t be searchable). Because the Spanish version es.example.com/javier-lopez is the canonical, queries that include template content from this page, e.g. [Javier Lopez familia] -- when using any language preference -- may return his profile (content from the canonical version). On the other hand, queries that include template content of the “duplicate” version, e.g. [Javier Lopez family], are less likely to return his profile page. If you would like the other language versions indexed separately and searchable, avoid using rel=”canonical” and rel=”alternate”.

  • Indexing properties, such as linking information, from the duplicate language variants will be consolidated with the canonical.

To recap (one more time, with feeling!)

For sites that have their template localized but the keep their pages’ main content untranslated:

Step 1: Once you have the canonical picked out you can use either rel=”canonical” or a 301 (permanent redirect) from the various localized pages to the canonical URL.

Step 2: On the canonical URL, specify the language-specific duplicated content with different boilerplate via the rel=”alternate” link tag, using its hreflang attribute. This way, Google can show the correctly-localized variant of your URLs to our international users.

We realize this can be a little complicated, so if you have questions, please ask in our webmaster forum!

this is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.com
Seo Master present to you:
Your website or blog is as good as the webhost that powers it. A web host is as important to your blog/website as an engine is for a vehicle. It usually is the factor that dictates whether your website can offer a predominantly positive or a lousy user experience. And if we’re not careful, we might fall for those web hosting companies that are only good at doing marketing stunts, but doesn’t focus on their service’s dependability at all. I’ll admit that in the beginning, I too fell victim to those hosts that offer domains for less than $5 a month. Over time though, I have smartened up. I finally realized that the errors and the frequency of slow loading time they’re causing my site is losing far more money than I’m saving.

If you’re currently on that dilemma, where you’re just starting to see how badly you’re mistaken in your selection. Then you have to add ‘seamless transition’ as one of the benefits of the web hosting company you’re going to switch to. On this infographic, you should consider other important factors you should be looking for in a web host.

How to Find a Reliable Web Hosting Partner. Some Important Web Hosting Checklist!




Author Bio:
Daniel A. Schultz love writing blogs, stories, poems and reading as well as collecting quotes & inspirational stuffs. He currently makes a living as an affiliate marketer where he spends most of his day telling people what is Amway review.
2013, By: Seo Master
Powered by Blogger.