Core Update
A significant, broad change Google makes to its ranking systems several times a year. Not a penalty and not aimed at specific sites; Google gives a calm procedure for checking a traffic drop.
Reviewed by Alexander Yarovenko · Updated: 2026-10-08
A core update is one of the significant, broad changes Google makes to its search algorithms and systems several times a year. Google announces them on its list of Search ranking updates. They are designed so that results overall stay helpful and reliable, and they do not target specific sites or pages. Google says most sites do not need to worry about a core update and may not even notice one.
What it is and where the boundary lies
A core update is a broad reassessment, not a penalty. Google’s own analogy is a list of your twenty favourite restaurants written in 2019: new places have opened, some you now rate higher, and the ones that move down are not necessarily bad, there are just others that make the list. A page that loses position after a core update has not necessarily done anything wrong; other pages may now serve the searcher better. Smaller core updates also happen continuously and are not announced, because they are not widely noticeable.
How it differs from similar terms
| Term | What it is | Relation to a core update |
|---|---|---|
| Core update | a broad, announced change to ranking systems | the subject here |
| Manual action | a human decision about a policy violation, shown in Search Console | a different thing; a core update is not a manual action |
| Google algorithm | the systems that rank results | a core update changes them broadly |
| SERP volatility | how much results move | often rises around an update, but moves for many reasons |
| Content decay | a page’s clicks falling over time | a slow decline, unlike a drop tied to an update date |
Why it matters
Because a traffic drop that coincides with a core update invites bad decisions: panic edits, deleted pages, a hunt for a “penalty”. Google’s page exists to give a calmer procedure and a fair warning: avoid quick fixes, deleting content is a last resort, and there is no guarantee that changes you make will have a noticeable effect.
What to do when traffic moves
- Confirm the update has finished. Check the Google Search Status Dashboard and note the start and end dates.
- Wait a full week after it ends. Google recommends waiting at least a week after completion before analysing in Search Console.
- Compare equal windows. Compare that week with the week before the update began rolling out.
- Review top pages and queries. A small change in position, for example from 2 to 4, needs no drastic action; Google recommends not changing content that already performs well. A large one, for example from 4 to 29, needs a deeper look.
- Split by search type. Analyse Web, Images, Video and News separately to see where the drop happened.
- For a sustained large drop, assess the whole site. Use the helpful-content questions, and consider asking people unaffiliated with the site to do it too.
Practical example
| Page | Position before | Position after | Reading |
|---|---|---|---|
| /guide/audit-checklist | 2 | 4 | small drop; leave it, do not rewrite a page that performs well |
| /blog/seo-trends | 4 | 29 | large drop; assess the page and the site against the helpful-content questions |
The figures follow Google’s own examples of a small and a large drop.
Common mistakes
- Analysing before the update finishes: Google says to confirm it has completed and to wait a week.
- Making quick-fix changes: Google warns against removing elements just because you heard they are bad for SEO.
- Deleting content in a panic: Google calls deletion a last resort, for content that cannot be salvaged.
- Treating a drop as a penalty: core updates are broad and do not target specific sites.
- Expecting a fast recovery: some changes take effect in days, but it could take several months, possibly until the next core update.
How to validate the result
After improvements, compare equal periods in Search Console for the affected pages and queries, with the same filters and search type. Allow months, not days, as Google states, and remember that there is no guarantee of a noticeable impact. Track whether visitors on those pages now find what they came for in your own analytics.
More questions
How many core updates are there per year?
Google says several times a year, and announces them on its list of ranking updates. It does not give a fixed number.
Is a core update a penalty?
No. Google describes core updates as broad changes that do not target specific sites or pages; pages that move down are not necessarily bad.
Do I need to wait for the next update to recover?
Not necessarily. Google says improvements can show up between announced updates, but it could take several months, and nothing is guaranteed.
Next practical step
If your traffic changed around an update, write down its start and end dates from the dashboard, wait a week and compare the two weeks in Search Console. Then decide with the helpful-content questions, not on instinct. See also the content decay playbook.
Related concepts
- Google algorithm — the ranking systems.
- Helpful content — what the self-assessment asks about.
- E-E-A-T — signals of trustworthy content.
- SERP volatility — how much results move.
- Penalty recovery — manual actions, a different case.