Googlebot's recent improvements might revolutionize web development
1–10 of 97 posts
Re: Googlebot's recent improvements might revolutionize web development
#2I'm not sure if this announcement changes anything. The bottom line is to make apps for the end user. Google is simply saying that those best practices are now crawlable in a way that is very mature. The same rules still apply.
A simple guide can be found here: https://developers.google.com/webmasters/ajax-crawling/. Although I suspect it needs to be updated since its from 2012.
If you create an application, make sure it alters the URL when applicable. For simple apps, the following repos will be useful:
The old way, that still works: https://github.com/asual/jquery-address
The better way, preferred: https://github.com/browserstate/history.js or https://github.com/defunkt/jquery-pjax.... not sure which is better to be honest. Feel free to chime in.
Re: Googlebot's recent improvements might revolutionize web development
#3I'm not sure if this announcement changes anything. The bottom line is to make apps for the end user. Google is simply saying that those best practices are now crawlable in a way that is very mature. The same rules still apply. A simple guide can be found here: https://developers.google.com/webmasters/ajax-crawling/ . Although I suspect it needs to be updated since its from 2012. If you create an application, make su…
fixed link: https://github.com/defunkt/jquery-pjax
Re: Googlebot's recent improvements might revolutionize web development
#4We're still using hypertext transfer protocol, right? You need to send hypertext down the wire.
We shouldn't let one company, google, dictate how the web works, simply because of their proprietary technological innovation.
Re: Googlebot's recent improvements might revolutionize web development
#5I wouldn't actually call this "recent" improvements. I mean, Google has been handling JavaScript for years now. And they're just now coming out and publicly saying it. Which is typical Google.
Re: Googlebot's recent improvements might revolutionize web development
#6We're still using hypertext transfer protocol, right? You need to send hypertext down the wire. We shouldn't let one company, google, dictate how the web works, simply because of their proprietary technological innovation.
Roads are meant for horses, right? We shouldn't let one company, Ford, dictate how the roads work.
My man, if we only used infrastructure and technology in the way it was originally intended and narrowly imagined, the world would be a dim place.
Re: Googlebot's recent improvements might revolutionize web development
#7One potential problem here is that google will use this to widen the gap between it and the 'one page apps' web and other search engines (such as duckduckgo) that can't match it in resources.
How strong of an advantage that will be in the long run is uncertain, I would rather see a web that ships pages with actual content in them than empty containers for a variety of reasons (most of which have to do with accessibility and the fact that not all clients are browsers or even capable of running javascript).
This 'new web' is going off in a direction that is harmful, coupled with the mobile app walled gardens it is turning back the clock in a hurry.
I'm fairly sure this is not the web that Tim Berners-Lee envisioned.
Re: Googlebot's recent improvements might revolutionize web development
#8Taking a step back: The "Page" paradigm is still very much alive, despite these recent javascript parsing advances.
1. Google still needs a URL-addressable "PAGE" to which it can send Users.
2. This "PAGE" needs to be find-able via LINKS (javascript or HTML) and it needs to exist within a sensible hierarchy of a SITE.
3. This "PAGE" needs to have unique and significant content visible immediately to the user, and on a single topic, and it needs to be sufficiently different from other pages on the site so as not to be discarded as duplicate content.
Re: Googlebot's recent improvements might revolutionize web development
#9We're still using hypertext transfer protocol, right? You need to send hypertext down the wire. We shouldn't let one company, google, dictate how the web works, simply because of their proprietary technological innovation.
Google is not dictating anything so there is no need to vent your dislike, of, Google, in that way. If anything, this releases developers from a constraint on how sites are built.
That said, I'd rather see more server-side HTML instead of client-side JS when it comes to the web. If you're developing a game, client-side JS is fine. If you're serving textual content with the odd image, please serve it in the way the web was won: HTML. Use CSS if you feel the need for some 'style', but remember that perfection is reached when there is nothing left to take away, rather than nothing more to add.
Re: Googlebot's recent improvements might revolutionize web development
#10We're still using hypertext transfer protocol, right? You need to send hypertext down the wire. We shouldn't let one company, google, dictate how the web works, simply because of their proprietary technological innovation.
Not to sound like a complete troll but, uh, how should i send this gif to the client?