I said above that this comparison has a good reason to be. Indeed, Google has a large-scale cluster management system called — you guessed it — Borg . It “…runs hundreds of thousands of tasks, from thousands of different applications, on a number of clusters, each comprising up to tens of thousands of machines.”
Additionally, some people at Google left to get into the microservices space and create a technology to connect different services into a coherent application. They codenamed this system “Project 7”, after the famous Borg character from Star Trek “7 of 9” that was under development, and although I’m not sure, I think I know why the name of this product (Kubernetes) starts with “Kube”…
It was a very nerdy background
Before we continue, here’s a quick video of the Borg Queen , where she freely discusses her role. This will give us a short break before we dive belgium telegram data back into the major updates.
Optimization for Google (not for the user)
The reason we’ve come this far is because. I’ve always believed it’s important to understand. Not just how to optimize, but what you’re optimizing for. And no, it’s not the user. It’s google.
And before a bunch of seos jump. Down my throat with quotes from john mueller and even. My own past comments about optimizing for users being a. Surefire path to higher rankings, let me tell.you that our job as seos is to rank well. And that means optimizing for google.
THEIR job is to optimize for users.
So yes, indirectly, we optimize for users, and it’s important to remember that, especially in the context of major updates lately, but words matter. Never take your eye off the ball and don’t forget what your role is.
Let’s get back to what a major optimization is and what it consists of
We can hardly talk about preparing your site for a major update without first exploring what it is, especially now that we know how the Core michael dulin chief clinical officer for analytics and outcomes research differs from other algorithms and functions.
A major update is, basically, an update of the base of the system itself, but not necessarily all of its individual components, or even many of them.
Areas that can be improved include:
- Infrastructure (eg: Caffeine ) – A major update may be more about how pages and data are indexed than how they are ranked.
- Improve language understanding (e.g. Hummingbird ) – A major update might involve reorganizing how information is understood and processed, rather than how signals are weighted. Basically, it’s about database d changing the input to the sub-algorithms rather than the output. Note: “sub-algorithm” is my term, not theirs, as far as I know; so you may not find it elsewhere.
- Merging Algorithms (e.g. Penguin 4.0 ) – At some point, it may seem better to integrate sub-algorithms into other algorithms. With Penguin 4.0, we saw a major update that took a rarely updated algorithm and integrated it into the permanent core.
- Broad signals (e.g. Medic ) – a major. Update may adjust how broad signals are.calculated. An adjustment to an individual.quality or confidence signal weight/algorithm. Would not be a core update. But with medic, the core was adjusted to reconfigure. How the entire system for assessing confidence. And quality for ymyl sites worked. Which certainly included adjustments to how. The various algorithms shared information.