Friday, March 23, 2012

[Gd] Dev Channel Update

| More

Chrome Releases: Dev Channel Update

The Dev channel has been updated to 19.0.1077.3 for Windows, Mac, Linux and Chrome Frame.  This build contains following updates:

  • Updated V8 -
  • Fixed dialog boxes in settings. (Issue: 118031)
  • Fixed flash videos turning white on mac when running with --disable-composited-core-animation-plugins (Issue: 117916)
  • Change to look for correctly sized favicon when multiple images are provided. (Issue: 118275)
  • Fixed issues - 116044, 117470, 117068, 117668, 118620

Known Issues
  • [Mac] Extension and download icons are drawn incorrectly (Issue: 118755)

Full details about what changes are in this build are available in the SVN revision log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug.

Dharani Govindan
Google Chrome

[Gd] Beta Channel Update

| More

Chrome Releases: Beta Channel Update

The Beta channel has been updated to 18.0.1025.137 for Windows and Chrome Frame.  

This release contains some stability fixes. Full details about what changes are in this build are available in the SVN revision log.  Interested in switching to the Beta channel?  Find out how.  If you find a new issue, please let us know by filing a bug.

Karen Grunberg
Google Chrome

[Gd] Fridaygram: forests, skies, sunken wrecks

| More

Google Developers Blog: Fridaygram: forests, skies, sunken wrecks

Author Photo
By Scott Knaster, Google Developers Blog Editor

You know Street View as the cool Google Maps feature that gives you a peek at your destinations as you map them out. This week, Street View went off-road – way off, all the way to the Amazon Basin. Instead of streets, the Street View team photographed forests, villages, and rivers. The team used more than 50,000 photos to build the Amazon views, and the scenery is much more beautiful than most streets.

Tributary of the Rio Negro - View Larger Map

Speaking of places where there are no streets, take a look (and a listen) to this video of a day in the life of a Solid Rocket Booster (SRB) during a Space Shuttle launch. The video includes a 720p HD version, and the audio was cleaned up by Skywalker Sound to make it sound its finest.

Finally, check out these photos of the sunken Titanic published by National Geographic. This completes our tour of land, air, and sea. Now you can go and enjoy the outdoors yourself!

Once a week we post a Fridaygram, which has little to do with developer announcements and is just for fun. Each Fridaygram item must pass only one test: it has to be interesting to us nerds. Special congrats to the team at Skywalker Sound for resisting the urge to add anything to the SRB video.

[Gd] Keeping Things Fresh

| More

YouTube API Blog: Keeping Things Fresh

Pop quiz: what’s the difference between the following feed URLs?


All three will return a list of videos uploaded in the GoogleDevelopers YouTube channel, with the most recent uploads listed first. However, only the first URL will return the freshest results available — the second or third feeds could both be missing videos that were uploaded within the past few hours. In addition, even if the videos are listed in the second and third feeds, the metadata returned for those videos might not reflect any recent updates.

The reason for this, as explained in our documentation, is that some requests go against our search index, which has cached data, while other requests retrieve data directly from our backend databases, which always contain the most up-to-date data. To determine whether a request will query the search index or the backend database, you can use the following rules of thumb:

  • If your request only includes the max-results and/or start-index query parameters, then it should go against the backend database and the results will be fresh. A few other parameters that change the way the feed is formatted, like prettyprint, callback, or alt, can also be used without triggering the search index. Although it does filter results out of the feed, the fields parameter can also be used while still going against the backend database, because the filtering is performed server-side after the data has been retrieved.

  • If your request contains other parameters, there’s a good chance it will end up against the search index. Some common parameters that will always trigger a search are q and orderby.

Going against the search index isn’t inherently a bad thing. Using the search index is an incredibly efficient way of returning all the videos that match an arbitrary keyword, or ordering a feed of videos so that they’re sorted by view count. The important thing to realize is that the search index doesn’t need to be used for tasks that the backend database can handle, and you’ll get fresher results from the backend database.

Until now we’ve been focusing on retrieving a feed of videos uploaded in a specific account, but these same principles apply to looking up a single video with a given ID as well. Using the information above, can you determine which of these URLs will request a video entry from the backend database, and which will go against the search index?


As you’ve probably figured out, the first URL retrieves the entry for video ID sOEAD-gfJ_M directly from the backend database, while the second URL searches for all entries with metadata containing sOEAD-gfJ_M and then returns the one matching result. The results look similar, but only the first URL will give you the complete, up-to-date video metadata. As such, we recommend always using that syntax when retrieving the entry for a video whose ID you know.

-Jeff Posnick, YouTube API Team

Thursday, March 22, 2012

[Gd] Dev and Beta Channels Update for Chromebooks

| More

Chrome Releases: Dev and Beta Channels Update for Chromebooks

The Beta channel has been updated to 18.0.1025.120 (Platform versions: 1660.94.0) for Chromebooks (Acer AC700, Samsung Series 5, and Cr-48). 

This build is also now available on the Dev channel for Cr-48 Chromebooks. 

This build contains a number of stability improvements. Some highlights of these changes are:
  • 110127 - The short-cut key for caps lock (Shift + Search) is disabled when an accessibility screen reader is enabled
  • 26028 - Fixes an issue with files not being displayed in File Manager when some file names contain UTF-8 characters (generally accented characters).
If you find new issues, please let us know by visiting our help site or filing a bug. Interested in switching channels? Find out how. You can submit feedback using ‘Report an issue’ under the wrench menu.

Danielle Drew
Google Chrome

[Gd] Beta Channel Update

| More

Chrome Releases: Beta Channel Update

The Beta channel has been updated to 18.0.1025.133 for Windows and Chrome Frame.  

This release brings back Swiftshader and gamepad. Full details about what changes are in this build are available in the SVN revision log.  Interested in switching to the Beta channel?  Find out how.  If you find a new issue, please let us know by filing a bug.

Karen Grunberg
Google Chrome

[Gd] App Engine Community Update

| More

Google App Engine Blog: App Engine Community Update

One of the best things about App Engine is our lively developer community. This week, we’re officially moving technical and development questions to Stack Overflow and retiring the language-specific App Engine Google groups. With this week’s move, we wanted to take a moment to highlight some of the best ways to engage with the community.

Technical & Development Questions
For technical and development questions big and small, add the google-app-engine tag to your App Engine questions on Stack Overflow. You can also join our hangouts or office hours to talk directly with App Engine team members.

Many community and team members are active on Google+, using the #appengine hashtag. Our weekly community updates and chats with App Engine community and team members are a great source of tips and tricks and to learn more about what our
community members are up to.

Google Groups
For general discussion about the platform, use the Google App Engine group.

Happy coding!

- Posted by the App Engine Team

[Gd] New Sales Reports on Google Play

| More

Android Developers Blog: New Sales Reports on Google Play

[This post is by Debashish Chatterjee, Krishna Atkuru, and Ellie Powers of the Google Play Publisher Site team. —Dirk Dougherty]

For app publishers, complete and timely sales reporting is incredibly useful for managing a business on Google Play. Today we are introducing a new financial tool — Estimated Sales Reports — to give you visibility over ongoing product sales and help you support customers between payout cycles.

The new sales reports show you complete transaction details of recent sales and refunds for all products in your developer account, including both in-app products and paid apps. Each report is a cumulative for the current payout period, updated nightly with the details of recent transactions. As customers complete purchases and their accounts are charged (or refunds are applied), the new transaction details are appended to the Estimated Sales Report. Depending on account timezone differences, transactions appear on the estimated sales report within 2 days of completion. Finally, at the close of the monthly payout cycle, the current Estimated Sales Report is archived and a new report is created for the next cycle.

You can access current or past sales reports from the “Merchant Reports” section of the Developer Console. The Estimated Sales Reports are downloadable CSV (comma-separated values) files, so you can analyze the data using any tools you choose, in the same way as you've been doing for payout reports. The sales reports list the same details as payout reports — buyer and order, product, device information, amount, currency of sale, and more — except without final payment details. This makes it easier for you to reconcile recorded sales against your actual payouts. Estimated sales reports are available with data starting February 1, 2012.

We’ve also taken this opportunity to rename our existing “Merchant Sales Reports” to Monthly Payout Reports, to better reflect their content.

Together with the application statistics introduced last month, the Estimated Sales and Monthly Payout Reports give you a more complete view of your products’ download and sales activity over time. We hope you’ll find them useful. As always, please feel free to give us feedback through the Developer Help Center.

Join the discussion on

+Android Developers


Wednesday, March 21, 2012

[Gd] Stable Channel Update

| More

Chrome Releases: Stable Channel Update

The Chrome Stable channel has been updated to 17.0.963.83 on Windows, Mac, Linux and Chrome Frame.  This release fixes issues with Flash games, along with the security fixes listed below.

Security fixes and rewards:

Please see the Chromium security page for more detail. Note that the referenced bugs may be kept private until a majority of our users are up to date with the fix.

Some of the items listed below represent the start of hardening measures based on study of the exploits submitted to the Pwnium competition.

  • [$1000] [113902] High CVE-2011-3050: Use-after-free with first-letter handling. Credit to miaubiz.
  • [116162] High CVE-2011-3045: libpng integer issue from upstream. Credit to Glenn Randers-Pehrson of the libpng project.
  • [$1000] [116461] High CVE-2011-3051: Use-after-free in CSS cross-fade handling. Credit to Arthur Gerkis.
  • [116637] High CVE-2011-3052: Memory corruption in WebGL canvas handling. Credit to Ben Vanik of Google.
  • [$1000] [116746] High CVE-2011-3053: Use-after-free in block splitting. Credit to miaubiz.
  • [117418] Low CVE-2011-3054: Apply additional isolations to webui privileges. Credit to Sergey Glazunov.
  • [117736] Low CVE-2011-3055: Prompt in the browser native UI for unpacked extension installation. Credit to PinkiePie.
  • [$2000] [117550] High CVE-2011-3056: Cross-origin violation with “magic iframe”. Credit to Sergey Glazunov.
  • [$500] [117794] Medium CVE-2011-3057: Invalid read in v8. Credit to Christian Holler.

Also, this single low severity issue was fixed in a previous patch but we forgot to issue proper credit:

  • [108648] Low CVE-2011-3049: Extension web request API can interfere with system requests. Credit to Michael Gundlach.

More detailed updates are available on the Chrome Blog.  Full details about what changes are in this release are available in the SVN revision log.  Interested in hopping on the stable channel?  Find out how.  If you find a new issue, please let us know by filing a bug.

Jason Kersey
Google Chrome

[Gd] Beta Channel Update

| More

Chrome Releases: Beta Channel Update

update: The Beta channel for Mac has now been updated to 18.0.1025.129. This brings back Print Preview.

The Beta channel has been updated to 18.0.1025.118 for Windows Chrome Frame.  

This release brings back Print Preview. Full details about what changes are in this build are available in the SVN revision log.  Interested in switching to the Beta channel?  Find out how.  If you find a new issue, please let us know by filing a bug.

Karen Grunberg
Google Chrome

[Gd] Updated SDK Tools and ADT revision 17

| More

Android Developers Blog: Updated SDK Tools and ADT revision 17

Today we are releasing an update to the SDK Tools and the Eclipse plugin. Revision 17 brings a lot of new features and bug fixes in various areas such as Lint, the build system as well as the emulator.

Lint is a static checker which analyzes Android projects for a variety of issues around correctness, security, performance, usability and accessibility, checking your XML resources, bitmaps, ProGuard configuration files, source files and even compiled bytecode. It can be run from within Eclipse or from the command line.
New for r17:

  • Added check for Android API calls that require a version of Android higher than the minimum supported version. You can use the new @TargetApi annotation to specify local overrides for conditionally loaded code. For more information, read here.
  • Added over 40 new Lint rules for a total of over 80, including checks for performance, XML layouts, manifest and file handling. For a full list read here.
  • Added ability to suppress Lint warnings in Java code with the new @SuppressLint annotation, and in XML files with the new tools: namespace prefix and ignore attribute. For more information, read here.
  • Improved HTML and XML reporting and Eclipse integration. For more information, read here.

We’ve also made improvements to the build systems for Eclipse and Ant:

  • Added strict dependency support for 3rd party Jar files. You can read more information here.
  • Added support for custom views with custom attributes in libraries. Layouts using custom attributes must use the namespace URI instead of the URI that includes the app package name. This URI is replaced with the app specific one at build time.
  • Added a feature that allows you to run some code only in debug mode. Builds now generate a class called BuildConfig containing a DEBUG constant that is automatically set according to your build type. You can check the (BuildConfig.DEBUG) constant in your code to run debug-only functions such as outputting debug logs.

The emulator is seeing some big improvements as well:

  • Thanks to contributions to AOSP from Intel, the emulator now supports running x86 system images in virtualization mode on Windows and Mac OS X. This allows the emulator running at near native speed. The drivers are available through the SDK Manager. Read more here.
  • After adding webcam support and sensor emulation, we are adding experimental support for Multi-Touch input through a tethered Android device. (Read more here)

Finally, we are also releasing an updated Support Library with the following improvements:

  • ShareCompat provides easy helper classes for both sending and receiving content for social sharing apps.
  • NavUtils and TaskStackBuilder provide cross-version support for implementing the Android Design guidelines for navigating within your app including the action bar's "Up" button.
  • NotificationCompat.Builder provides a compatibility implementation of Android 3.0's Notification.Builder helper class for creating standardized system notifications.
  • A new Library Project adds support for GridLayout back to API level 7 and higher.

You can get more information about these changes in the SDK Tools Release Notes and ADT Release Notes.


[Gd] Google I/O registration reminder

| More

Google Developers Blog: Google I/O registration reminder

Author PhotoBy Mike Fox, Google Developer Marketing Team

This is a friendly reminder that Google I/O 2012 registration is less than one week away! We can’t wait to see who will be joining us at Google I/O. Registration is first come, first served and opens next Tuesday, March 27, at 7 AM PDT / 14:00 UTC. Last year, tickets sold out in less than an hour, so to be prepared, we suggest you sign in to your Google+ account and be ready to pay with
Google Wallet (formerly Google Checkout). And remember that if you can’t make it to San Francisco, you can attend an I/O Extended viewing party, or watch I/O Live from just about anywhere.

image that reads I want a ticket

While you’re waiting for registration to open, play input/output and show your skill and creativity. If you need inspiration, take a look at some of the ingenious machines fellow developers have made. We’ll be showing off some of the best ones at Google I/O - will yours make the cut?

Mike Fox is a member of the Google Developer Marketing Team. When not working on I/O or cloud products he is cheering on his daughter's soccer team at the University of Notre Dame, trying to enjoy his son's dubstep DJ music, or cheering his brother racing in the 24 Hours of LeMons.

Posted by Scott Knaster, Editor

[Gd] Google Cloud Storage adds several highly requested features

| More

Google Developers Blog: Google Cloud Storage adds several highly requested features

Author Photo
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

[Gd] Service Accounts have arrived

| More

Google Developers Blog: Service Accounts have arrived

Author Photo
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

[Gd] A new home for Google Maps API developers

| More

Google Developers Blog: A new home for Google Maps API developers

Author Photo
By Carlos Cuesta, Product Marketing Manager, Google Maps API

Cross-posted with the Google Geo Developers Blog

When we first launched the Google Maps API, it was all about a map, a pin, and a dream. Back then our technical documentation was relatively simple, consisting of a couple of developer docs and some code samples. Since then the Google Maps API has expanded far beyond our expectations, due in large part to the diverse and innovative developer ecosystem that has grown with us.

With the continuing evolution of the Google Maps API, it became clear that we needed more than just code documentation to convey what’s possible with the Google Maps API. Thus, was born.

In addition to having all the same developer content that was previously available on, the site is designed to highlight and illustrate new features of the Google Maps API through fun and interactive demos. Our goal with is to inspire the next wave of innovation on the Google Maps API, and to connect developers and decision makers with the tools and services that can make their products better.

One of the features of the Google Developers site we’re most excited about is the 3rd party developer showcase, which allows us to celebrate a selection of innovative sites in the Google Maps API ecosystem. Showcase content is carefully curated by the Google Maps API team.

In order to help users discover relevant apps and topics in the showcase, we’ve devised a tagging system that allows you to filter examples both by theme, and by Google Maps API features used.

We hope that the showcase and the interactive examples on the new Google Maps API Developers capture your imagination and inspire you with what’s possible using the platform. The imagination of Google Maps API developers has always been what makes the product great and we’re looking forward to seeing what you come up with next.

Carlos Cuesta is the Product Marketing Manager for Google Maps API. He also enjoys travelling, photography, and collecting vinyl.

Posted by Scott Knaster, Editor

[Gd] Beta Channel Update

| More

Chrome Releases: Beta Channel Update

The Beta channel has been updated to  18.0.1025.116 or 18.0.1025.117 for Windows and 18.0.1025.117 Chrome Frame.  

This release turns off swiftshader and gamepad. These changes and the version differences are due to stability measures and some or all of these features may be enabled again in a future release Please note that print preview will be turned back on in the next release. Full details about what changes are in this build are available in the SVN revision log.  Interested in switching to the Beta channel?  Find out how.  If you find a new issue, please let us know by filing a bug.

Karen Grunberg
Google Chrome


Tuesday, March 20, 2012

[Gd] Inline installation for your apps and extensions

| More

Chromium Blog: Inline installation for your apps and extensions

Over the past several months, the number of daily app and extensions downloads from the Chrome Web Store has more than doubled. We are now seeing millions of downloads per day. Some apps and extensions have grown even faster thanks to inline installation, a feature we launched a few months ago.

With inline installation, you can allow Chrome users who visit your web site to install your apps and extensions directly without requiring them to visit the Chrome Web Store. This creates a smoother experience for your users as it eliminates an extra step where potential users could drop off.

Here are a few examples of the impact of inline installation:
  • Chrome extensions Evernote Clearly and Evernote Web Clipper derive 15% and 25% of their Chrome installations (respectively) from their inline installation implementation 
  • Rovio implemented inline installation for their Angry Birds Chrome game and saw their install rate jump by almost 10%) 
  • Equire, a CRM extension that integrates with Gmail, saw a 66% increase in Chrome user retention after they implemented inline installation. 

    Example: Installing Evernote Web Clipper from Evernote’s Site
Implementing inline installation is very easy:
  1. Provide a link to your Chrome Web Store item.
  2. Write some script to check for whatever client-side capabilities your app requires (support for WebGL, the Web Audio API, etc). Modernizr is a great library to use for this. 
  3. Call a JavaScript function to initiate the install process. 
The user sees the same Add To Chrome dialog prompt that they would on the store, confirm the install, and they're done – all without leaving your site.

The full details and documentation for using inline installation can be found here. If you have any questions, you can reach us on our developer forum.

Posted by Joe Marini, Developer Advocate

[Gd] Five common SEO mistakes (and six good ideas!)

| More

Official Google Webmaster Central Blog: Five common SEO mistakes (and six good ideas!)

Webmaster Level: Beginner to Intermediate

To help you avoid common mistakes webmasters face with regard to search engine optimization (SEO), I filmed a video outlining five common mistakes I’ve noticed in the SEO industry. Almost four years ago, we also gathered information from all of you (our readers) about your SEO recommendations and updated our related Help Center article given your feedback. Much of the same advice from 2008 still holds true today -- here’s to more years ahead building a great site!

If you’re short on time, here’s the gist:

Avoid these common mistakes
1. Having no value proposition: Try not to assume that a site should rank #1 without knowing why it’s helpful to searchers (and better than the competition :)

2. Segmented approach: Be wary of setting SEO-related goals without making sure they’re aligned with your company’s overall objectives and the goals of other departments. For example, in tandem with your work optimizing product pages (and the full user experience once they come to your site), also contribute your expertise to your Marketing team’s upcoming campaign. So if Marketing is launching new videos or a more interactive site, be sure that searchers can find their content, too.

3. Time-consuming workarounds: Avoid implementing a hack rather than researching new features or best practices that could simplify development (e.g., changing the timestamp on an updated URL so it’s crawled more quickly instead of easily submitting the URL through Fetch as Googlebot).

4. Caught in SEO trends: Consider spending less time obsessing about the latest “trick” to boost your rankings and instead focus on the fundamental tasks/efforts that will bring lasting visitors.

5. Slow iteration: Aim to be agile rather than promote an environment where the infrastructure and/or processes make improving your site, or even testing possible improvements, difficult.
Six fundamental SEO tips
1. Do something cool: Make sure your site stands out from the competition -- in a good way!

2. Include relevant words in your copy: Try to put yourself in the shoes of searchers. What would they query to find you? Your name/business name, location, products, etc., are important. It's also helpful to use the same terms in your site that your users might type (e.g., you might be a trained “flower designer” but most searchers might type [florist]), and to answer the questions they might have (e.g., store hours, product specs, reviews). It helps to know your customers.

3. Be smart about your tags and site architecture: Create unique title tags and meta descriptions; include Rich Snippets markup from where appropriate. Have intuitive navigation and good internal links.

4. Sign up for email forwarding in Webmaster Tools: Help us communicate with you, especially when we notice something awry with your site.

5. Attract buzz: Natural links, +1s, likes, follows... In every business there's something compelling, interesting, entertaining, or surprising that you can offer or share with your users. Provide a helpful service, tell fun stories, paint a vivid picture and users will share and reshare your content.

6. Stay fresh and relevant: Keep content up-to-date and consider options such as building a social media presence (if that’s where a potential audience exists) or creating an ideal mobile experience if your users are often on-the-go.
Good luck to everyone!

Written by Maile Ohye, Developer Programs Tech Lead

[Gd] Beta Channel Update

| More

Chrome Releases: Beta Channel Update

The Beta channel has been updated to 18.0.1025.113 for Windows, Mac, Linux, and Chrome Frame.  

This release changes to turns of print preview and fixes a few known crashes and memory issues. Please note that print preview will possibly be turned back on in a future release. Full details about what changes are in this build are available in the SVN revision log.  Interested in switching to the Beta channel?  Find out how.  If you find a new issue, please let us know by filing a bug.

Karen Grunberg
Google Chrome