News for hackers. Stuff that matters.
Re:Lyft for Work by akavi on Friday December 05, 2014 @03:02AM (#8703389)
Google crawlers have been able to execute javascript since at least May of this year[0].

[0] http://googlewebmastercentral.blogspot.ca/2014/05/understand...

Re:Lyft for Work by mootothemax on Friday December 05, 2014 @06:18AM (#8703920)
Google crawlers have been able to execute javascript since at least May of this year[0].

As I wrote in another comment, that hasn't stopped Google requested pages via _escaped_fragment_.

Re:Lyft for Work by xyby on Friday December 05, 2014 @03:08AM (#8703405)
Interesting. The content must have changed recently then. Because I see different text in the Google serps then on the page with js enabled.

For lyft.com Google shows me "Lyft is your friend with a car" which is not on the page.

For lyft.com/stories Google shows "Discover extraordinary stories from the Lyft community" which is also not on the page.

Maybe it's from good old metatags. The have some, but somehow they apply a scripting engine (angular?) to them:

    <meta property="og:title" content="{{meta.title || 'A ride whenever you need one' }}{{meta.signoff || ' - Lyft'}}">
The "Discover extraordinary stories" text is not in the metatags though.
Re:Lyft for Work by fnom on Friday December 05, 2014 @03:58AM (#8703507)
they dont necessarily give the google bot this version of the page. its perfectly ok to prerender the page with something like phantomjs and send the crawler the prerendered pages. this was , to my knowledge, quite common with angularjs apps that relied heavily on seo/google juice.