|
|
Hummingbird A core update may mean how information is understood and processed, rather than how signals are valued. Basically, the input of the sub-algorithms is changed, rather than the output. Note: "sub-algorithm" is my own term, not theirs, and as far as I know, you won't find it mentioned anywhere. Merge Algorithms (ex – Penguin ): At some point, it may seem better for sub-algorithms to be integrated with others.
With Penguin , we saw a core update that took an infrequently updated algorithm, built into the evergreen core. Broad Signals (ex – Medic ): A core update can adjust how broad signals are calculated. Using the Medic India Phone Number Update as an example, an adjustment to an individual quality or weight signal/algorithm would not be a Core update, but with the Medic, the Core was adjusted to reconfigure how the entire trust and quality system worked for.
YMYL , which It certainly included adjustments to the way different algorithms shared information. EAT (ex – Google Warning): On its blog , Google specifically warns that sites negatively impacted by Core Updates need to pay attention to EAT . It makes sense when we think about the variety of signals needed to evaluate EAT. They could not be captured in a signal algorithm; They require multiple algorithms working together in multiple areas on and off the site. To do this, you need to update the Core, updating the basis of how the other parts work together.
|
|
發表於 14:09:03