Author Archive
Twitter Camp Madurai 2010
The first twitter event for the year 2010 is finally announced by Dot Com Infoway. They have decided to host the TwitterCamp in Madurai, India. Normally we don’t see such event organized in small town and this seems to be a good start for twitter enthusiast in Madurai.
Any Form of Paid Links = SPAM by Google
It is a well known fact that Google considers paid links as SPAM and website’s PageRank were penalized few years back for paid links. With this there was various consideration in getting paid links that experts used to share that the links shouldn’t be named as sponsored/paid links so that crawlers can identify and similar conditions.
Search MeetUp Bangalore 2009 – Round Up
The first ever Search Meetup that took place on Friday, October 30, 2009 in Bangalore which was hosted by Crederity & Digital Marketers is an interactive session with Gillian Muessig (SEOmom). The event kicked off with an introductory among the participants and a small SEO tip session due to the delay by speaker to the event. If you think you had missed a great tip I would say ‘No’ it is again the old SEO story “Content is the King” that came from most of the participants. With few tips going on a sudden shift to this is the entry of the SEOmom to the event.
HTTP Status Codes and Search Engines
Server Status code are the number values of the HTTP request. It is important to understand the different server status code that will be useful in the SEO perspective and how search engines bots react to the same.
Before getting into the server status codes it is important to understand the difference between HTTP /1.0 and HTTP/ 1.1 protocols. The HTTP/1.0 protocol has been stunningly successful and as a measure of its popularity, HTTP accounted for about 75% of Internet backbone traffic. In spite of its success, however, HTTP/1.0 is widely understood to have numerous flaws. To overcome the flaws in HTTP/1.0 the HTTP-Working Group (HTTP-WG) developed an improved protocol, known as HTTP/1.1. This specification states the various requirements for clients, proxies, servers and later became an Internet Engineering Task Force (IETF) Draft Standard. The server status code tends to differ based on the version of the HTTP.
