Supporting rel="canonical" HTTP Headers
12:19 AM - Posted by NIA - 0 comments
Based on your feedback, we’re happy to announce that Google web search now supports link rel="canonical" relationships specified in HTTP headers as per the syntax described in section 5 of IETF RFC 5988. Webmasters can use rel="canonical" HTTP headers to signal the canonical URL for both HTML documents and other types of content such as PDF files.
To see the rel="canonical" HTTP header in action, let’s look at the scenario of a website offering a white paper both as an HTML page and as a downloadable PDF alternative, under these two URLs:
  • http://www.example.com/white-paper.html
  • http://www.example.com/white-paper.pdf
In this case, the webmaster can signal to Google that the canonical URL for the PDF download is the HTML document by using a rel="canonical" HTTP header when the PDF file is requested; for example:
GET /white-paper.pdf HTTP/1.1
Host: www.example.com
(...rest of HTTP request headers...)
 
HTTP/1.1 200 OK
Content-Type: application/pdf
Link: ; rel="canonical"
Content-Length: 785710
(... rest of HTTP response headers...)
Another common situation in which rel="canonical" HTTP headers may help is when a website serves the same file from multiple URLs (for example when using a content distribution network) and the webmaster wishes to signal to Google the preferred URL.
We currently support these link header elements for web search only. As we see how webmasters are using these elements, we're hoping to add support for them in our other properties. For more information, please see our Help Center articles about canonicalization and the rel="canonical" element. If you have any questions, please ask in our Webmaster Help Forum.


Webinar: Implementing the +1 Button
12:18 AM - Posted by NIA - 0 comments
A few weeks ago, we launched the +1 button for your site, allowing visitors to recommend your content on Google search directly from your site. As people see recommendations from their friends and contacts beneath your search results, you could see more, better qualified traffic from Google.

But how do you make sure this experience is user friendly? Where should you position the +1 button? How do you make sure the correct URL is getting +1’d?
http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ http://digitalet.net/ 

On Tuesday, June 21 at 3pm ET, please join Timothy Jordan, Google Developer Advocate, to learn about how to best implement the +1 button on your site. He’ll be talking through the technical implementation details as well as best practices to ensure the button has maximum impact. During the webinar, we’ll review the topics below:


  • Getting started
  • Best practices
  • Advanced options
  • Measurement
  • And, we’ll save time for Q&A
If you would like to attend, please register here. To download the code for your site, visit our +1 button tool on Google Webmaster Central.


Announcing Instant Pages
12:18 AM - Posted by NIA - 1 comments
Earlier today we announced Instant Pages, a new feature to help users get to their desired search results even faster--in some cases even instantly! The Instant Pages feature is enabled by prerendering technology that we are building into Chrome and then is intelligently triggered by web search when we're very confident about which result is the best answer for the user's search.

This prerendering technology is currently in the Chrome Dev Channel and will be going to Beta later this week.

You can see Instant Pages in action in this video:


At Google we're obsessed with speed. We've seen time and time again how an increase in apparent speed leads to a direct increase in user happiness and engagement. Instant Pages helps visitors arrive at your site faster. When we trigger Instant Pages for your site, users can start interacting with your site almost immediately, without having to wait for text and images to load. We'll only trigger Instant Pages when we have very high confidence that your site is the exact result users are looking for. Search traffic will be measured in Webmaster Tools just like before this feature, with only results the user visited counted. We'll take the time this summer before the feature launches in stable versions of Chrome to collect your feedback.

The vast majority of sites will automatically work correctly when prerendered in Chrome. Check out the prerendering post on the Chromium blog if you want to learn more about how prerendering works in Chrome or how you can detect that your site is being prerendered.


Authorship markup and web search
12:17 AM - Posted by NIA - 0 comments

Tuesday, June 07, 2011 at 12:49 PM

Webmaster level: Intermediate

Today we're beginning to support authorship markup—a way to connect authors with their content on the web. We're experimenting with using this data to help people find content from great authors in our search results.

We now support markup that enables websites to publicly link within their site from content to author pages. For example, if an author at The New York Times has written dozens of articles, using this markup, the webmaster can connect these articles with a New York Times author page. An author page describes and identifies the author, and can include things like the author’s bio, photo, articles and other links.

If you run a website with authored content, you’ll want to learn about authorship markup in our Help Center. The markup uses existing standards such as HTML5 (rel=”author”) and XFN (rel=”me”) to enable search engines and other web services to identify works by the same author across the web. If you're already doing structured data markup using microdata from schema.org, we'll interpret that authorship information as well.

We wanted to make sure the markup was as easy to implement as possible. To that end, we’ve already worked with several sites to markup their pages, including The New York Times, The Washington Post, CNET, Entertainment Weekly, The New Yorker and others. In addition, we’ve taken the extra step to add this markup to everything hosted by YouTube and Blogger. In the future, both platforms will automatically include this markup when you publish content.

We know that great content comes from great authors, and we’re looking closely at ways this markup could help us highlight authors and rank search results.


No Script Tags help Ful for SEO
4:59 AM - Posted by NIA - 0 comments


Introducing schema.org: Search engines come together for a richer web
11:59 PM - Posted by NIA - 0 comments
Today we’re announcing schema.org, a new initiative from Google, Bing and Yahoo! to create and support a common set of schemas for structured data markup on web pages. Schema.org aims to be a one stop resource for webmasters looking to add markup to their pages to help search engines better understand their websites.

At Google, we’ve supported structured markup for a couple years now. We introduced rich snippets in 2009 to better represent search results describing people or containing reviews. We’ve since expanded to new kinds of rich snippets, including products, events, recipes, and more.


Example of a rich snippet: a search result enhanced by structured markup. In this case, the rich snippet contains a picture, reviews, and cook time for the recipe.

Adoption by the webmaster community has grown rapidly, and today we’re able to show rich snippets in search results more than ten times as often as when we started two years ago.

We want to continue making the open web richer and more useful. We know that it takes time and effort to add this markup to your pages, and adding markup is much harder if every search engine asks for data in a different way. That’s why we’ve come together with other search engines to support a common set of schemas, just as we came together to support a common standard for Sitemaps in 2006. With schema.org, site owners can improve how their sites appear in search results not only on Google, but on Bing, Yahoo! and potentially other search engines as well in the future.

Now let’s discuss some of the details of schema.org relevant to you as a webmaster:

1) Schema.org contains a lot of new markup types.
We’ve added more than 100 new types as well as ported over all of the existing rich snippets types. If you’ve looked at adding rich snippets markup before but none of the existing types were relevant for your site, it’s worth taking another look. Here are a few popular types:
Or, view a full list of all schema.org types. The new markup types may be used for future rich snippets formats as well as other types of improvements to help people find your content more easily when searching.

2) Schema.org uses microdata.
Historically, we’ve supported three different standards for structured data markup: microdata, microformats, and RDFa. We’ve decided to focus on just one format for schema.org to create a simpler story for webmasters and to improve consistency across search engines relying on the data. There are arguments to be made for preferring any of the existing standards, but we’ve found that microdata strikes a balance between the extensibility of RDFa and the simplicity of microformats, so this is the format that we’ve gone with.

To get an overview of microdata as well as the conventions followed by schema.org, take a look at the schema.org Getting Started guide.

3) We’ll continue to support our existing rich snippets markup formats.
If you’ve already done markup on your pages using microformats or RDFa, we’ll continue to support it. One caveat to watch out for: while it’s OK to use the new schema.org markup or continue to use existing microformats or RDFa markup, you should avoid mixing the formats together on the same web page, as this can confuse our parsers.

4) Test your markup using the rich snippets testing tool.
It’s very useful to test your web pages with markup to make sure we’re able to parse the data correctly. As with previous rich snippets markup formats, you should use the rich snippets testing tool for this purpose. Note that while the testing tool will show the marked up information that was parsed from the page, rich snippets previews are not yet shown for schema.org markup. We’ll be adding this functionality soon.

The schema.org website and the rich snippets testing tool are in English. However, Google shows rich snippets in search results globally, so there’s no need to wait to start marking up your pages.

To learn more about rich snippets and how they relate to schema.org, check out the Rich snippets schema.org FAQ.






Panda Updattion: Goodbye to Low-Quality LB
5:52 AM - Posted by NIA - 0 comments
A while back, I wrote about how to get the best high volume links. Fast forward eight months and Google has made two major changes to its algorithm -- first to target spammy/scraper sites, followed by the larger Panda update that targeted "low quality" sites. Plus, Google penalized JCPenney, Forbes, and Overstock.com for "shady" linking practices.
What's it all mean for link builders? Well, it's time we say goodbye to low quality link building altogether.
'But The Competitors Are Doing It' Isn't an Excuse
This may be tough for some link builders to digest, especially if you're coming from a research standpoint and you see that competitors for a particular keyword are dominating because of their thousands upon thousands of pure spam links.
But here are two things you must consider about finding low quality, high volume links in your analysis:
  1. Maybe it isn't the links that got the competitor where they are today. Maybe they are a big enough brand with a good enough reputation to be where they are for that particular keyword.

  2. If the above doesn't apply, then maybe it's just a matter of time before Google cracks down even further, giving no weight to those spammy backlinks.
Because, let's face it. You don't want to be the SEO company behind the next Overstock or JCPenney link building gone wrong story!
How to Determine a Valuable Backlink Opportunity
How can you determine whether a site you're trying to gain a link from is valuable? Here are some "warning" signs as to what Google may have or eventually deem as a low-quality site.
What Should You Be Doing
Where should you focus your energy? Content, of course!
Nine in 10 organizations use blogs, whitepapers, webinars, infographics, and other high quality content to leverage for link building and to attract natural, organic links. Not only can use your content to build links, but you can use it to build leads as well by proving the business knows their stuff when it comes to their industry.
Have You Changed Your Link Building Strategy?
With the recent news, penalties, and algorithm changes, have you begun to change your link building strategies? Please share your thoughts in the comments!