ZINC / Demand

Google Core Update Review: Find What Changed

October 6, 2026 / / Demand

Illustrated search update review with unnumbered comparison trends and page review sheets.
TL;DR

Wait for a confirmed rollout to finish before making the recommended post-update comparison. Segment affected pages and queries, inspect competing explanations and record evidence. Use the review to choose a justified action, not to assign blame to an algorithm by default.

A traffic drop is an observation, not a diagnosis.

Use this routine to decide which pages need investigation after a confirmed core update. Keep it beside the SEO framework and your ongoing SEO work.

Step 1: Confirm the update and comparison dates

Check the Google Search Status Dashboard for the actual rollout status. Do not date an update from a social post.

Google's core update guidance recommends waiting at least a full week after completion before reviewing Search Console. Compare that week with a week before rollout began. Record both ranges.

Step 2: Hold the reporting view steady

In the Search Console Performance report, use the same search type, country and device filters for both periods.

Start with commercially important pages. Keep branded and non-branded queries separate where useful. Export the observations so the next review can reproduce the comparison.

Step 3: Separate the symptoms

Use the same query-and-page pair when comparing position. An aggregate average can move because the mix of queries changed.

Observation Next check
Impressions fell; position stayed similar Demand, seasonality and query mix
Position fell for the same queries Search results, intent and page usefulness
Search clicks held; Analytics visits fell Tracking, consent and reporting definitions
A page disappeared from results Indexing, canonical and response checks

These are investigation routes, not automatic explanations.

Step 4: Rule out a release problem

Review deployments, redirects, robots directives and recent content edits. Inspect an affected URL before changing its copy.

If several pages broke after the same release, record that connection as a hypothesis. Confirm the technical defect before attributing the change to Google's update.

Illustrated Search Console page review with private figures omitted.
Compare the same page and reporting view before choosing a repair.

Step 5: Choose one useful page action

Compare the page with the question its visitors need answered. Improve missing facts, weak explanations or a broken journey. Avoid rewriting every heading simply because a chart moved.

Use this record:

  • Page and query group
  • Observed change and comparison dates
  • Evidence checked; remaining uncertainty
  • One proposed action, owner and review date

Step 6: Review the result without changing the baseline

Save the original comparison and the release date. Recheck the same page group after the change has had time to be processed.

Keep fixes, observed outcomes and assumptions in separate columns. A clear record makes the next decision easier; a hurried rewrite only creates another variable.

Work a completed-rollout comparison

Google records the May 2026 core update as ending on 2 June. An illustrative review on 10 June could compare 13–19 May with 3–9 June: two complete Wednesday-to-Tuesday windows, one before rollout and one after it. Check the property's available data and seasonal context before using that pattern; the dates alone do not make the periods commercially comparable.

In Search Console, open Search results, use the date comparison and keep search type, country and device fixed. Open Pages and select the affected page. Switch to Queries; export the visible rows with the filters. For a selected query, remove the page filter and open Pages to check which URLs appeared. The query/page routine walks through that switch.

Illustrative page/query pair Earlier clicks / impressions Later clicks / impressions Finding and next action
Reporting guide / dashboard requirements 40 /1,000 24 /1,000 CTR fell from 4% to 2.4%; inspect the same query's results, page answer and device detail
Reporting service / reporting consultant 20 /500 21 /525 CTR held at 4%; preserve the useful page while checking actual enquiries

The guide lost 16 clicks. That is not 16 lost leads, nor proof of a core-update cause. If the page inspection reveals a broken example or missing requirement, document that concrete repair. If it reveals no actionable defect, retain the finding and investigate the competing explanations instead of rewriting all pages.

Use the search review workbook to retain the filters, source views, hypothesis and next check. Record the repair date separately from any later movement.

Separate the observation from the diagnosis

Illustrative finding: several guides lost clicks while service-page enquiries stayed stable. That is worth investigating, but it does not yet establish a commercial decline or a content penalty. Group the affected queries, compare complete periods and inspect whether search appearances changed.

Add site releases, stock changes, promotions and tracking changes to the same timeline. Write two columns: what the records show, and what might explain it. Choose the smallest check that distinguishes the explanations. If an indexing restriction is confirmed, repair it; if the evidence remains inconclusive, continue monitoring rather than prescribing a wholesale rewrite.

Sources

A question about this article? Message Wendy

ZINC / Request for proposal

SEO

A clear brief.
A useful next step.

Turn search priorities into a scoped plan. Tell us about your business, scope and timing.

01 / Your business
02 / What you need
Build
Demand
Intelligence
03 / The context

Jaymie receives your request and coordinates the next step.

Tell us about your project and how to reach you.

ZINC DIGITAL.
ZINC / A conversation
Projects & conversations

Message Jaymie.

Have a question before writing a brief? Jaymie manages incoming inquiries and will help with the next step.

Delivered by email. Jaymie can reply to the address you provide.

ZINC / A conversation
Articles & editorial

Message Wendy.

Ask about an article, a source or an editorial detail. Your message goes directly to Wendy.

Delivered by email. Wendy can reply to the address you provide.