If your rankings or traffic started moving at the end of June, the June 2025 core update is the most likely reason. Google began rolling it out on 30 June 2025 and says it may take up to three weeks to finish. So what you see in your reports this week is a moving picture, not a final result.
In this guide I cover what Google has confirmed, what a core update really changes, and what Google says you should (and shouldn’t) do while one is rolling out. I also show how I set up Search Console so I can read the impact properly once things settle.
What Google Has Confirmed About the June 2025 Core Update
Google posted the update on its Search Status Dashboard at 07:34 Pacific time on Monday, 30 June 2025. The note was short: “Released the June 2025 core update. The rollout may take up to 3 weeks to complete.”
In its posts about the update, Google called it a regular update meant to better show relevant, satisfying content for searchers from all types of sites. It also said it would update its ranking release history page when the rollout is complete.
Here is what that means in practice:
- Start date: 30 June 2025.
- Stated length: up to three weeks. That points to it ending around the third week of July at the latest.
- Status today (2 July): still rolling out. Google has not announced that it’s complete.
- Scope: a broad core update. It is not a spam update and is not aimed at any one type of site.
It is the second announced core update of 2025. The first, the March 2025 core update, started on 13 March and finished on 27 March.
Google did not share a detailed list of what changed, and it rarely does for core updates. Anyone who claims to know exactly which sites “won” or “lost” two days into a three-week rollout is guessing. I’d ignore those hot takes for now.
What a Core Update Is (and What It Isn’t)
A core update is a big, broad change to Google’s ranking systems. Google releases several a year. It announces them because they can clearly shift results across many searches, languages and countries at the same time.
The key word is broad. A core update does not target certain pages or punish certain sites. It changes how Google’s systems judge content overall. Some pages go up, some go down, and many barely move.
Core Updates vs. Spam Updates vs. Manual Actions
People mix these three up all the time, and the difference matters for what you do next.
| Type | What it does | Where you’ll see it |
|---|---|---|
| Core update | Re-checks how relevant and helpful content is across the whole index | Search Status Dashboard; ranking shifts in Search Console |
| Spam update | Gets better at spotting content and links that break Google’s spam policies | Search Status Dashboard; ranking shifts in Search Console |
| Manual action | A human reviewer applies a penalty for a specific policy violation | The Manual actions report in Search Console, with a notice |
If a core update lowers your rankings, there is no notice, no penalty and nothing to “lift”. There is also no reconsideration request (a request asking Google to review a penalty) to send. The only way back is for Google’s systems to judge your content as more helpful than the other options.
A Drop Doesn’t Mean Your Page Is Bad
Google has said for years that a ranking drop after a core update doesn’t always mean something is wrong with your page. Other pages may simply have become better matches for what searchers want.
Think of it like a new list of the best restaurants in a city. A restaurant can fall a few places without getting worse, because the list was redone with different weightings and new entries.
What to Expect While the June 2025 Core Update Rolls Out
Core updates don’t land all at once. They roll out across Google’s systems and data centres over days or weeks, and the effects come in waves.
- Rankings can swing back and forth. A page might drop on day three and recover on day ten. Early moves often reverse.
- Different keywords move at different times. One section of your site may shift this week and another next week.
- Rank trackers will look jumpy. Industry volatility tools usually spike during rollouts. That tells you the update is active, not where your site will end up.
- Other changes can overlap. Google ships ranking changes all the time. A move in early July might come from something other than the core update, or from the season.
The simple lesson: the first week of a core update is the worst time to draw conclusions about it. In my experience, the people who stay calm in week one make much better decisions later.
Google’s Guidance During a Rollout: What to Do and What to Avoid
Google’s documentation on core updates and your site is clear on one point. Most sites don’t need to do anything, and you should wait until an update has finished before you analyse it.
What Google Recommends
- Wait for completion. Check the Search Status Dashboard for the official end date before you judge anything.
- Then wait about a week more. Google recommends leaving at least a full week after the update ends, so you have clean data to compare.
- Compare like with like. Look at a week after the rollout ends against a week before it started (before 30 June).
- Focus on people-first content. Google points site owners to its self-assessment questions. Is the content original and accurate? Is it written with real expertise? Does it truly satisfy the person searching?
What to Avoid While It’s Rolling Out
- Don’t rewrite pages in a panic. If a page drops on day two and you overhaul it on day three, you won’t know if a later recovery came from your changes or from the rollout itself.
- Don’t delete or noindex content because of a short dip. Noindex is a tag that tells Google to leave a page out of search. Removing pages is a big decision. Make it on settled data, not mid-update noise.
- Don’t chase quick fixes. Changing word counts, stuffing keywords or adding links won’t undo a core update effect. These updates judge overall quality and relevance, not checklist items. I’ve never seen a checklist tweak fix a core update drop.
- Don’t run a site migration or redesign now if you can avoid it. Big structural changes mid-rollout make it almost impossible to separate cause from effect later.
What You Can Safely Keep Doing
Business as usual is fine. Keep publishing the content you had planned, keep fixing real technical bugs, and keep improving pages based on what your users need.
The point is not to freeze the site. It’s to avoid quick reactions driven by numbers that are still moving.
How to Monitor the June 2025 Core Update in Search Console
Google Search Console is the most reliable view you have. It shows Google’s own data for clicks, impressions and average position on your site. Third-party rank trackers are useful for context, but they only check a sample of keywords and locations. Search Console is always where I look first.
1. Mark the Key Dates
Write down 30 June 2025 as the start date. When Google announces completion on the dashboard, note that date too. Every comparison you make later depends on these two dates.
If you share reports with a team or clients, add a note in your reporting tools so nobody misreads July’s numbers later.
2. Capture a Clean Baseline Now
In the Performance report (Search results), set a custom date range for the four weeks before 30 June. Export the Queries and Pages tables. This is your baseline, the “before” picture you compare against.
Search Console keeps 16 months of data, so this isn’t urgent. But having the export ready makes the later comparison faster, and you can work with the figures in a spreadsheet. I do this as a habit for every core update.
3. Watch Trends, Not Single Days
During the rollout, check in every few days, not every hour. The Performance report’s 24-hour and 7-day views help you spot sharp shifts. But daily figures are noisy, and weekday-to-weekend swings are normal for most sites.
Look at the shape of the line over a week. A slow slide or climb across several days tells you more than one bad Tuesday.
4. Break It Down by Page and Query
Site-wide totals hide the story. Use the Pages tab to see which URLs are gaining or losing clicks. Use the Queries tab to see which searches are moving.
For example, an online shop might find that category pages are steady while blog guides have lost impressions. That points to a question about the content, not a site-wide problem.
5. Separate Search Types and Countries
Change the “Search type” filter to check Web, Image, Video and News one by one. A drop in image search traffic is a different issue from a drop in web results.
If you serve several markets, filter by country too. Core updates roll out globally, but the effects can show up unevenly.
6. Rule Out Other Causes
Before blaming the update, check for problems you can fix. Look at the Page indexing report for new errors. Check for a spike in server errors or redirects (our guide to HTTP status codes and what they tell Google helps here). And make sure there’s no notice in the Manual actions or Security issues reports.
Also think about the season. Many industries slow down in summer, so compare against the same period last year where you can.
How to Interpret Early Movement
Two days in, here is a sensible way to read what you see.
- Small changes in average position (a page moving a spot or two) are normal in any week, let alone during a core update. Note them and move on.
- Large, sudden drops on important pages are worth writing down now: which URLs, which queries, which dates. You’ll want that record when you look at the final picture.
- Gains are not final either. Don’t celebrate or report wins to your boss or clients until the rollout is done and the data has settled.
- Clicks and impressions can move apart. If impressions rise but clicks don’t, your pages may be showing for more searches in lower positions. Or features on the results page may be taking more attention.
Pair Search Console with your analytics. A GA4 report focused on organic search traffic shows whether changes in Google visibility affect engagement and conversions. That is what your business really cares about.
If the Update Hurts Your Site: The Right Mindset
Whatever happens over the next few weeks, plan your response for after the rollout, not during it.
If you do see a real, lasting drop once things settle, Google’s advice is to judge your content honestly against its self-assessment questions. Do your pages offer original information or analysis? Do they show first-hand expertise? Would a visitor leave satisfied, or need to search again?
It also helps to look at the pages that now rank above yours. Not to copy them, but to understand what searchers might get from them that they don’t get from you. When I review a drop, this is usually the most useful hour I spend.
How Long Recovery Can Take
Google has been clear that improvements don’t guarantee a recovery, and that some changes can take months to show. Its systems need time to see that a site keeps producing helpful content.
Google also runs smaller core updates that it doesn’t announce. These can move a site that has improved without waiting for the next big named update. Still, for many sites, the next announced core update is when a larger change shows up.
Questions Worth Asking Your Team Now
You can use the rollout period well without touching anything live:
- Which pages bring in most of our organic revenue or leads?
- Which of those pages haven’t been reviewed or updated in a long time?
- Do our key pages clearly show who wrote them and why they’re qualified?
- Are there sections of the site built mainly to attract search traffic, not to help our customers?
Answering these now gives you a head start if you need to act later. They’re useful questions even if the update leaves you alone.
What Happens Next
Google will mark the rollout complete on the Search Status Dashboard and add it to its ranking release history. That’s your signal to start your post-update analysis. Wait about a week after completion, then compare against your pre-30 June baseline.
When the time comes, our follow-up guide on how to read your core update results walks through that analysis step by step.
Conclusion
The June 2025 core update is a broad, routine change to Google’s ranking systems. It began on 30 June and may take up to three weeks to roll out. Right now, I think the best move for most sites is to watch, write things down and wait.
Set your dates, save your baseline in Search Console, check for technical issues you can really fix, and don’t rewrite pages based on a few days of data. Once Google confirms the rollout is finished and a week has passed, you can compare clean periods and decide if anything needs to change.
