MatrixAdapt | Logiciel de gestion d'Entreprise, Création et référencement des sites web

Seo Master present to you: ส่วนสาเหตุที่ต้องมีการจำกัด % ของ Keyword Density เนื่องจาก การที่หน้าเวบของคุณมีความหนาแน่นมากๆ เหล่า Search Engine จะเพ่งเล็งเว็บของคุณเป็นพิเศษ เพราะนั่นถือว่าคุณกำลัง Spam Keyword เพื่อให้บอทอ่านมากเกินไปนั่นเอง ทั้งนี้ การคิด เปอร์เซ็นต์ Keyword นั้น ทุกๆ Search Engine จะไม่สนใจ พวก Stop Words และ Stop Phrases นะครับ Stop Words หรือ Stop Phrases คืออะไร ? ก็คือ คำที่ไม่เกี่ยวข้องในเนื้อหา ไม่มีความหมายซึ่งจะสามารถเป็น Keyword ได้ เช่นพวก a, is, the, so, that, this, are เป็นต้น ซึ่งสิ่งที่เราควรทราบก็คือ เครื่องมือวิเคราะห์เปอร์เซ็นต์ความหนาแน่นส่วนใหญ่ นั้น ไม่ฉลาดพอที่จะตัดพวก Stop Words เหล่านี้ทิ้งไป ในการคำนวณ Keyword Density ดังนั้นหมายความว่า ค่าเปอร์เซ็นต์ Keyword Density ที่เราวิเคราะห์ได้จากเครื่องมือ กับ Search Engine จะมีค่าไม่เท่ากัน (%ที่ Search Engine คิดได้จะสูงกว่าพวกเครื่องมือวิเคราะห์เหล่านี้ เพราะมีตัวหารน้อยกว่า) ทีนี้คงเข้าใจเรื่องราวของ Keyword Density พอสมควรแล้วนะครับ ไปปรับแต่งกันได้เลย ส่วนตัวผมปรับประมาณ ไม่เกิน 7% เท่านั้นเองครับ แนะนำเครื่องมือช่วยตรวจสอบความหนาแน่นของ Keyword ครับ Keyword Checker

เครดิต Seosamutprakarn2013, By: Seo Master

Seo Master present to you:
By Justin Smith, Product Manager

Starting today, Google supports Service Accounts, which provide certificate-based authentication for server-to-server interactions. This means, for example, that a request from a web application to Google Cloud Storage can be authenticated via a certificate instead of a shared key. Certificates offer better security properties than shared keys and passwords, largely because they are not human-readable or guessable.

Service accounts are currently supported by the following Google developer services:

• Google Cloud Storage
• Google Prediction API
• Google URL Shortener
• Google OAuth 2.0 Authorization Server
• Google APIs Console
• Google APIs Client Libraries for Python, Java, and PHP

Over time, more Google APIs and client libraries will be supported.

This feature is implemented as an OAuth 2.0 flow and is compliant with draft 25 of the OAuth 2.0 specification. An application implements the following steps to authenticate with a Service Account:

1. Generate a JSON structure.
2. Sign the JSON structure with a private key, and encode it as a JSON Web Token (JWT).
3. Send the JWT to Google’s OAuth 2.0 Authorization Server in exchange for an access token.
4. Send the access token to Google Cloud Storage or the Google Prediction API.

The Google APIs Client Libraries for Python, Java, and PHP wrap these steps into a few lines of code and abstract the error-prone signing and encoding operations from your applications. We strongly encourage you to use these libraries for this type of interaction. We will be expanding support to other client libraries (including Ruby and .NET). Library developers can find the specifics of the protocol in the OAuth 2.0 Service Accounts documentation.

If you’re a Google App Engine developer, all this might sound similar to what is described in these articles: App Engine & Storage, App Engine & Prediction. Service Accounts generalize this App Engine capability by making it available to other server-side platforms. When using another server-side platform, you can create a Service Account through the Google APIs Console. See the Google APIs Console documentation for more information on creating a Service Account.

As always, we welcome and appreciate feedback. Please post any questions or comments to the OAuth 2.0 Google group.


Justin Smith is a Google Product Manager and works on authentication and authorization technologies. He enjoys woodworking, cycling, country music, and the company of his wife and newborn daughter (not in that order).

Posted by Scott Knaster, Editor

2013, By: Seo Master

Seo Master present to you:
By Navneet Joneja, Product Manager

Google Cloud Storage enables you to use our storage and network infrastructure to store and access your data with high reliability, scale and performance. Today, we’re launching several frequently requested new features:

Signed URLs and updated browser uploads

Many of you have asked us for "virtual valet keys" that give limited access to specific data to the bearer for a short time, enabling them to implement application-managed access control for mobile applications, premium content distribution, and so on. You can now implement these applications and more using short-lived signed URLs to address any object stored in Google Cloud Storage. This feature gives your application another powerful tool to control access to any piece of data. You can also use this feature to enable browser-based uploads from your end users to Google Cloud Storage without requiring them to have Google accounts (browser-based uploads were previously limited to the interoperable API). URL signing is implemented using PKCS-12 keys and the industry-standard RSA algorithm and is currently experimental.

Cross-Origin Resource Sharing

We now support configuring storage buckets to return appropriate Cross-Origin Resource Sharing (CORS) headers, which streamlines the development of advanced JavaScript applications (such as browser-based games) using Google Cloud Storage. Other uses include serving web fonts from Google Cloud Storage and enabling trusted JavaScript access from your App Engine applications.

gsutil 3.0

We've been hard at work making gsutil easier to use at all levels. This latest release includes significant enhancements:

• A refactored, cleaner code-base
• Better in-tool documentation
• Easy in-place update to new releases
• Multithreaded operations
• A hierarchical file tree abstraction layer that maps more closely to the way traditional file systems are organized.

To try all these features and more, download the latest version of gsutil (zip, tarball). Please note that wildcard and list bucket semantics have changed in gsutil to make the tool easier to use in a broad variety of use cases. You can read all about the latest update in the release notes.

We also recently reduced storage prices across all usage tiers by up to 15%.

As always, we welcome your feedback in our discussion group. If you haven’t tried Google Cloud Storage yet, you can sign up and get started here.


Navneet Joneja loves being at the forefront of the next generation of simple and reliable software infrastructure, the foundation on which next-generation technology is being built. When not working, he can usually be found dreaming up new ways to entertain his intensely curious almost-two-year-old.

Posted by Scott Knaster, Editor

2013, By: Seo Master