Barry has details of what looks like an initiative by Google to index JavaScript. Is the Googlebot trying to find the hidden web?
Similar Stories in: General | Forward: Email This Post
Similar posts you may like...
1 comment on “Google Trying to Index JavaScript?”
- Google Search Share Stays Steady As Microsoft and Yahoo Wrestle for the Rest
- Chrome for Android Beta Arrives
- Majority of Users Say Social Networkers Are Kind and Caring
- The Sharing Economy: Could It Be the Next Big Thing?
- Groupon’s First Public Quarter Is No Deal for Investors
- Compete Says Google+ Is Becoming An Enormous Success
- Win Copies of Brian Carter's "The Like Economy: How Businesses Make Money With Facebook" - 32 comments
- Google's Not Focusing On the User! Waah Waah Waah, Cry Me a River! - 17 comments
- Reputation Watch: Zappos Security Breach Tests Internet Giant - 16 comments
- Facebook's Real Problem in Just 44 Words - 14 comments
- Revenue Starts to Figure Into Social Media ROI - 11 comments
- Marketers To Invest in Blogs in 2012 - 10 comments
- Will 2012 Become the Year of Mobile SEO? - 9 comments
- 5 Marketing Tips from the Social Commerce Summit - 9 comments
- Is Google a Public Company or Part of the Public Domain? - 8 comments
- Blogging Declines in Inc. 500 Survey - 8 comments
Ammon Johns Says:
March 20th, 2006 at 8:39 am
Googlebot first came to my notice for starting to interpret JavaScript back in late 2000 or early 2001 when it gained the ability to detect JavaScript redirection used on-page.
At that time, it wasn’t very advanced, and caused pages with frame-busting or frame-loading javascripts to suffer problems. Since that time, I have used external JavaScript files for everything but a few test sites. Thankfully, this early JavaScript detection (and penalization) was turned off within months.
However, it naturally highlighted Google’s interest and ambition in having a robot that could interpret various JavaScript functions. I’ve never allowed it to slip my mind since, and I’m sure that Google haven’t either.