Google updates: why Scout pauses changes

A few times a year Google changes how it decides which sites to show higher. The big ones are called core updates. One takes about 2–4 weeks to roll out, and during that time results jump: a page can drop from 3rd to 30th in the morning and be back by evening, because Google's servers switch to the new rules unevenly.

What Scout does. From the day Google announces a core update until 7 days after it ends, Scout does not change your published pages on its own: no automatic refreshes, no re-sent links in posts already live, no next wave of district pages. New articles go out as usual — they do not disturb what is already ranking.

Why. Editing pages in the middle of the storm is the classic way to hurt yourself: a team sees −18% on day two, rewrites a hundred titles, and a week later it turns out the drop was one Google data centre lagging behind. The pages would have come back on their own — the edits reset how they were judged, and nobody can tell any more what moved them.

What you see. A banner while it lasts, a notification and an email when it starts and when it ends. You can still change a page yourself — Scout only asks you to confirm. Spam updates do not pause anything: they punish manipulation, not an honest site.

After it ends. Give it a quiet week, then compare a full week after the update with a full week before it — not day by day. With Search Console connected Scout does it for you: a week after the end you get the report on «Site pages» and by email — noise, lost ranking, the results page took the clicks, or fewer people searched — and a month after, once more. A drop of a place or two inside the top 10 is noise; a group of pages falling from the top 10 to the third page is a real signal.