My First Experience with Twitter Chat

This past Thursday, at exactly one O’clock P.M., I logged onto Twitter to participate in my first ever Twitter Chat. Always the technological laggard, my reluctance to participate in such a phenomenon was mostly due to my ignorance of it.

My veil of ignorance was lifted upon my enrollment in the Social Media Management class at the University Of Florida, taught by Professor Lisa Buyer. There have been new social media-related things that I have been mandated to do for this class, from creating accounts on the scheduling/analytics platforms of Hootsuite and Buffer (although my trial for the latter just ended, and I do not see myself paying the 10$ a month membership fee), to writing articles on Medium, which I am doing now.

The Twitter Chat that I tuned into was #seochat. SEO, or Search Engine Optimization, is a topic that I was (who am I kidding, I still am) completely in the dark on. Basically, the reason I decided to participate in this chat over any of the other multitudes that may have been going on was that I knew it was scheduled, and I knew it fit into my schedule.

The topic of this particularly chat was, as moderator Matthew Young from Adobe put it, “how well or poorly JavaScript and SEO get along,” a topic which right away alerted me to the fact that I was less-than-an-amateur, in a chat of SEO industry professionals (tweet). Luckily, this seems to be what the Twitter Chat model is all about. A few other people also came out as first timers Nonetheless, as far as I knew, JavaScript was a font favored by baristas.

The first question was whether SEO and JavaScript can get along. J.P. Sherman, from RedHat.com, seemed to think so, so long as Java, “doesn’t block indexing,” “contributes User Interface/User Experience”, and “doesn’t hide content”.

The second question regarded Google’s position on crawling and executing JavaScript on the page. Luckily, someone else asked what crawling and executing was, and Matthew responded by explaining that it was, “when google bot approaches a page it crawls that HTML document in order to save it to the index”. He continued to explain how, “Google also has the ability to execute files associated with a webpage, like JavaScript files.”

I could wrap my mind around some of these ideas, but from the third question on it was apparent that I was in over my head.