Google June 2021 Core Update (2 June 2021): What Changed and How to Recover

The Google June 2021 Core Update started on 2 June 2021 and finished on 12 June 2021, a rollout of about 10 days. It was unusual because it was only the first half of a two-part core release: Google shipped the improvements that were ready and held the rest back for July. The key takeaway is to judge any June 2021 movement together with July, because some June changes reversed a month later.

This article is part of my full list of Google algorithm updates.

Detail	Information
Update name	Google June 2021 Core Update
Type	Broad core update (part one of two)
Rollout started	2 June 2021
Rollout finished	12 June 2021
Rollout length	About 10 days
Confirmed by Google	Yes, announced by Danny Sullivan (Google Search Liaison)
Official source	Google Search Central: core updates documentation

What the June 2021 Core Update changed

Google announced it in the usual way. Danny Sullivan wrote: “Later today, we are releasing a broad core update, as we do several times per year. It is called the June 2021 Core Update.”

What made it different was the admission that came with it. Google said “some of our planned improvements for the June 2021 update aren’t quite ready, so we’re moving ahead with the parts that are”. The rest would follow in July 2021. Google also warned that “a very small slice of content” might see changes in June that would reverse in July.

That matters for how you read your data. With a normal core update, the period after completion is a reasonably stable new baseline. With June 2021, the baseline was explicitly temporary. A site that lost visibility on 5 June might have been one of the cases that bounced back in July, and a site that gained might have handed some of it back.

As with every core update, Google did not name specific targets. Core updates are broad changes to how Google assesses content overall, not penalties for particular tactics.

Timeline

June 2021 was one of the busiest months in Google’s update history, which is the single biggest complication when diagnosing it.

Date	Event
2 June 2021	June 2021 Core Update begins. Google says part of the planned changes will follow in July.
12 June 2021	June 2021 Core Update completes.
15 June 2021	Page Experience update (mobile) begins its gradual rollout.
23 June 2021	June 2021 spam update, part one, released and concluded.
28 June 2021	June 2021 spam update, part two, released and concluded.
1 July 2021	July 2021 Core Update begins, completing the two-part release.

Who was affected

Google named no specific site types. As reported by data providers, it was one of the bigger core updates of that period, and RankRanger later ranked it as its largest measured update. Treat those as tool-based observations: trackers measure ranking volatility across a sample of keywords, not your traffic.

Because the update was large and broad, effects showed up across many niches. In my experience with core updates generally, the sites that feel it most are those where a large share of traffic sits on pages that do not fully satisfy the query, or where the site lacks clear signs of who is behind the content in topics where trust matters.

How to tell if the June 2021 Core Update hit your site

The clean window for this update is short. You have 2 to 12 June before the page experience rollout and two spam updates muddy the picture. Use that to your advantage.

1. Use a tight comparison. In the Search Console Performance report, compare 19 May to 1 June 2021 against 3 to 14 June 2021. Avoid stretching the “after” period past mid-June or you will be measuring several updates at once.
2. Look at daily clicks. A core update effect usually shows as a step change during the rollout window, not a gradual slide over months.
3. Break it down by page group. Tag URLs by template (blog posts, service pages, category pages, product pages) and compare. Core update losses often cluster on one type of content.
4. Check average position, not just clicks. If position held but clicks fell, look at SERP feature changes or seasonality instead.
5. Then extend to July. Compare the same groups across 13 to 30 June and after 12 July. If losses in June reversed in July, you were likely in the “small slice” Google mentioned, and there may be nothing to fix.
6. Rule out non-Google causes. Site migrations, tracking changes, robots.txt or noindex mistakes and server problems around those dates are easy to confuse with an update. A technical SEO check rules these out first.

How to recover from the June 2021 Core Update

Google’s position is that there is no specific fix for a core update, and a drop does not necessarily mean a page has a problem. Other pages may simply have become more relevant. That said, a drop is a good prompt to review quality honestly. For June 2021, I would add one step at the start that does not apply to most core updates.

1. Wait for July before acting. Because Google said some June changes would reverse, anyone diagnosing this today should look at where they stood after 12 July 2021, not after 12 June. Do not rebuild pages based on a change that undid itself.
2. List the pages and queries that lost. Work from data, not instinct. Focus on pages that lost meaningful clicks, not every small wobble.
3. Check intent match. Search the main query and look at what now ranks. If the top results are practical guides and you have a sales page, or vice versa, intent is the gap.
4. Review against Google’s self-assessment questions. Does the page give original information or analysis? Is it written by someone with real knowledge of the topic? Would a reader leave satisfied, or need to search again?
5. Strengthen trust signals. Clear authorship, an about page that explains who you are, accurate contact details, and sources for factual claims, especially on health, finance or legal topics.
6. Consolidate overlapping pages. Several thin pages chasing the same query can be merged into one stronger page with redirects.
7. Improve or remove weak content. Pages that add nothing can drag on how a site is perceived. Improve what is worth keeping; remove or noindex what is not.
8. Be patient. Recovery most often shows at a later core update, though some movement between updates is possible.

Is it still relevant today?

Directly, no: later core updates have since replaced its effects many times over. Its lasting relevance is twofold. First, if you are auditing a long traffic history, June 2021 is a period where four separate Google changes overlap, so it is easy to blame the wrong one. Second, it showed that Google can split a core update in two and that early movement is not always final. When a core update is running, I still advise clients not to make big changes until it has finished and settled.

Frequently asked questions

When did the June 2021 core update start and finish?

It started on 2 June 2021 and finished on 12 June 2021, about 10 days.

Why was the June 2021 core update split into two parts?

Google said some of its planned improvements were not ready, so it released the parts that were in June and the rest in the July 2021 Core Update.

Did the July 2021 core update reverse June changes?

Google warned that a very small slice of content might see June changes reverse in July, and some sites did report that. It was not a general reversal.

Was the June 2021 core update a penalty?

No. Core updates are broad changes to ranking systems. There is no manual action involved and nothing to submit to Google.

How long does recovery from a core update take?

Usually until a later core update, after sustained quality improvements. Some movement between core updates is possible, but there is no fixed timeline.

Sources

• Google Search Central: core updates documentation
• Search Engine Land: June 2021 core update rolling out
• Search Engine Land: June 2021 core update finished rolling out
• Keywords Everywhere: June 2021 core update

If your traffic changed in June 2021 and you cannot tell which update caused it, request a free audit. My SEO audit service separates overlapping updates by page type and date, so you fix the real problem.