Googlebot now makes POST requests via AJAX(thumbtack.com)
thumbtack.com
Googlebot now makes POST requests via AJAX
http://www.thumbtack.com/engineering/googlebot-makes-post-requests-via-ajax/
45 comments
I run a site which triggers POSTs via Ajax for visitor tracking. We explicitly disable crawling of the Ajax directory via robots.txt and have not observed Googlebot crawling these URLs. Strange that Googlebot behaves differently for you.
These don't seem like crawlers, but rather proxies requesting information on behalf of a user (perhaps with that user agent that is in the UA string). Those are "Google bots", but they aren't the Googlebot.
From the blog post:
The source of the requests is our client-side JavaScript error tracking code, which installs a global JavaScript error handler and attempts to POST to our server when unhandled errors are detected on the client.
Sounds like Googlebot's executing more advanced Javascript, though it's pretty scary it's allowing POSTs to go through.
The source of the requests is our client-side JavaScript error tracking code, which installs a global JavaScript error handler and attempts to POST to our server when unhandled errors are detected on the client.
Sounds like Googlebot's executing more advanced Javascript, though it's pretty scary it's allowing POSTs to go through.
I think it'd be silly to block POSTs in cases like this. The page makes an unsolicited POST. It's quite reasonable for any crawler to do the same. How else would they get an accurate representation of what the user sees?
Now, if Google is sending random forms, as another commenter claims, that's a different case. But unsolicited POSTs coded in the page's scrips? Send 'em.
Now, if Google is sending random forms, as another commenter claims, that's a different case. But unsolicited POSTs coded in the page's scrips? Send 'em.
I believe the HTTP spec defines a GET as a representation of a resource and a POST as modifying or updating a resource, so google bot doing POSTS is not very neighborly.
By that definition, unsolicited POSTs are not very neighborly.
I don't see how. Updating a view count or putting a pin on a "countries that have visited this page" map is fairly benign. Trying to randomly scribble on somebody else's data is not.
If all the Googlebot is doing is executing the JS as an arbitrary user's browser would, and part of that page load JS involves doing a POST, I can see the argument for doing it.
Agree. Otherwise a page could dynamically load html via AJAX and give a totally different view to a user than what google-bot sees.
I noticed this a few days ago. I'm actually considering POSTing the screen dimensions and a few other browser properties for Googlebot via js.
https://twitter.com/#!/lm741/status/122378906669023232
https://twitter.com/#!/lm741/status/122378906669023232
I like your idea. Let's find out something about what the Googlebot is "seeing" and log the POST requests in a database table.
Surely you can do this with GET with minor server trickery? (Has such been done already?)
Correct. The richness of the Javascript environment for Googlebot is probably a more significant discovery than the POST requests. I previously pretty much assumed that bots didn't really run Javacript. (Or at least that they would kill network access before running it)
This is a bit annoying. My company has an IRC bot that notifies us when someone fails to properly fill out an important AJAX POSTed form on our front page and soon found out all the "errors" we were seeing on IRC were generated by googlebot.
No crawler should perform POST requests. it is simply bad etiquette and it is understood that POST requests are typically used to create/change/delete content or affect the environment.
Don't write unsolicited POSTs into your page if you don't want crawlers to execute them. I think Google's doing the right thing in this particular case. If a post is happening automatically for all users, then crawlers must do it to ensure they get the same view.
I wonder what this means for SEO? If they are actually fully rendering pages in javascript I guess that means you have to be a lot more careful about how pages are laid out.
This definitely is important in terms of how much "value" Google assigns to links on the page, if they can identify where they render. They got a patent for varying the amount of page rank that flows to a link based on how likely the "reasonable surfer" is to click it. So in terms of flowing Pagerank to a bunch of high value landing pages via a slew of footer links, it's game over.
My only question is how frequently Googlebot actually renders the full JavaScript. Surely they don't have the computing resources to render it on every crawl.
Link to patent discussion: http://www.seobythesea.com/2010/05/googles-reasonable-surfer...
My only question is how frequently Googlebot actually renders the full JavaScript. Surely they don't have the computing resources to render it on every crawl.
Link to patent discussion: http://www.seobythesea.com/2010/05/googles-reasonable-surfer...
Surely they don't have the computing resources to render it on every crawl.
Why do you think this? They had the computing resources to randomly generate billions of mutations of compiled Flash programs to find bugs in the Flash VM.
Why do you think this? They had the computing resources to randomly generate billions of mutations of compiled Flash programs to find bugs in the Flash VM.
They seem to have been doing this for a while, google bot was running a tracking js that gets dynamically loaded and communicates to an iframe using postMessage which then sends ajax. If it is doing that, you would assume it's doing most of everything a browser does now.
As a corollary, does this mean that the googlebot now reads pages generated by javascript? I remember that you needed to follow their ajax guidelines, as well as generate the actual page on the server, but if they're able to run javascript on pages now, does this mean they let the page render first (or with a delay of some sort) before parsing it?
That would be cool.
That would be cool.
I wonder if you could add your POST URLs to robots.txt if you don't want the crawler to access them.
If other crawlers start doing this, it should probably be added to robots.txt formally.
If other crawlers start doing this, it should probably be added to robots.txt formally.
I'm an engineer at Thumbtack. And yes: we have noticed that Googlebot does seem to obey robots.txt even when issuing these AJAX requests.
According to google they can to some length read you ajax but you to follow some guides.
http://www.google.com/support/webmasters/bin/answer.py?answe...
That's a little spooky. I wonder how many people have AJAX posts for handling deletes?
In order to delete any content owned by a user, the Google bot would have to have logged in as that user first, which seems unlikely - so long as all destructive actions are behind access control, which they definitely should be already.
This is very far from true. Failing to implement access control or even authentication on POST is a routine error even in applications built in the last couple of years.
Well, maybe not for much longer...
Less facetiously: the Googlebot isn't making random POST requests, it's just executing Javascript on the page. So not only would you need an unprotected POST /comments/1234/delete endpoint, you'd also need to serve the UI and Javascript for POSTing to that endpoint to an unauthenticated user.
I'm sure there are still people out there doing that, but at least it's more than a simple error of omission.
Less facetiously: the Googlebot isn't making random POST requests, it's just executing Javascript on the page. So not only would you need an unprotected POST /comments/1234/delete endpoint, you'd also need to serve the UI and Javascript for POSTing to that endpoint to an unauthenticated user.
I'm sure there are still people out there doing that, but at least it's more than a simple error of omission.
I agree that this Googlebot change is unlikely to be the end of the world.
Well, maybe not for much longer...
I wonder how much the Google Web Accelerator debacle made people realize that GET is supposed to be idempotent.
Perhaps Googlebot will do the same for POST and authentication.
I wonder how much the Google Web Accelerator debacle made people realize that GET is supposed to be idempotent.
Perhaps Googlebot will do the same for POST and authentication.
It definitely requires that you be more vigilant in the design of something like crowdsourced flagging, though.
http://thedailywtf.com/Articles/The_Spider_of_Doom.aspx
I think this is more common than you believe.
I think this is more common than you believe.
Does it only do POSTs that are in the document's onload handler, or also things that are in onclick? I think that the latter could be dangerous
<a href="#">Delete</a>
<a href="#">Delete</a>
Why would you let an anonymous visitor to delete a data just by clicking a link?
Would it click facebook Like, too? ;)
Nonetheless, there have been some more recent Google "bots," including the POST in question, that may be of interest to those that track those metrics -- remove those requests from internal reports.
Requests:
UserAgents (Google "bots"):