Rankings swing in the first weeks because Google is actively testing a new page’s position, then they stabilize once that evaluation reaches a verdict. When a page is fresh, Google has little real-world data on how searchers respond to it, so it gathers signals by trying the page at different placements and watching what happens. The early volatility is that testing in progress, and the eventual settling is the conclusion the system arrives at after it has seen enough. The wobble is not a malfunction; it is the evaluation running.
The mechanism is that ranking a new page is partly an experiment. Google forms an initial estimate from on-page and link signals, places the page somewhere, and then observes how it performs against the existing results, whether searchers engage with it, how it compares to neighbors, how it holds up across crawls. Based on what it sees, it adjusts the placement up or down, sometimes sharply, because a small amount of early data can swing the estimate. As more data accumulates, each new observation moves the estimate less, the adjustments shrink, and the position converges. That convergence is the stabilization you observe.
This reframes what the early swings mean. A page jumping from page two to page five and back is not telling you the content is broken or that something needs urgent fixing. It is telling you the page is still being placed, with the system trying positions to gauge response before committing. Reacting to those swings, rewriting, re-optimizing, or panicking mid-test, risks changing the very thing being measured and resetting the evaluation, which can prolong the instability you were trying to end. This is observed behavior rather than a documented dial, so treat the pattern as something to recognize, not a guaranteed sequence.
So when a new page fluctuates in its first weeks, recognize it as the evaluation in progress and hold off on reacting. Let the page accumulate the data Google needs and wait for the position to stabilize before judging it, since the verdict only arrives after the testing finishes, and intervening early often just restarts the clock.