Download

https://plusone.google.com/*
www.google.com##BUTTON[name="eswidget"]

The Site Speed report measures the page load time (latency) for a sample of pageviews on your website pages. It appears in the Content section of the Analytics reports. With this report, you can see which pages load the fastest and which ones are slower. You can also analyze your overall site speed along other important dimensions in order to learn how your site speed relates to a variety of factors. For example, you can view your site speed across the following categories:

Content—which landing pages are slowest?
Traffic sources—which campaigns correspond to faster page loads overall?
Visitor—how does latency compare by visitor type or geographic region?
Technology—does browser, operating system or screen resolution impact latency metrics?
Finally—and most importantly—you can take action to improve page load speed for slower pages and then track latency along these other dimensions to see if your actions resulted in desired improvements.

Huffduffer extension for Google Chrome

Update Frequency

To change how frequently Google Software Update checks for updates, execute the following in the Terminal application:

$ defaults write com.google.Keystone.Agent checkInterval <frequency>

where <frequency> is the elapsed time in seconds between update checks.

To disable Google Software Update from checking for updates, execute the following in the Terminal application:

$ defaults write com.google.Keystone.Agent checkInterval 0

Manual Updates

Google Software Update also provides a way to manually update all Google software on a user's Mac. Here's how:

In Finder, select Go > Go to Folder.
In the window that appears, enter one of the following locations. It's expected that one of these folders won't be found:
/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/
~/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/
In the folder that opens, double click the file named 'CheckForUpdatesNow.command'.
Terminal will open to run the file. When you see the message '[Process completed]' you can close Terminal. Once this is done, your Google programs will be up to date.

All about Googlebot

Rich snippets testing tool
Share

* Twitter
* Gmail
* Blogger
* Buzz
* Orkut
* Google Reader
* Bookmarks
* » More

Comment Print

The rich snippets testing tool lets you check your markup and make sure that Google can extract the structured data from your page. This tool will display the markup found on a specific web page, as well as a preview of how that page might appear in Google search results.

This tool is still a work in progress, so there are a few points to note:

* The tool doesn't currently display a preview of breadcrumbs content. We're working on it!
* The tool interface is currently available in English only. The tool will correctly test markup in other languages; however, the results will not look like they will look in an actual non-English search results page.
* The tool will only display extracted information that is officially supported for rich snippets. Supported RDFa attributes are xmlns, typeof, property, rel, and content.

"Insufficient data to generate preview"

In general, the goal of rich snippets is to display the most relevant content on the page to users. If you see an "insufficient data to generate preview" message, it is generally for one of two reasons:

* The marked-up content doesn't appear to be the main subject of the page. This can happen if the marked-up content is very low down on the page, is found in boilerplate elements such as headers, footers, and navigation, or is included in a hidden HTML element.
* The marked-up content is missing important tags. For example, a Person item must include organization, location, or role, as well as name.

This is an early release of the testing tool, and feedback is welcome. Please submit feedback or bugs on the Webmaster Tools forum. For tips and tricks, check out the Rich snippets knol (English only).

Rich snippets (microdata, microformats, RDFa)

o Rich snippets (microdata, microformats, and RDFa)
o Breadcrumbs
o About microdata
o About microformats
o About RDFa
o Nested items
o Recipes
o Reviews
o Review ratings
o People
o Events
o Businesses and organizations
o Products
o Videos: Facebook Share and RDFa
o Rich snippets testing tool

<div itemscope itemtype="http://data-vocabulary.org/Breadcrumb"> <a href="http://www.example.com/dresses" itemprop="url"> <span itemprop="title">Dresses</span> </a> › </div> <div itemscope itemtype="http://data-vocabulary.org/Breadcrumb"> <a href="http://www.example.com/dresses/real" itemprop="url"> <span itemprop="title">Real Dresses</span> </a> › </div> <div itemscope itemtype="http://data-vocabulary.org/Breadcrumb"> <a href="http://www.example.com/clothes/dresses/real/green" itemprop="url"> <span itemprop="title">Real Green Dresses</span> </a> </div>

# Google Website Optimizer Support/Help

## Testing with fragmented sections

Fragmented sections allow you to control your experiments so that certain variations always appear together, delivering more consistent page variations. With fragmented sections, you can classify multiple elements on your page as part of the same section -- when a specific variation of one element shows, a specific variation of another element will show. The result is greater coordination within your page and the exclusion of combinations that you suspect will not work.

If you want to use Google Web History and save your browser's history on Google's servers, you generally need to go to this page and select "Enable Web History and install the toolbar". This procedure installs Google Toolbar, a plug-in available only for Internet Explorer and Firefox, and enables the PageRank feature, which displays the ranking of any site you visit while sending the URL to Google in the process.

If you use another browser or if you don't like Google Toolbar, there's an alternative way to send all the web pages you visit to Google: a script that asks Google for the PageRank of any web pages you load in your browser. To install the script you need:

* Greasemonkey, an extension for Firefox. Make sure to restart the browser before trying to add the script.
* Trixie, one of the best Greasemonkey-like plug-ins for Internet Explorer
* SIMBL and GreaseKit for Safari
* no additional software for Opera, but you need to enable the feature from Opera's interface
* Konqueror Userscript for Konqueror

The script is taken from this site, that also adapted it from other scripts. I mirrored the script to an easily-accessible location.

Once you've added the script, you only need to enable Google Web History: go to this page and select "Enable Web History and install the toolbar", but cancel the downloading process (you don't need the toolbar).

This feature only works when you're logged in to your Google Account. To disable it, remove the script from Greasemonkey or from another plug-in you've installed.

The Google Font Directory lets you browse all the fonts available via the Google Font API. All fonts in the directory are available for use on your website under an open source license and served by Google servers.

View font details to get the code needed to embed the font on your web site. Please also visit our quick start guide and FAQ page. For more help and suggestions, use our moderator page

This guide explains how to use the Google Font API to add web fonts to your pages. You don't need to do any programming; all you have to do is add a special stylesheet link to your HTML document, then refer to the font in a CSS style.

With the AJAX Language API, you can translate and detect the language of blocks of text within a webpage using only Javascript. In addition, you can enable transliteration on any textfield or textarea in your web page. For example, if you were transliterating to Hindi, this API will allow users to phonetically spell out Hindi words using English and have them appear in the Hindi script.

The language API is designed to be simple and easy to use to translate and detect languages on the fly when offline translations are not available. We plan on adding more exciting capabilities to the AJAX Language API in the future, so stay tuned.

So what is the difference between Translation and Transliteration? Transliteration is the process of phonetically converting a word written in one script into another. Transliteration should not be confused with translation, which involves a change in language while preserving meaning. With transliteration, it is the sound of the words that are converted from one alphabet to the other.

We think JavaScript is awesome. We also think browsers are awesome. Indeed, when we talk about them, we say they are the cat's meow – which is an American expression meaning AWESOME.

In light of these deeply held beliefs, we created this site to showcase cool experiments for both JavaScript and web browsers.

These experiments were created by designers and programmers from around the world using the latest open standards, including HTML5, Canvas, SVG, and more. Their work is making the web faster, more fun, and more open – the same spirit in which we built Google Chrome.

Naturally, if you've made something fun and fast with JavaScript, please send it in. We can't post everything, but we'd love to see it.

Thanks for visiting, and happy experimenting.

With the Feed API, you can download any public Atom, RSS, or Media RSS feed using only JavaScript, so you can easily mash up feeds with your content and other APIs like the Google Maps API.

The Google AJAX Feed API takes the pain out of developing mashups in JavaScript because you can now mash up feeds using only a few lines of JavaScript, rather than dealing with complex server-side proxies. This makes it easy to quickly integrate feeds on your website, as shown below.

Look at public data.
Get started with an interesting data set from the Table Gallery.

Import your own.
Upload data tables from spreadsheets or CSV files, even KML. Developers can use the Fusion Tables API to insert, update, delete and query data programmatically. You can export your data as CSV or KML too.

During our labs release, we can support up to 100MB per table, and up to 250MB per user.

Visualize it instantly.
See the data on a map or as a chart immediately. Columns with locations are interpreted automatically, and you can adjust them directly on a map if necessary. Use filter and aggregate tools for more selective visualizations.

Web applications have evolved from simple HTML pages into rich, interactive applications that provide a great user experience. Today's web apps pose a challenge for developers, however: how do you create and maintain efficient JavaScript code that downloads quickly and works across different browsers?

The Closure tools help developers to build rich web applications with JavaScript that is both powerful and efficient. The Closure tools include:
A JavaScript optimizer

The Closure Compiler compiles JavaScript into compact, high-performance code. The compiler removes dead code and rewrites and minimizes what's left so that it downloads and runs quickly. It also also checks syntax, variable references, and types, and warns about common JavaScript pitfalls. These checks and optimizations help you write apps that are less buggy and easier to maintain. You can use the compiler with Closure Inspector, a Firebug extension that makes debugging the obfuscated code almost as easy as debugging the human-readable source.
A comprehensive JavaScript library

The Closure Library is a broad, well-tested, modular, and cross-browser JavaScript library. You can pull just what you need from a large set of reusable UI widgets and controls, and from lower-level utilities for DOM manipulation, server communication, animation, data structures, unit testing, rich-text editing, and more.

The Closure Library is server-agnostic, and is intended for use with the Closure Compiler.
An easy templating system for both Java & JavaScript

Closure Templates simplify the task of dynamically generating HTML. They have a simple syntax that is natural for programmers. In contrast to traditional templating systems, in which you use one big template per page, you can think of Closure Templates as small components that you compose to form your user interface.

Closure Templates are implemented for both JavaScript and Java, so that you can use the same templates on both the server and client side. For the client side, Closure Templates are precompiled into efficient JavaScript.

A little over six months ago we released a new malware diagnostic tool in Webmaster Tools with the help of Lucas Ballard from the anti-malware team. This feature has been a great success; many of you were interested to know if Google had detected malicious software in your site, and you used the tool's information to find and remove that malware and to fix the vulnerabilities in your servers.

The single best way to make Google aware of all your videos on your website is to create and maintain a Video Sitemap. Video Sitemaps provide Google with essential information about your videos, including the URLs for the pages where the videos can be found, the titles of the videos, keywords, thumbnail images, durations, and other information. The Sitemap also allows you to define the period of time for which each video will be available. This is particularly useful for content that has explicit viewing windows, so that we can remove the content from our index when it expires.

# Create a transaction object.

Use the _addTrans() method to intialize a transaction object. The transaction object stores all the related information about a single transaction, such as the order ID, shipping charges, and billing address. The information in the transaction object is associated with its items by means of the order IDs for the transaction and all items, which should be the same ID.
# Add items to the transaction.

The addItem() method tracks information about each individual item in the user's shopping cart and associates the item with each transaction via the orderId field. This method tracks the details about a particular item, such as SKU, price, category, and quantity.
# Submit the transaction to the Analytics servers.

The _trackTrans() method confirms that a purchase has occurred, and all data that has been built up in the transaction object is finalized as a transaction.

A fully automated, active web application security reconnaissance tool. Key features:

* High speed: pure C code, highly optimized HTTP handling, minimal CPU footprint - easily achieving 2000 requests per second with responsive targets.

* Ease of use: heuristics to support a variety of quirky web frameworks and mixed-technology sites, with automatic learning capabilities, on-the-fly wordlist creation, and form autocompletion.

* Cutting-edge security logic: high quality, low false positive, differential security checks, capable of spotting a range of subtle flaws, including blind injection vectors.