Google updates how it ranks and selects content throughout the year. A traffic change needs investigation; it does not automatically mean your website has been penalised.
Know the update type
- Core update: Broad changes to how Google evaluates and ranks content.
- Spam update: Changes to systems that detect content or practices that break Google’s spam policies.
- Discover update: Changes to the Discover recommendation feed, which is separate from ordinary web search results.
Recent confirmed updates
Latest announced update in each category, checked 14 October 2026. All three rollouts below are complete. Dates follow Google’s US/Pacific dashboard.
| Update | Rollout dates |
|---|---|
| September 2026 spam update | 24 September–8 October 2026 |
| May 2026 core update | 21 May–2 June 2026 |
| February 2026 Discover update | 5–27 February 2026 |
February’s Discover rollout initially targeted English-language users in the US.
What to do after an update
- Confirm the rollout. Use Google’s Search Status Dashboard to check the dates and completion status.
- Compare the right data. For a core update, wait at least one full week after it ends. In Search Console, compare the week after completion with the week before the rollout began.
- Find the affected pages. Check queries, traffic changes and relevant technical or content issues. Review spam policies after a spam update.
- Make focused improvements. Improve weak pages and fix verified problems. Avoid changing everything because a chart moved.
An audit score does not guarantee ranking recovery. Keep a record of changes and measure actual search performance.
Need help understanding a traffic drop? Discuss an SEO review.
Build an evidence record before changing pages
When traffic changes around an announced update, begin with the data question. Which search type changed, which pages were affected and which reporting period is relevant? Note the official rollout dates and any known website edits, changed URLs or tracking interruptions. An update appearing on the calendar is a reason to investigate, not proof that it caused every movement in your charts. Keep observations separate from explanations that still need evidence. This makes it easier to choose a focused review instead of rewriting the whole website in response to one dashboard total.
Google recommends waiting at least a full week after a core update has completed before comparing the relevant Search Console periods. Record the dates used so another reviewer can repeat the comparison. Review important pages and queries rather than relying only on a site-wide average. Search types should be considered separately because a change in ordinary Web Search is different from a movement in Discover or image search. The historical update table above records the latest category announcements checked on its stated date; use Google’s dashboard again when investigating a later change.
Look for a pattern across the affected pages
For example, suppose visits to several old buying guides fall while the main service pages remain stable. Start by identifying the guides and the questions they were intended to answer. Review their current information, sources, comparisons and internal links. Check whether a recent URL change or an unintended access problem affects the same pages. This is an illustrative investigation, not a diagnosis of your site. The observed pattern should lead to checks that can distinguish possible causes, rather than an assumption that every lower ranking means a manual penalty or that one technical setting will reverse the change.
Compare an affected page with its actual visitor need. Does it explain the topic clearly, support factual claims and provide information a reader can use to make a decision? Are historical report dates and current facts distinguished? Product or service details may need an owner-approved update when the offer changes. A relevant competitor can help reveal unanswered questions, but copying its wording or adding generic paragraphs does not provide your own evidence. Record specific gaps and the information needed to address them. A meaningful improvement should have a purpose beyond increasing the length of the page.
Make focused changes and review them consistently
Prioritise confirmed faults and useful content improvements. A broken enquiry route can be repaired and checked directly. An outdated product comparison needs verified current information before it is revised. A poorly explained service needs accurate scope and responsibilities from the business. Keep a baseline for each selected URL, identify what was changed and state how it was reviewed. If the issue depends on hosting or an external resource, document that dependency. Avoid removing working page features or deleting whole sections simply because an unverified recommendation labels them as bad for SEO.
Use the same relevant data sources and comparable periods in the follow-up. Note any additional changes that affect the interpretation, including a different crawl scope or a changed reporting setup. Search movement can take time, and improved website content does not establish a guaranteed recovery date. Keep the work record, technical observations and business results in separate parts of the report. If the available evidence cannot identify the cause of a change, say so and define the next investigation. This gives the website owner a useful decision process while leaving uncertain explanations visible.
Sources
Sources checked 14 October 2026.