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

salam every one, this is a topic from google web master centrale blog:
In 2006 we ramped up on international webmaster issues and particularly tried to support Eastern Europe. We opened several offices in the region, improved our algorithms with respect to these languages, and localized many of our products. Should I find only one word to describe these markets, I would say they are diverse. Still, they have two things in common: their online markets are currently in a developing phase and a high number of webmasters and search engine optimizers work there in a variety of languages. We are aware that a certain amount of webspam is generated in this region and we would like to reinforce that we have been working hard to take action on it both algorithmically and manually. Since I have seen some common phenomena in a bunch of these markets, here are a couple of suggestions for Eastern European webmasters and SEOs:
  • Avoid link exchanges. If a fellow webmaster approaches you with some sketchy offer, just refuse. Instead, work on the content of your site. Once you have the quality content, you can use the buzzing blogger community and social web services in your language to get nice linkbaits. Creating good content for your language community will pay off. Help the high-quality people in your language community and they will re-power you.
  • Use regional and geographical domains in line with their purpose. First, a sidenote for the Western webmasters: some Eastern European countries like Poland and Russia have so-called regional or geographical domains. Imagine that all the states in the U.S. had their official second level domain and if you wanted to open your webshop delivering to Kentucky, you could do it cheap or for free on eg. ky.us. This could help Google serve geographically relevant search results. In case you wish to sell organic soaps to people in Szczecin, do open your webshop on szczecin.pl. If you are from Kalmykia and would like to show the world the beauty of your area, go ahead and set up your Kalmyki travel site on kalmykia.ru. If you like a region, support it by hosting your site on the related regional or geographical domain. Be aware that webspam on these regional domains violates the correct use of them and prevents the development of your country's web culture.
  • Say no to Cybersquats! Sneaky registering of strong online brands with Belarusian, Estonian or Slovak top level domains is just bad. While it will not particularly help you boost the ranking of your site, cybersquatting often has created disappointed users and legal actions as side effects.
  • Think long-term. You have your share of responsibility for the development of your market. Creating quality sites that target users who search for highly specific content in your particular language will help you get your market into a more mature status -- and mature markets mean mature publisher revenue too.
this is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.com
salam every one, this is a topic from google web master centrale blog:
Webmaster Level: Intermediate to Advanced
Since launching Google Chrome last September, we received a number of questions from webmasters and web developers about how to make their sites look great in Google Chrome. The questions were very insightful and illuminating for the Chrome team, and I want to respond with a few helpful tips for making your site look stellar in Google Chrome.

Detecting Google Chrome

Most sites will render the same in both Safari and Google Chrome, because they're both WebKit-based browsers. If your site looks right in Safari, then it should look right in Google Chrome, too.

Since Chrome is relatively new, many sites have confused Google Chrome with another browser. If your site doesn't look quite right in Chrome but works fine in Safari, it's possible your site may just not recognize Chrome's user-agent string.

As platforms and browsers adopt WebKit as their rendering engine, your site can detect and support them automatically with the right JavaScript checks. Commonly, sites use JavaScript to 'sniff' the navigator.userAgent property for "Chrome" or "Safari", but you should use proper object detection if possible. In fact, Gmail has been detecting WebKit properly in Chrome since day one!

If you must detect the user-agent type, you can use this simple JavaScript to detect WebKit:

var isWebkit =
  navigator.userAgent.indexOf("AppleWebKit") > -1;


Or, if you want to check that the version of WebKit is at least a certain version—say, if you want to use a spiffy new WebKit feature:

var webkitVersion =
  parseFloat(navigator.userAgent.split("AppleWebKit/")[1]) ||
  undefined;
if (webkitVersion && webkitVersion > 500 ) {
  // use spiffy WebKit feature here
}


For reference, here are a few browser releases and the version of WebKit they shipped:

BrowserVersion of WebKit
Chrome 1.0525.19
Chrome 2.0 beta530.1
Safari 3.1525.19
Safari 3.2525.26.2
Safari 4.0 beta528.16


We do not recommend adding "Google" or "Apple" to your navigator.vendor checks to detect WebKit or Google Chrome, because this will not detect other WebKit or Chromium-based browsers!

You can find more information about detecting WebKit at webkit.org.

Other helpful tips
  • Google Chrome doesn't support ActiveX plug-ins, but does support NPAPI plug-ins. This means you can show plug-in content like Flash and Java in Google Chrome the same way you do with Firefox and Safari.
  • If text on your site looks a bit off, make sure you provide the proper content type and character encoding information in the HTTP response headers, or at the beginning of your pages, preferably near the top of the <head> section.
  • Don't put block elements inside inline elements.
Wrong:   <a><div>This will look wrong.</div></a>

Right:     <div><a>This will look right!</a></div>
  • If your JavaScript isn't working in Google Chrome, you can debug using Chrome's built-in JavaScript debugger, under the "page" menu -> 'Developer' -> 'Debug JavaScript' menu option.
To help webmasters and web developers find more answers, we created a support center and forum specifically to answer your questions. Of course, if you find something you think is really a bug in Chrome, please report it to us!

Help us improve Google Chrome!

If you'd like to help even more, we're looking for sites that may be interested in allowing Google to use their site as a benchmark for our internal compatibility and performance measurements. If you're interested in having Google Chrome development optimized against a cached version of your site, please contact us about details at chrome-webmasters@google.com.

Please keep the feedback coming, and we'll keep working to improve Google Chrome!

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:

In case you haven't seen the announcement on the Google Data API blog, there is a new API available for Google Finance Portfolios.

The Google Finance API makes it easy to create and access investment data for your users -- ranging from updating their investment holdings and watchlists to retrieving current portfolio value and performance. With your applications, users can monitor their portfolios and transactions and keep positions up-to-date and in-sync. If you have a great idea for a portfolio application, give the new API a try!2013, By: Seo Master
Powered by Blogger.