Core Algorithm

What a core algorithm is

Google's core algorithm is the always-on ranking system that decides, for every query, which pages show up and in what order. It runs constantly in the background; a "core update" is a periodic adjustment to that system — and conflating the two is where most people go wrong.

Get this distinction right and a lot of panic evaporates. The core algorithm is the machine. A core update is Google reaching in and retuning the machine. You don't get "hit by the core algorithm" — it's always running. You get affected by a core update, which is a specific, dated event.

The core system vs a core update

This is the spine of the whole topic, so it's worth nailing down concretely.

A real example

A recipe site holds a stable position 4 for "sourdough starter" for months — that's the core system doing its steady job. Then a core update rolls out over two weeks and the page slides to position 11. Nothing on the page changed. What changed is how the system now weighs the competing pages: maybe it's rewarding first-hand experience and depth more heavily, and three competitors simply demonstrate that better.

The wrong reaction is to gut the page the day rankings wobble mid-rollout. The right one is to wait until Google confirms the update is done, then compare the page honestly against the ones that gained, and close the real gaps.

How to tell a core update from normal noise

1. Confirm an update is actually running. Check Google's Search Status Dashboard and its ranking-updates page. If nothing is announced, your movement is normal query-level fluctuation, not the system being retuned.
2. Look at the shape of the change. A core update moves lots of pages at once over a defined window. A single page dropping while everything else holds is usually a page-specific issue, not a core event.
3. Wait for the rollout to finish. Rankings jump around during a rollout. Judging impact before Google marks it complete gives you a false reading.
4. Segment in Search Console. Compare the two weeks before and after the confirmed dates by query and page. Find which topics and templates lost, not just the sitewide number.
5. Diagnose against winners, not against yesterday. Pull the pages that gained for your lost queries and ask what they demonstrate that yours doesn't — depth, experience, accuracy, trust.

Common mistakes and how to fix them

• Calling every ranking dip "the algorithm." Most day-to-day movement is the core system re-scoring live results, not an update. Fix: only invoke "update" when Google has confirmed one on the dates that match your drop.
• Reacting mid-rollout. You'll chase noise and can't tell what helped. Fix: note the drop, wait for "completed," then act on stable data.
• Hunting for a "penalty" to undo. Core updates aren't penalties and there's no single fix to reverse. Fix: treat a drop as a re-rating of relative quality and improve the content itself.
• Making dozens of changes at once. If everything moves, you learn nothing. Fix: prioritize the pages and topics that actually lost, change deliberately, and measure across the next update.
• Expecting instant recovery. Improvements often aren't fully reflected until a later core update reassesses the site. Fix: set the expectation that recovery is measured in updates, not days.

Frequently asked questions

Is the core algorithm the same thing as a core update?

No, and it's the single most important distinction here. The core algorithm is the permanent, always-running system that ranks results. A core update is an occasional, named change to that system. One is the engine; the other is a tune-up.

Did a core update penalize my site?

Almost certainly not in the penalty sense. Core updates re-evaluate the relative quality of all content; a drop means other pages are now judged more deserving for those queries, not that you broke a rule. Google's own guidance says there's nothing to "fix" — you improve the content.

How often does the core algorithm change?

The system is adjusted constantly in small ways, but broad, announced core updates land a handful of times per year. Between them, thousands of smaller, unannounced tweaks ship continuously.

How long does a core update take to roll out?

Typically one to three weeks. Google announces the start and confirms completion. Rankings are volatile in between, which is exactly why you wait for the end before drawing conclusions.

Can I recover between core updates?

You can and should make improvements immediately, but the full re-rating often waits for the next core update to reassess your site. Steady improvement plus patience is the play.

Where this fits

Once you can tell the system apart from an event, the practical work is monitoring and diagnosis. See how to monitor algorithm updates and the Google algorithm update history every SEO should know for the record of past core updates and how sites reacted. For a concrete recent case, the March 2026 core update breakdown walks through what actually moved.