How quickly can an SEO company respond to algorithm changes?
It should run on two clocks. Attention should be fast: the company should know when an announced update has started and begin watching your figures, on a schedule you agree in advance. Changes to your site should be slow: apart from genuine errors, nothing should be rewritten or removed until the update has finished rolling out and the data has had time to settle. Confusing the two clocks, by editing pages in the middle of a rollout, risks reacting to movement that would have reversed on its own.
The fast clock: attention
Google lists its announced ranking updates, with start and end times, on its Search Status Dashboard. A company that follows it knows when an update begins and can start recording how your pages and queries move in Search Console from the first days. You should hear early, in plain terms: an update has started, this is what we are seeing so far, and this is when we expect to be able to judge it. Agree beforehand how soon you will hear from the company once an update starts; a company that cannot say whether your traffic moved is not watching closely enough.
The slow clock: changes
Rollouts take time: on the same dashboard, the five most recent core updates, from March 2025 to May 2026, each took between 11 days 21 hours and 18 days 2 hours to complete. During that period positions can move back and forth, and a page that drops in the first week may recover in the second without anyone touching it. Google’s guide to core updates advises waiting until an update has finished and then allowing a further week before comparing your figures with the period before it began.
So the sensible sequence is: monitor and document during the rollout; wait for completion and the further week; then compare, diagnose, and plan. On that timetable, the earliest well-founded change to your content comes some weeks after an update starts, which is the right pace, not a slow one.
What should not wait
Two kinds of problems should be fixed as soon as they are found, update or not: factual errors on your pages, and technical faults such as pages accidentally blocked from indexing, broken redirects, or a template that stopped rendering properly. These are not reactions to the update; they would need fixing anyway, and the update is simply when someone looked.
Testing a company’s answer
Ask how the company tracks announced updates, how soon it will tell you what it sees, what it will and will not change during a rollout, and how it decides when the data is reliable enough to act on. An answer that combines prompt communication with unhurried changes describes a company that puts reliable data ahead of the appearance of speed.