What is an algorithm update?

In Google Search, an algorithm update changes one or more ranking systems that help select and order results. Google says it regularly improves these systems through testing and evaluation and announces changes when that notice is useful to creators and others.

A system is the mechanism; an update is a change to it. Google’s 2022 explanation of ranking-system terminology makes that distinction because older names sometimes used “update” for the system itself.

Avoid treating the phrase as a single, visible switch that explains every movement in search. Google’s ranking-systems guide describes page-level evaluation alongside site-wide signals; good or poor site-wide signals do not mean every page must rank the same way.

An announcement gives context, not a site diagnosis

A public announcement gives the investigation a named event and source to record. That helps keep Google’s stated change separate from your own changes, the performance observation and any proposed explanation.

Google’s traffic-drop troubleshooting guide also discusses technical issues, security issues, spam violations, seasonality and changing demand.

What does an algorithm update record tell you?

Use the public record to establish what was announced, then read its scope and rollout status before comparing performance. Keep a record of when you checked it and any completion date available. Add the source URL, exact label and any limits Google states for affected features or markets.

For suspected core-update effects, Google directs readers to the Search Status Dashboard’s ranking history to check completion and note start and end dates.

Log the announcement URL and label, its stated scope, the rollout dates or ongoing status, the performance measure you are comparing and any site changes in the same interval. Preserve the source’s wording when scope or completion is uncertain.

Core changes, spam changes and ordinary improvements

Google’s core-update guidance describes broad changes that do not target specific sites or individual pages. Its spam-update guidance describes notable improvements to automated spam detection that is already operating.

Different changes require different questions
ChangeDocumented scopeWhat the label does not establish
Core updateBroad changes to present helpful, reliable results; no targeting of a particular site or pageA diagnosis of a specific website
Spam updateNotable improvements to continuously operating spam-detection systemsThat every coincident traffic loss is a spam violation
Smaller core improvementsGoogle says it also makes smaller, unannounced core updatesA fixed date when an individual page will improve

Use the actual announcement rather than imposing a permanent annual count or rollout length. Historical names can describe systems that have since changed; an old update name is not a current operating schedule.

Reading an official record alongside a fictional incident

The dashboard’s historical March 2024 core-update entry lists a date of 5 March 2024 and a duration of 45 days. That is a specific published entry, not a template for how long every core update lasts.

Now imagine a fictional gardening publisher moving a guide to a new URL during an announced rollout. Its later comparison shows fewer clicks for that guide. The log contains two events: a Google update and a local URL change. The timing alone does not tell the publisher which explains the observation.

For this hypothetical investigation, first check the guide’s old and new URLs, redirects and indexing evidence. Record those findings alongside the performance comparison. If another page rose during the rollout, that still would not prove its format is the exact fix for the affected guide.

Google’s traffic-drop guidance distinguishes automated detection of spam practices from human review that can result in a manual action, and recommends checking the Manual Actions report when a spam violation is suspected.

A missing notice should not be used as proof that a loss was caused by an algorithm update. The broader term covers ranking-system changes; the informal phrase algorithmic penalty raises a narrower diagnosis question. Keep the evidence for each explanation separate.

A core update is one kind of broad ranking change. Its specific content-assessment workflow belongs in that narrower guide rather than being applied automatically to every update or technical failure.

Compare the right evidence

For core-update analysis, Google recommends waiting at least a full week after completion before comparing Search Console performance with a week before the rollout began. That is specific guidance for that analysis, not a reason to leave a confirmed broken page or site outage unresolved.

Keep clicks, impressions and position distinct in the log. Identify the pages, queries and search type involved, and record the comparison periods and filters. If account data is unavailable, leave the site-impact result unknown rather than filling in an estimated loss.

For a traffic change that coincides with an update, test alternative explanations and record actual findings. Keep investigation and intervention separate: a confirmed redirect defect calls for a different response from an untested hypothesis about content quality.

Avoid fixed recovery clocks and pruning quotas

Google says improvements do not necessarily have to wait for a major core update: smaller updates can also reflect them. It also says website changes are not guaranteed to produce a noticeable effect. A next-update-only recovery rule is therefore too categorical.

Google describes deleting content as a last resort when it cannot be salvaged. Its core-update guidance does not supply a universal percentage of pages to remove. Do not turn a traffic ranking of pages into an automatic deletion or noindex quota.

For link-spam updates, Google warns that removing the effects of spammy links can remove their previous ranking benefit, and that benefit cannot be regained. Do not present one generic recovery promise for all update types.

Use manual action for the distinct human-review enforcement concept, and SERP for the results page where positions are observed. Neither a ranking movement nor a tool’s volatility label is, on its own, a finding about your site’s cause.

Sources and scope

The definitions and update-specific statements above use Google’s ranking-systems, core-update, spam-update and traffic-drop documentation. The historical example is a single dashboard entry.