Google guys are just too good

I think you guys must have had a real good experience searching on Google. No wonder they have a very good algorithm but then that too us susceptible to spam so you cant really have 100% reliability on that. That was the question that made me think that googlrithm is more complex than what it seems. And yesterday night I got that light from my thinking bulb. At first when Google introduced Google Sitemaps and Google Analytics. No one would have suspected it to have any consequences on search. But now I realize that the assumption is perhaps wrong. So heres my hypothesis on how Google makes it happen.

Well every webmaster now by default goes to Google Sitemaps to get his site in the list. The webmaster would get information like his indexed pages, when his page was indexed and what searches picked up his pages and at what rank. It also records for which searches his site was visited. Great now you know who visited your site for what result. But then Google also knows. From here Google Analytics takes over. It records how long was the user there before he moved on. That too determines how useful your page was. Very simple but effective most of the time. Also Google Analytics would let the search engine know what is the usual time a visitor is at the site. So you get a higher ranking for more the number of visitors and longer they spent on your site. A spam site would never get visitors to spend anything more that 5seconds and if you have most visitors staying for real short period then your ranking gets a good hit. A very simple solution indeed all while giving the webmasters a feeling of serving them well. Ironically it does that too well. Google Sitemaps and Google Analytics are both such good tools that they leave competition miles behind. Great going Google.

Comments

Sohny said…
Interesting that... sounds simple
October 17, 2007 2:57 PM
Post a Comment

Popular posts from this blog

[24th November 2024] Interesting Things I Learnt This Week

Image
1. AI Makes Tech Debt More Expensive - The core argument is that generative AI significantly widens the gap between codebases with low and high tech debt. Companies with clean code can leverage generative AI to write code much faster, while companies with messy legacy codebases struggle to adopt these new tools. This widens the gap between the two codebases, making tech debt even more expensive for companies with outdated systems. My Take : Legacy systems inevitably accumulate technical debt. A common analogy for this is the state of urinals over time: missed targets lead to increasing mess, keeps pushing people away from urinals and leading to more mess in turn. AI-powered coding tools could potentially accelerate the accumulation of tech debt. However, skilled engineers can leverage AI to reduce and even eliminate it. Ultimately, AI is just a tool, and human judgment remains crucial for making informed decisions. I hope AI will be used responsibly to drive positive outcomes. 2. Make...
Read more

[17th November 2024] Interesting Things I Learnt This Week

Image
 1. Booleans are a trap : Booleans, while seemingly simple, can introduce complexity and limitations into domain modeling. When used to represent complex states, booleans can lead to unclear code and potential errors. To avoid these pitfalls, consider using enums or enum sets. These approaches provide a more expressive and maintainable way to model complex states in your applications. My Take : I wish I had learned this earlier in life. When working with Google Docs, I realized the limitations of booleans. Expanding boolean-based behaviors often led to adding more fields, making the system complex. Enums would have provided a simpler solution. The problem wasn't just the booleans themselves, but also the need to pass them through multiple layers of the stack, often requiring additional parameters. Another important aspect of enums is the inclusion of an " enum not specified " state. This state explicitly indicates that an enum value hasn't been set, which can be usef...
Read more

[1st December 2024] Interesting Things I Learnt This Week

Image
1. C++ Pitfalls - this article, explains some of the pitfalls you can fall into when programming in C++ and shares their experience with them. This includes Operator precedence, Arithmetic conversion rules, Right bit-shift, Implicit conversions and Order of evaluation.  My Take : We've all read about JavaScript's quirks, leading to unexpected outputs. But let's remember that such behaviors aren't unique to JavaScript. Even languages like C and C++ have their share of ambiguities and compiler-specific behaviors. While it's tempting to dive deep into these intricacies, I've found that focusing on clear, consistent, and unambiguous code is often more practical. However, understanding these nuances is essential for any experienced programmer. It helps us avoid pitfalls and write robust, reliable code. Remember, mastering a language isn't just about writing "Hello World." It involves delving into its intricacies, including its counterintuitive and ambi...
Read more