Rankings move, and the first instinct is to change something immediately. That instinct is almost always wrong, and acting on it is how a temporary dip becomes a permanent one.
Core updates, including the Google March 2025 core update, are broad revisions to how quality and relevance are assessed. They are not penalties. Nothing has been done to you, and there is no specific violation to correct.
Which means the useful response starts with diagnosis rather than action, and requires more patience than most people have available.
Google March 2025 Core Update: Navigating Ranking Volatility
1. Wait for it to finish
Core updates roll out over one to two weeks, and rankings fluctuate throughout. What you see on day three is not where you will land.
Changing things mid-rollout means you cannot attribute anything afterwards. You will have altered several variables during a period when the ground was already moving, and you will never know which mattered.
Note the dates, watch, and resist.
Then work out what actually happened
Look at Search Console rather than a rank tracker, and compare a period after the rollout completes against an equivalent period before.
Ask four questions.
- Which pages moved? A handful of pages behaving differently is a content issue. A site-wide shift is something broader.
- Which queries moved? Losing informational queries while retaining commercial ones tells a very different story from the reverse.
- Did impressions or clicks fall? Falling impressions means visibility declined. Steady impressions with falling clicks means something changed in how your result is presented, which is increasingly common as generated answers occupy more of the page.
- Did competitors gain, or did the query itself change? Sometimes a query stops returning what it used to for everybody.
What to prioritise if content is the issue
Core updates repeatedly favour depth, accuracy and genuine usefulness over volume.
Look for pages that skim a subject without answering it, near-duplicate pages competing with each other, content written to a keyword rather than a question, and pages that are simply out of date.
Consolidating several thin pages into one substantial page is frequently more effective than improving them individually. It also reduces the number of pages competing with one another for the same query.
Google publishes guidance on creating helpful content and the self-assessment questions in it are more useful than most third-party commentary about any given update.
The technical floor
Technical health rarely causes a core update decline on its own, but it constrains recovery. A page that cannot be crawled reliably cannot be reassessed favourably, however much you improve it.
Check crawlability and indexation first, then page speed on your most-visited pages under stated conditions: which device, which connection, first or repeat visit. Confirm that important pages are actually indexed rather than assuming, since exclusions accumulate quietly through redirects, canonical tags and robots rules nobody revisits.
Where performance and environmental impact both apply, treat them as the same lever: reducing unnecessary data transfer and processing supports a faster experience while lowering estimated digital carbon, though environmental figures remain modelled rather than directly measured.
None of this substitutes for content quality. It removes the obstacles that would otherwise prevent improved content from being seen.
Recovery, realistically
Improvements made after a core update typically take effect during a subsequent one, which may be months away. There is no reconsideration process because there is no penalty to appeal.
Some sites do not return to their previous position, and that is worth saying plainly. If the update reflected a genuine reassessment of quality relative to competitors, the previous position may not have been sustainable.
Anyone guaranteeing restoration is describing something outside their control. What is within your control is producing better material than the alternatives, which is the same answer as before the update.
Our search engine optimisation work starts by diagnosing what actually moved, since acting before that is how recoveries get delayed.