Spiderable returns empty body #721
Comments
Spiderable only works for requests that match AJAX Crawl Specification ( https://developers.google.com/webmasters/ajax-crawling/ ). Try doing curl http://meteorrain.meteor.com/?_escaped_fragment_= |
Thanks @erundook, I've read the google spec - So spiderable is only usefull for ajax enabled crawlers actually setting the Just for the fun of it I tried setting a fictive parametre in fb link eg. Would it be possible to check the agents and eg. set the |
@raix you could do that (useragent detection) with some kind of reverse proxy (nginx for exapmle). |
@erundook : nope, dont have to use proxy, I just have to make the |
@erundook: Guess facebook's user agent changed from lower case to CamelCase - the spiderable only tested lower case. Spiderable only supported the fb bot. I've fixed the test and added the linkedin bot. |
@erundook: ... and thanks for your input :) |
Pushed @raix's patch. |
It would be awesome if this would be configurable on per-app basis. |
Just to clearify, |
Yes, just like that, but with a way to add agents instead of overriding the On Fri, Mar 1, 2013 at 5:25 PM, Morten N.O. Nørgaard Henriksen <
|
I'v added the spiderable package, it kinda renders - used curl to check but body is empty?
Really just needed a img tag and some text for twitter/fb to use.
EDIT: At first I tested with fb - It didn't find any img tags or text. I've read the spiderable code - can see that only facebook bot is supported and there might be an issue with node?
Knowing the spiderable is a temperary approach - Should I try fixing or try getting templates rendered serverside? (guess it would require some input from core, eg. strategy for js/non js bots - use robots.txt or only support major bots)
The text was updated successfully, but these errors were encountered: