This is unusual…and Google hasn't explained more about it (for obvious reasons). Quick overview of a dual-core update: In this article, I will provide a list of quick facts based on what I see on the affected sites. First, here's a quick table of contents in case you want to jump around the post. Contents: Rolling out July and June core updates. Illustrator Art Work It's time to see the impact. Reversals from June. The June and July core updates were distinct and unique. Tremors. Health and medical sites. Financial sites. Sites with the same or nearly duplicate content. Category adjustment based on product reviews update flaw.
Rollbacks of previous general kernel updates. Product review sites. Spam updates. Impact of rich snippets. A note on Core Web Vitals. Illustrator Art Work The "Kitchen Sink" approach to sanitation. Site-level quality signals. Latest tips and recommendations. General June and July Update Rollout: The June Update started rolling out on 2/6 and ended on 12/6. It was quite fast for a large baseline update, which can sometimes take up to 14 days to fully roll out. The July General Update started rolling out on 7/1 and was completed on Monday 7/12. So the July update took 12 days to fully roll out, closer to what we normally see with extended core updates.
And I should mention the dates of other Google algorithm updates rolled out since early June. Site owners should be aware of these dates to ensure that they see the movement of general core updates and not others. Illustrator Art Work Google started rolling out the long-awaited Page Experience update on 6/15, but it will be slow and won't be fully complete until the end of August. Also, Google explained that Page Experience Signal would be a lightweight factor (more of a deciding factor). So if you see a big move in June and July, it's probably not coming from the