SEO

Google Core Update

Also called Core algorithm update, broad core update

A broad, announced change to Google's ranking systems that can move a site's visibility without anything on the site changing.

Quick facts: Google Core Update

Category
SEO
Also called
Core algorithm update, broad core update
Level
Intermediate
Affects
Organic visibility, enquiry volume, content priorities
Where to see it
Google Search Console (Performance report), Google Search Status Dashboard, Google Analytics 4
In this article4
  1. How a Google core update works
  2. Why core updates matter
  3. Where core updates go wrong
  4. What to do about it

How a Google core update works

Google adjusts its ranking systems constantly, but several times a year it announces a broad core update: a re-weighting of how relevance, usefulness and trust are judged across every language, country and industry at once. These updates do not target individual sites and they are not punishments. The systems that decide which page best answers a query simply start valuing slightly different things, and every page on the web is re-assessed against the new weighting. That is why a site can lose or gain visibility in a fortnight while not one word on it has changed.

Rollouts run over days or weeks rather than hours, and positions often move in both directions before they settle. Google publishes the start and the finish of each one, which is the only dependable way to tell whether a movement lines up with an update or with something you did to the site yourself.

Why core updates matter

A core update resets the competitive picture rather than grading your site in isolation. A page can fall because a competitor’s page is now judged to answer the query more completely, not because yours got worse. For a business the effect usually shows up in enquiries before it shows up in a traffic chart, because commercial pages and informational pages rarely move together.

Exposure is not even across sectors. Topics that touch someone’s health, money, safety or legal position — what Google groups under Your Money or Your Life subject matter — are held to a stricter standard of demonstrated expertise, so clinics, consultancies, remittance services and finance sites tend to feel core updates more sharply than a hobby blog does.

Where core updates go wrong

The most expensive mistake is acting during the rollout. Rankings are unstable while an update is still deploying, so changes made in week one cannot be attributed to anything, and a site that was going to recover on its own gets rewritten for no reason. Wait for the confirmed completion before you draw a conclusion.

The second is diagnosing a drop as a technical fault. Core updates are content and quality judgements; the tags, speed scores and sitemaps that people rush to check are almost never the cause. And a drop after an update is not a manual action, which is a separate, human-issued penalty that appears as a notice in Search Console.

What to do about it

Start with evidence rather than instinct. In Search Console, compare the weeks before and after the rollout query by query and page by page, and separate pages that lost impressions from pages that kept impressions but lost position. A site-wide fall and a fall confined to one section point to very different problems.

Then work on the pages that lost, honestly. Ask whether each one actually answers the search it targets better than the pages now above it, whether it shows real first-hand experience, and whether it is one strong page or three overlapping thin ones. Recovery from a core update comes from making the content genuinely better, and it usually lands at the next update rather than the next week. If the drop is broad and you cannot see the pattern yourself, an outside read through SEO consulting is cheaper than a year of guessing.

Do and do not

Do

  • Wait for the confirmed rollout end before judging anything
  • Compare before and after query by query in Search Console
  • Improve the losing pages rather than the whole site

Do not

  • Rewrite pages while the update is still rolling out
  • Treat a core update drop as a manual penalty
  • Chase technical fixes for what is a content problem

Questions people ask about this

How do I know whether a core update caused my traffic drop?

Match the dates. Google announces when each core update starts and finishes, so compare your Search Console performance to that window. If the fall begins on the announced start date and affects many pages at once, an update is the likely cause. If it begins on a day you changed the site, migrated hosting or edited templates, look there first.

Can I recover from a core update?

Yes, but not by tweaking. Google's own guidance is that there is nothing to fix in a technical sense; the systems have simply changed what they reward. Recovery comes from improving the content itself so it answers the search more completely and shows genuine experience. Improvements are usually reflected at a later update rather than immediately.

Should I stop publishing while an update is rolling out?

No. Keep publishing on your normal schedule, because pausing removes the freshest signal you have and teaches you nothing. What you should pause is large, reactive rewrites of existing pages. Let the rollout complete, read the data, then decide which pages genuinely need work rather than rewriting the site on a hunch.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.