SEO
SEO Resolution for the Year 2010
New Year Resolution is the traditional one and which does not go well with me. To speak frankly, I think about having a great and energizing New Year resolution every year but when the clock ticks, I don’t think I take the decision move with me. This is purely personal when comes to business /career everyone wants to be in better shape compared with last year.
I take this space to widespread my SEO Resolutions for the Year 2010. Read the rest of this entry
7 Secrets to Make Your SEO Clients Happy
Success of every business comes from the satisfaction of the customer. As we all involve ourself in SE Optimization / Marketing process it’s vital to get satisfaction from the clients. By setting the proper propositions right from the start in the project you can easily create and manage a successful SEO project. This even applies for the people those who run in-house SEO campaigns, through which you can make your Boss / CEO happy with the SEO campaign results. Lets discuss few things which can be done with due plan and implementation which makes the clients happy!
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.
