GET, POST, and safely surfacing more of the web
googlewebmastercentral.blogspot.com
googlewebmastercentral.blogspot.com
Google begins indexing yummy-sundae.html and, as a part of
this process, decides to attempt to render the page to
better understand its content and/or generate the Instant
Preview.
this is the first time ever that google confirms that they are internally rendering the page - not only for preview purposes - but also for indexing purposes. >Remember to include important content (i.e., the content you’d like
>indexed) as text, visible directly on the page and without
>requiring user-action to display. Most search engines are text-
>based and generally work best with text-based content. We’re always
>improving our ability to crawl and index content published in a
>variety of ways, but it remains a good practice to use text for
>important information.
first time ever they advise - directly - against "user action dependent hidden content"I wonder if another implication of Google actually rendering pages is that SEO is going to have to focus much more heavily on visible page content rather than hidden or quietly shuffled out-of-sight content.
google says they will only post POST request that are automatically triggered onpageload and will have no other side effects other than (fetching & ) rendering content.
ok, lets say google does 1000 000 000 POST requests and gets it 99.999% right. this means that there will be 1 000 000 occurrences where google actually will trigger some unintended side-effects.
"At scale everything breaks" (c) Urs Hölzle http://www.zdnet.co.uk/news/cloud/2011/06/22/google-at-scale...
http://www.thumbtack.com/engineering/googlebot-makes-post-re...