Latest SEO updates: where to read them first and what to do in the week after

Check three sources, in this order. The Google Search Status Dashboard lists confirmed ranking, indexing and serving updates with start and end dates, and it is the only place that tells you whether a change is still rolling out. The Google Search Central blog publishes the announcement and the guidance that comes with each one. The ranking updates history page on Google Search Central lists every confirmed update going back years, which is what you compare your own traffic dates against. Everything else, including the ranking volatility trackers and the industry news sites, is commentary on those three. Read the source first, then the commentary, because the commentary is usually written within hours and the rollout usually takes weeks.

Then do the diagnosis before the fixing. Most of the work people do in the week after an update is aimed at the wrong page, because they never checked which pages and which queries actually moved.

The sources, and what each one is good for

Source	What it tells you	How to use it
Google Search Status Dashboard	Confirmed ranking, indexing, serving and crawling incidents, with start and finish dates	First stop when traffic moves. Check whether a rollout was open on your dates
Google Search Central blog	The announcement, the reasoning, and the guidance that accompanies it	Read the actual wording. The guidance is usually more specific than the coverage of it
Google ranking updates history page	The dated list of all confirmed updates	Overlay these dates on your own analytics and Search Console charts
Google Search Central documentation	The current rules: spam policies, structured data support, crawling guidance	When an update references a policy, read the policy, not the summary
Search Console announcements and emails	Changes to reports, and manual actions against your own site	Keep the notification email address current and monitored
Volatility trackers and industry press	Early signal that something unconfirmed is happening	Useful as a weather report. Confirm against the dashboard before acting

The kinds of update, because they are not interchangeable

• Core updates. Broad changes to how ranking systems assess content overall, run a few times a year and taking one to several weeks to complete. They are not penalties, and the guidance attached to them is consistently about the quality and usefulness of content rather than a technical fix.
• Spam updates. Improvements to the systems that detect behaviour the spam policies name. If one of these moved you down, read the spam policies and find which one applies.
• Policy changes. New or clarified rules, which the ranking systems then enforce. The three named in recent years are worth knowing by name: scaled content abuse, site reputation abuse, and expired domain abuse.
• Feature and serving changes. Changes to what the results page looks like rather than to ranking: AI Overviews appearing on more queries, rich result types gaining or losing support, local and shopping modules changing shape. These move clicks without moving positions, which is why position reports alone miss them.
• Infrastructure changes. Crawling, indexing and rendering. These show up in the Pages and Crawl Stats reports in Search Console before they show up in traffic.

The direction of travel, which matters more than any single release

Three themes have run through the confirmed updates of the last few years and they tell you where to put effort.

• Separate quality systems have been folded into core ranking. The helpful content system stopped being a standalone update and became part of the core systems. The practical effect is that site wide quality is assessed continuously rather than in occasional sweeps.
• Spam policy has become specific and named. Publishing large volumes of low value pages, renting out a section of a trusted domain to a third party for ranking purposes, and buying expired domains for their history are now each described explicitly in the policies.
• The results page gives more answers directly. AI Overviews and other answer features now sit above the links on a large share of informational queries, so impressions can rise while clicks fall, and that pattern is a serving change rather than a ranking loss.

How to tell whether an update actually hit you

1. Fix the dates first. Note the rollout start and end from the dashboard. Compare the twenty eight days before the start with the twenty eight days after the end, never the week either side of the announcement.
2. Work in Search Console, not analytics. Clicks, impressions and average position by query and by page, with the comparison feature.
3. Split by page type. Export and group your URLs by section: blog, product, category, location. A real update almost always hits one type far harder than the others, and that grouping is the single most useful step in the whole diagnosis.
4. Separate the three causes of a click drop. Lost positions, lost impressions, or the same positions with a lower click through rate. The third usually means the results page changed around you.
5. Check for seasonality and self inflicted causes. A migration, a redesign, a robots file edit, an expired certificate or a plugin update in the same fortnight is a far more common cause than the algorithm.
6. Write down the finding in one sentence before you make a change. If you cannot, you are not ready to make the change.

What to do in the four weeks after a core update

• Wait for the rollout to finish. Positions move in both directions during one, and acting on day three means acting on a number that is still in motion.
• Audit the pages that lost, against the questions Google publishes. Is this page clearly the work of someone with first hand experience of the subject, does it answer the query completely, would a reader trust it, is it the original rather than a rewrite of page one.
• Deal with thin and duplicate pages honestly. Consolidate, improve, or remove. Site wide quality is assessed site wide, so a large archive of pages nobody reads affects the pages people do read.
• Improve the best losers first. A page that used to earn real traffic and has a genuine subject is a faster win than a page that never worked.
• Keep a dated change log. One line per change with the date. Without it the next update is undiagnosable.
• Reassess after the next core update, not before. Recovery from a core update is read at the next one, so give the work a full cycle to be scored.

What to leave alone

Do not buy links in a hurry, do not rewrite the whole site in a weekend, do not add schema to pages that are not eligible for it, and treat any service that offers an immediate recovery for a fee the way you would treat a ranking guarantee. Also skip the technical micro optimisations: changing title tags across a thousand pages during a rollout removes your ability to attribute anything afterwards.

This page covers how to follow confirmed updates and respond to them. For a drop that has no update behind it, the traffic drop diagnosis covers that ground, and penalty recovery deals with manual actions specifically.

What people ask about Latest SEO updates

What is the latest SEO update?

Open the Google Search Status Dashboard and the ranking updates history page on Google Search Central. Between them they show what is live, what finished and when, which is the current answer on any given day.

How often does Google update its algorithm?

Continuously, with a small number of broad core updates announced each year plus spam and feature updates in between. Only the announced ones are dated, which is why the dated list is the right reference point for diagnosis.

How long does a core update take to roll out?

Typically one to several weeks, and the dashboard publishes the start and the completion. Read your numbers after the completion date.

Is a core update a penalty?

No. A penalty is a manual action, and it appears in the Manual Actions report in Search Console with a reason. A core update is a reassessment of relative quality across the whole index.

How do I recover from an update?

Find the page type that lost, improve those pages against the published quality questions, consolidate what is thin, and keep a dated log. Then read the result at the next core update rather than the next week.

Should I follow the volatility trackers?

They are a useful early signal that something is moving across the index. Confirm against the dashboard before you change anything, and never attribute your own numbers to an unconfirmed event.

The update nobody puts on a dashboard

While the ranking systems change, the place the question is asked has been changing too. A growing share of buyers now put the research question to ChatGPT, Gemini, Perplexity or Claude, or read Google's AI Overview and stop there. Each of those answers names a few companies, each names a different few, and each cites different pages. There is no position number in any of them and no report in Search Console that covers them.

So add one check to your monthly routine next to the dashboard. Ask the question a customer would ask, keep your own name out of the prompt so the answer comes back clean, and record who is named and which pages are quoted. Run it monthly and you are working from current data. AI Knows Us measures those answers across the main assistants.