Welcome

menu

Official Google Webmaster Central Blog

Sabtu, 24 Mei 2014

Official Google Webmaster Central Blog

Link to Google Webmaster Central Blog

Understanding web pages better

Posted: 23 May 2014 09:00 AM PDT

In 1998 when our servers were running in Susan Wojcicki's garage, we didn't really have to worry about JavaScript or CSS. They weren't used much, or, JavaScript was used to make page elements... blink! A lot has changed since then. The web is full of rich, dynamic, amazing websites that make heavy use of JavaScript. Today, we'll talk about our capability to render richer websites — meaning we see your content more like modern Web browsers, include the external resources, execute JavaScript and apply CSS.

Traditionally, we were only looking at the raw textual content that we'd get in the HTTP response body and didn't really interpret what a typical browser running JavaScript would see. When pages that have valuable content rendered by JavaScript started showing up, we weren't able to let searchers know about it, which is a sad outcome for both searchers and webmasters.

In order to solve this problem, we decided to try to understand pages by executing JavaScript. It's hard to do that at the scale of the current web, but we decided that it's worth it. We have been gradually improving how we do this for some time. In the past few months, our indexing system has been rendering a substantial number of web pages more like an average user's browser with JavaScript turned on.

Sometimes things don't go perfectly during rendering, which may negatively impact search results for your site. Here are a few potential issues, and – where possible, – how you can help prevent them from occurring:
  • If resources like JavaScript or CSS in separate files are blocked (say, with robots.txt) so that Googlebot can't retrieve them, our indexing systems won't be able to see your site like an average user. We recommend allowing Googlebot to retrieve JavaScript and CSS so that  your content can be indexed better. This is especially important for mobile websites, where external resources like CSS and JavaScript help our algorithms understand that the pages are optimized for mobile.
  • If your web server is unable to handle the volume of crawl requests for resources, it may have a negative impact on our capability to render your pages. If you'd like to ensure that your pages can be rendered by Google, make sure your servers are able to handle crawl requests for resources.
  • It's always a good idea to have your site degrade gracefully. This will help users enjoy your content even if their browser doesn't have compatible JavaScript implementations. It will also help visitors with JavaScript disabled or off, as well as search engines that can't execute JavaScript yet.
  • Sometimes the JavaScript may be too complex or arcane for us to execute, in which case we can't render the page fully and accurately.
  • Some JavaScript removes content from the page rather than adding, which prevents us from indexing the content.

To make things easier to debug, we're currently working on a tool for helping webmasters better understand how Google renders their site. We look forward to making it to available for you in the coming days in Webmaster Tools.

If you have any questions, please feel free to visit our help forum.

Posted by Erik Hendriks and Michael Xu, Software Engineers, and Kazushi Nagayama, Webmaster Trends Analyst

Official Google Webmaster Central Blog

Selasa, 20 Mei 2014

Official Google Webmaster Central Blog

Link to Google Webmaster Central Blog

Making your site more mobile-friendly with PageSpeed Insights

Posted: 19 May 2014 09:00 AM PDT

Webmaster level: all


To help developers and webmasters make their pages mobile-friendly, we recently updated PageSpeed Insights with additional recommendations on mobile usability.




Poor usability can diminish the benefits of a fast page load. We know the average mobile page takes more than 7 seconds to load, and by using the PageSpeed Insights tool and following its speed recommendations, you can make your page load much faster. But suppose your fast mobile site loads in just 2 seconds instead of 7 seconds. If mobile users still have to spend another 5 seconds once the page loads to pinch-zoom and scroll the screen before they can start reading the text and interacting with the page, then that site isn't really fast to use after all. PageSpeed Insights' new User Experience rules can help you find and fix these usability issues.

These new recommendations currently cover the following areas:
  • Configure the viewport: Without a meta-viewport tag, modern mobile browsers will assume your page is not mobile-friendly, and will fall back to a desktop viewport and possibly apply font-boosting, interfering with your intended page layout. Configuring the viewport to width=device-width should be your first step in mobilizing your site.

  • Size content to the viewport: Users expect mobile sites to scroll vertically, not horizontally. Once you've configured your viewport, make sure your page content fits the width of that viewport, keeping in mind that not all mobile devices are the same width.

  • Use legible font sizes: If users have to zoom in just to be able read your article text on their smartphone screen, then your site isn't mobile-friendly. PageSpeed Insights checks that your site's text is large enough for most users to read comfortably.
  • Size tap targets appropriately: Nothing's more frustrating than trying to tap a button or link on a phone or tablet touchscreen, and accidentally hitting the wrong one because your finger pad is much bigger than a desktop mouse cursor. Make sure that your mobile site's touchscreen tap targets are large enough to press easily.
  • Avoid plugins: Most smartphones don't support Flash or other browser plugins, so make sure your mobile site doesn't rely on plugins.
These rules are described in more detail in our help pages. When you're ready, you can test your pages and the improvements you make using the PageSpeed Insights tool. We've also updated PageSpeed Insights to use a mobile friendly design, and we've translated our documents into additional languages.

As always, if you have any questions or feedback, please post in our discussion group.

Belajar Ngeblog di BLOG kurnia septa

Selasa, 13 Mei 2014

Belajar Ngeblog di BLOG kurnia septa

Link to Belajar Ngeblog di BLOG

Membuat Link Header Blog Mengarah ke Blog Lain

Posted: 12 May 2014 05:14 PM PDT

Kamu memiliki beberapa blog yang mungkin sudah tidak terurus lagi, tidak ingin menghapusnya dan ingin blog-blog itu bisa mengarah ke blog utama kamu. Inilah salah satu cara mengarahkan link header blog ke laman utama blog kita atau situs web lain. Membuat link header blog mengarah ke blog atau situs lain yang kita inginkan juga dapat blog-blog yang sudah terurus kembali bisa bermanfaat. Dengan

Official Google Webmaster Central Blog

Official Google Webmaster Central Blog

Link to Google Webmaster Central Blog

Creating the Right Homepage for your International Users

Posted: 12 May 2014 03:10 AM PDT


If you are doing business in more than one country or targeting different languages, we recommend having separate sites or sections with specific content on each URLs targeted for individual countries or languages. For instance one page for US and english-speaking visitors, and a different page for France and french-speaking users. While we have information on handling multi-regional and multilingual sites, the homepage can be a bit special. This post will help you create the right homepage on your website to serve the appropriate content to users depending on their language and location.

There are three ways to configure your homepage / landing page when your users access it:
  • Show everyone the same content.
  • Let users choose.
  • Serve content depending on users' localization and language.
Let's have a look at each in detail.

Show users worldwide the same content 

In this scenario, you decide to serve specific content for one given country and language on your homepage / generic URL (http://www.example.com). This content will be available to anyone who accesses that URL directly in their browser or those who search for that URL specifically. As mentioned above, all country & language versions should also be accessible on their own unique URLs.


Note: You can show a banner on your page to suggest a more appropriate version to users from other locations or with different language settings.

Let users choose which local version and which language they want 

In this configuration, you decide to serve a country selector page on your homepage / generic URL and to let users choose which content they want to see depending on country and language. All users who type in that URL can access the same page.

If you implement this scenario on your international site, remember to use the x-default rel-alternate-hreflang annotation for the country selector page, which was specifically created for these kinds of pages. The x-default value helps us recognize pages that are not specific to one language or region.

Automatically redirect users or dynamically serve the appropriate HTML content depending on users' location and language settings

A third scenario would be to automatically serve the appropriate HTML content to your users depending on their location and language settings. You will either do that by using server-side 302 redirects or by dynamically serving the right HTML content.

Remember to use x-default rel-alternate-hreflang annotation on the homepage / generic page even if the latter is a redirect page that is not accessible directly for users.

Note: Think about redirecting users for whom you do not have a specific version. For instance, French-speaking users on a website that has English, Spanish and Chinese versions. Show them the content that you consider the most appropriate.

Whatever configuration you decide to go with, you should make sure all the pages – including country and language selector pages:
  • Have rel-alternate-hreflang annotations.
  • Are accessible for Googlebot's crawling and indexing: do not block the crawling or indexing of your localized pages.
  • Always allow users to switch local version or language: you can do that using a drop down menu for instance.
Reminder: As mentioned in the beginning, remember that you must have separate URLs for each country and language version. 

About rel-alternate-hreflang annotations

Remember to annotate all your pages - whatever method you choose. This will greatly help search engines to show the right results to your users.

Country selector pages and redirecting or dynamically serving homepages should all use the x-default hreflang, which was specifically designed for auto-redirecting homepages and country selectors. 

Finally, here are a few useful reminders about rel-alternate-hreflang annotations in general:
  • Your annotations must be confirmed from the other pages. If page A links to page B, page B must link back to page A, otherwise, your annotations may not be interpreted correctly.
  • Your annotations should be self-referential. Page A should use rel-alternate-hreflang annotation linking to itself.
  • You can specify the rel-alternate-hreflang annotations in the HTTP header, in the head section of the HTML, or in a sitemap file. We strongly recommend that you choose only one way to implement the annotations, in order to avoid inconsistent signals and errors.
  • The value of the hreflang attribute must be in ISO 639-1 format for the language, and in ISO 3166-1 Alpha 2 format for the region. Specifying only the region is not supported. If you wish to configure your site only for a country, use the geotargeting feature in Webmaster Tools
Following these recommendations will help us better understand your localized content and serve more relevant results to your users in our search results. As always, if you have any questions or feedback, please tell us in the internationalization Webmaster Help Forum.

Official Google Webmaster Central Blog

Kamis, 01 Mei 2014

Official Google Webmaster Central Blog

Link to Google Webmaster Central Blog

Webmaster Guidelines for sneaky redirects updated

Posted: 30 Apr 2014 02:06 AM PDT

Webmaster Level: All

Redirects are often used by webmasters to help forward visitors from one page to another. They are a normal part of how the web operates, and are very valuable when well used. However, some redirects are designed to manipulate or deceive search engines or to display different content to human users than to search engines. Our quality guidelines strictly forbid these kinds of redirects.

For example, desktop users might receive a normal page, while hackers might redirect all mobile users to a completely different spam domain. To help webmasters better recognize problematic redirects, we have updated our quality guidelines for sneaky redirects with examples that illustrate redirect-related violations.

We have also updated the hacked content guidelines to include redirects on compromised websites. If you believe your site has been compromised, follow these instructions to identify the issues on your site and fix them.

As with any violation of our quality guidelines, we may take manual action, including removal from our index, in order to maintain the quality of the search results. If you have any questions about our guidelines, feel free to ask in our Webmaster Help Forum.


Detik Pos Indonesia

Selasa, 29 April 2014

Detik Pos Indonesia


Juara Premier League Ditentukan Lewat Selisih Gol Lagi?

Posted: 28 Apr 2014 12:15 AM PDT

DETIKPOS.net - Juara Premier League Ditentukan Lewat Selisih Gol Lagi?. Berita Liga Inggris ini dikutip dari DETIK.com, 28 April 2014.



Detik Pos Indonesia

Senin, 28 April 2014

Detik Pos Indonesia


Hasil Liga Inggris: Chelsea Bungkam Liverpool di Anfield 2-0

Posted: 27 Apr 2014 03:03 PM PDT

DETIKPOS.net - Chelsea Bungkam Liverpool di Anfield. Berita Liga Inggris ini dikutip dari KOMPAS.com, Senin 28 April 2014.

Apakah Ada Iming-iming Kursi Menteri di Balik Koalisi Prabowo-Wiranto?

Posted: 27 Apr 2014 02:18 PM PDT

DETIKPOS.net - Apakah Ada Iming-iming Kursi Menteri di Balik Koalisi Prabowo-Wiranto?. Berita Politik ini dikutip dari DETIK.com, 28 April 2014.

PKS Batal Usung Capres, Bagaimana Nasib Anis, Hidayat, dan Aher?

Posted: 27 Apr 2014 04:43 AM PDT

DETIKPOS.net - PKS Batal Usung Capres, Bagaimana Nasib Anis, Hidayat, dan Aher?. Berita POLITIK ini dikutip dari DETIK.com, Minggu 27 April 2014.