Google Search Ranking Volatility Heated On November 12th
Briefly

Google Search Ranking Volatility Heated On November 12th
"We are seeing significant movement and volatility in the Google Search results again, with this one kicking up more yesterday, November 12th. This may be a continuation of the ongoing Movember update, which I covered over the weekend. But there has been a lot of chatter over the past day or so, and some of the tools spiked over the past 24 hours."
"Today was disappointingly interesting. I have two websites, one of which has an 11-year-established background (over 10k products) and the other with hardly any backlinks (less than 1k products). My established website, which gets easily 20-30 new signups and about 20 sales every day, received 3 signups so far. Meanwhile, my other website, which usually receives a sale every other day, had 6 sales in one day today ... So obviously something's up ..."
"The last time we reported on Google ranking volatility was what I called the Movember update around November 8th and then the Halloween update and then between October 15th to 17th and then on October 7/8th and to be honest, there has been a lot less chatter since Google turned off the ability to see 100 results per page and the tools began to recalibrate."
Significant movement and volatility in Google Search results occurred on November 12, possibly continuing the Movember update. Several ranking-tracking tools spiked over 24 hours. Google Search Console performance reports have not fully updated since Monday, and GA4 real-time reporting experienced a break, complicating tracking. Previous volatility events included Movember (around Nov 8), Halloween, and mid-October fluctuations, with a notable adjustment around October 16. Removal of the 100-results-per-page view led to reduced chatter and tool recalibration. SEO community reports include major traffic drops, low Discover traffic, conversion declines on established sites, and unexpected sales gains on smaller sites.
Read at Search Engine Roundtable
Unable to calculate read time
[
|
]