What is a Google core update?

Core update, explained

Google's documentation describes core updates plainly: several times a year, it makes significant, broad changes to its search algorithms and systems, and it gives notice on its list of ranking updates. Most sites don't need to worry about them and may not notice one happened. Rankings can move around while one rolls out.

A drop after a core update isn't a penalty. There's no manual action, nothing to fix technically, and often nothing "wrong" with the pages that fell. Google reassessed how helpful and relevant pages are compared with others, and some sites moved up while others moved down.

Google's advice is to assess before reacting. It recommends waiting at least a full week after a core update completes, then comparing that week in Search Console with a week before the rollout started. Look at which pages and queries dropped, and by how much; small moves in position are normal. Then ask Google's helpful content questions honestly of the pages that fell, and compare them with what now ranks above them.

Recovery takes time. Google says some improvements can take effect in days, but it can take several months for its systems to confirm a site as a whole is producing helpful content, and that sometimes means waiting for the next core update. It also runs smaller, unannounced core updates, which can reflect improvements in between.

What not to do: delete large sections in a panic, rewrite everything at once, or buy links to make up the difference. Improve the pages that deserve it, remove or noindex the ones that don't, and keep publishing work you'd be proud to show a reader.

Why it matters for founders

A core update can move a small site's traffic sharply in either direction. Knowing it isn't a penalty keeps you from making panicked changes that do more harm than the update did.

Example

A startup's blog loses a third of its clicks after a core update. The founder finds most losses on thin listicles, merges them into three strong guides, and sees recovery by the following update.

Common mistakes

• Treating a core update drop as a technical penalty to debug.
• Making sweeping changes before the rollout has finished.
• Expecting recovery within days of improving content.