What Are Google Core Updates?

Several times a year, Google makes broad changes to its ranking systems that can shift rankings significantly across many sites and query types. Google calls these core updates. They are not penalties, and they do not target individual pages or specific violations. A drop following a core update means competing pages now look more helpful, relevant, or trustworthy. It does not mean your site broke a rule.¹

How do core updates differ from other Google updates?

Google runs three types of updates, and confusing them leads to the wrong response.

Core updates are broad recalibrations of how Google’s systems assess content quality across all sites and query types simultaneously. A core update does not mean anything on your site is wrong. It means Google’s evaluation of what constitutes quality has shifted, and some sites have risen or fallen relative to each other as a result.

Spam updates target sites using specific tactics that violate Google’s policies: manipulative link schemes, cloaking, scaled auto-generated content, expired domain abuse. AI content risks, including thin AI-generated pages with absent authorship and factual errors, increasingly fall under this category. International SEO mistakes, such as machine-translated pages with no local editorial review, create similar quality signals. A spam update is closer to an enforcement action. If a spam update affects your site, there is a specific violation to find and fix.

Unannounced minor updates happen continuously. Google adjusts its systems thousands of times per year, most invisibly. Position movements that do not coincide with a confirmed core update may still reflect these smaller changes.

The practical difference: a core update drop calls for content quality improvements. A spam update drop calls for policy compliance. Disavowing links or fixing technical issues in response to a core update addresses the wrong problem.

How often does Google release core updates?

Google releases core updates roughly three to four times per year. Every core update is announced via the Google Search Status Dashboard and typically confirmed on Google’s official channels.

Recent core updates:

Update	Dates
May 2026	21 May 2026 (rolling out)
March 2026	27 March to 8 April 2026
December 2025	11 to 29 December 2025
June 2025	30 June to 17 July 2025
March 2025	13 to 27 March 2025

Rollouts typically take one to two weeks. Rankings continue to settle throughout the rollout period, so data pulled mid-rollout will not reflect the final state.

For a full history of named updates since 2011, see the Google algorithm updates timeline.

How do I know if a core update affected my site?

Start with the Search Status Dashboard to confirm the update has finished and note its start and end dates. Wait at least one full week after completion before analysing data, to avoid drawing conclusions from a still-settling index.

Then in Google Search Console:

1. Open the Performance report and switch to Compare mode
2. Set the comparison to the week before the update started against the week after it completed
3. Look at total clicks and impressions across the site. A site-wide drop confirms impact; a stable overall trend with some pages shifting suggests normal volatility
4. Switch to the Pages view, sort by average position change, and export the pages with the largest position declines
5. Look for a common thread in the worst-affected pages: same content type, same topic cluster, no named author, thin depth, no original data or first-hand experience

That pattern is the diagnosis. The fix follows from it.

A useful secondary check: compare your visibility against competitor sites in the same category. If peers held position or gained while you dropped, the issue is specific to your site. If the whole category shifted, a query-level recalibration may be involved.

What should I do after a core update?

Wait for the rollout to finish before acting. Rankings are still in flux during rollout, and changes made on the basis of incomplete data may not reflect the actual outcome.

Once the rollout is complete and you have identified the pattern in affected pages:

Focus on content quality. The most consistent factor in core update drops is content that lacks depth, originality, or clear expertise. Generic summaries, content without first-hand experience, and pages without a named author fare consistently worse. Improving these dimensions is the most effective response.

Strengthen authorship and trust signals. Add or improve author bios with verifiable credentials. Cite sources for factual claims. Make the publisher and author clearly identifiable. These are signals that Google’s quality systems actively assess.

Do not delete pages as a first response. Google’s own guidance states that deletion is a last resort. A page that underperforms can often be improved; removing it may also remove any authority it has accumulated.

Do not make structural or technical changes when content is the issue. Updating title tags, restructuring URLs, or improving Core Web Vitals does not address the quality signals that core updates recalibrate. Technical improvements are worth making on their merits, but they will not recover a core update drop.

For guidance on assessing content quality systematically, see SEO auditing and E-E-A-T.

How long does recovery take?

Google is explicit on this point: some changes may take effect within days, but full recovery often takes months.¹ In practice, meaningful recovery typically aligns with the next core update cycle, three to four months later.

This is counterintuitive but reflects how the system works. Google must recrawl improved content, reassess it against current quality signals, and then factor that reassessment into the next broad recalibration. Content improvements made between core updates are not wasted: they position a site for recovery when the next update runs. But the improvement itself is not sufficient to trigger immediate recovery.

A site that dropped in one core update and improved its content before the next update is in the best position for recovery. A site that waits to see whether rankings recover before making changes is extending the timeline unnecessarily.

Footnotes

1. Google Search’s core updates — Google Search Central ↩ ↩²