Google Core Update: How to Tell If You Were Hit, and What to Do

What is a Google core update?

Google runs many ranking systems. A core update changes the main ones at the same time, so it can move results for almost any query. It does not target one site, one niche or one trick. Google says most sites do not need to worry about core updates.

Three things it is not:

• Not a penalty. You get no message in Search Console. There is nothing to appeal.
• Not a spam update. Spam updates target sites that break Google's spam policies. They are announced separately.
• Not a manual action. Those are decisions by a person at Google and appear under Security & Manual Actions in Search Console.

Since March 2024, the old "helpful content" system is part of Google's core ranking systems. There is no separate helpful content update anymore. That is why Google's helpful content questions are now the main guide after a core update. (Google ranking systems guide)

Google core update dates: every one since 2024

From the Google Search Status Dashboard. "Done" is start date plus rollout length and can be off by a day.

Watch for overlaps. In March 2024 a spam update started the same day as the core update. In 2026 there have also been spam updates in March, June, August and September. If your drop falls inside two updates, you cannot tell from dates alone which one moved you.

How long does a core update take to roll out?

Since 2024, core updates have taken between 6 and 45 days. The two 2026 updates each took about 12 days. Rankings can swing up and down during the rollout, so the middle of a rollout is the worst time to judge it, and the worst time to change your pages. Every rollout length is in how long a core update takes, and 2026 in detail in Google core updates in 2026.

How to tell if a core update hit you (the 15-minute test)

This follows Google's own advice: wait at least one full week after the update is complete, then compare that week with a week before the update started. (Google: core updates)

1. In Search Console, open Performance, Search results.
2. Click the date filter, then Compare, then Custom.
3. "After" week: a full Monday to Sunday week that starts at least 7 days after the done date. "Before" week: a full Monday to Sunday week that ends before the start date.
4. Turn on clicks, impressions, CTR and average position.
5. Add a query filter with Custom (regex), "Doesn't match regex", and your brand names. Core updates mostly show up in non-brand searches.
6. Open the Pages tab and sort by Clicks Difference. Your biggest losers are at the top.
7. Click a losing page, then Queries, to see which searches dropped and by how many positions.
8. Check the same 3 months last year to rule out seasonality.

Worked example (fictional site)

northwind-outdoors.com sells camping gear. For the May 2026 core update it compares May 11 to 17 (before) with June 15 to 21 (Monday to Sunday) (after).

Brand is flat. Impressions and position fell. The same weeks last year were flat. That is a real ranking drop, not lower demand. Nine buying guides account for most of the lost clicks, while product pages barely moved. So the review starts with those nine guides, not the whole site.

How to read the result

• Position slid a little (say 2 to 4): normal. Google says small moves like this do not call for big changes.
• Position fell far (say 4 to 29) on a group of pages: the update re-judged those pages. Review them.
• Clicks down but impressions and position flat: not a ranking loss. Look at the results page itself, such as AI Overviews or new ad slots.
• Everything down, including brand: demand, seasonality, or tracking. Check Google Trends and analytics.
• Pages gone from Google: indexing problem or manual action. Check the Pages report and Manual actions today.

What Google says to do after a core update

Google's guidance is short. In plain words:

1. Confirm the update has finished on the Search Status Dashboard.
2. Wait a week, then compare the right weeks. Look at your top pages and queries.
3. Do not act on small drops.
4. For big drops, look at the site as a whole and ask honestly whether the content is helpful, reliable and made for people first.
5. Make real improvements, not quick fixes. Google calls deleting content a last resort.
6. Be patient (see recovery time below).

Google's self-assessment questions are the best tool for step 4 (we turned them into a scorable checklist). Here are a few, paraphrased:

• Does the page add original information, testing or analysis?
• Is it clearly better than what already ranks?
• Is it clear who made it and why they know the topic?
• Would a reader leave with what they came for, without searching again?
• Was it made mainly to attract search traffic, for example written to a word count, or with dates changed to look fresh?

Page-level review: a sample from the checklist

Here is section B of the page review, which you run on your 10 to 20 biggest losers next to the top 3 pages that now outrank them:

• The first screen answers the main question. No long intro.
• It has something only you can say: your test, your data, your photos, your price, your process.
• Facts, prices, specs and dates are current. Old screenshots replaced.
• The author or business is named, with a short reason to trust them.
• The title matches what the page delivers. No "ultimate" or "best" it does not earn.
• It is not one of several near-identical pages on your site for the same query.
• Ads, popups and affiliate boxes do not push the content below the fold.

The full checklist adds the search-intent check, site-level signals, technical rule-outs and a fill-in review sheet.

What to fix and what to leave alone

The most common mistake after a core update is doing too much. Rewriting 200 pages in a week loses the pages that were fine and teaches you nothing.

• Leave: pages that slid 1 to 3 positions, and pages that still rank and convert. They are your control group.
• Fix the title and snippet, not the content: pages that lost clicks but kept their position.
• Rethink: pages where the new top 3 serve a different intent (for example, product lists where you have a long guide).
• Improve: pages that fell far against similar pages with more to offer. Add your own data, steps and examples. Do not just add words.
• Merge: two or more of your pages chasing the same query.
• Remove, last resort: thin pages made only for traffic that you cannot make useful.
• Do not: change "last updated" dates without real changes, disavow links in bulk, or rewrite everything with an AI tool in a weekend.

How long does core update recovery take?

Google says some changes can take effect within a few days, but it can take several months for its systems to confirm that a site as a whole now produces helpful, reliable content. Google also runs smaller core updates that it does not announce, so gains can come between big updates. Plan on months, check monthly, and compare pages you changed with similar pages you left alone. That way you know whether your work helped or Google simply moved. More in core update recovery time.

If the drop was a spam update instead, Google says its systems may learn "over a period of months" that a site now complies, and value from links it has discounted does not come back. (Google: spam updates)

Who it is for

Site owners, marketers and small agencies who saw traffic move around a Google update and want a clear, calm way to find out what happened and what to do. No SEO tools needed: just Google Search Console.

Sources

All checked October 2026.

• Google Search's core updates (updated Dec 10, 2025)
• Creating helpful, reliable, people-first content (updated Oct 5, 2026)
• Debugging drops in Google Search traffic
• Google Search ranking systems guide
• Google Search spam updates (updated Dec 10, 2025)
• Google Search Status Dashboard, ranking history

Use SEOmatic to run the Google core update checklist on mysite.com.

Context: the last Google core update was the May 2026 core update (started May 21, 2026, done about June 2, 2026, per the Google Search Status Dashboard). Replace these dates if a newer core update has finished.

1. If I am not signed in, run check_site on mysite.com first, then connect_seomatic so you can read my Search Console data.
2. Rule out non-update causes:
- gsc_insights action sitemaps: any sitemap errors or stale sitemaps?
- site_audit: noindex leaks, canonicals pointing elsewhere, dead pages, broken internal links.
- Remind me to check Security & Manual Actions in Search Console myself (no SEOmatic tool reads that report).
3. Was I hit?
- gsc_insights action brand_split with my brand terms: [my brand names]. Report brand and non-brand separately.
- gsc_performance action compare_periods (dimension page, then query): list the biggest losers and winners by click change.
- gsc_performance action trend: show where daily clicks changed and whether that lines up with the update dates.
- gsc_insights action seasonality: is this drop normal for this time of year? If compare_periods cannot use my exact before and after weeks, say so and tell me which custom weeks to set in Search Console (before = a full Monday to Sunday week ending before the start date, after = a full Monday to Sunday week starting at least 7 days after the done date).
4. Classify each of my 10 to 20 biggest losing pages:
- small slide (about 1 to 3 positions): leave
- clicks down but position flat: snippet problem, check gsc_insights action ctr_outliers
- big fall: needs a page review
- two of my pages on the same query: check gsc_insights action cannibalization Use gsc_indexing action inspect on each big loser to confirm it is still indexed with the right canonical.
5. Page review for big losers: use site_pages action analyze and site_pages action crawl on my page, and gsc_performance action query_pages to see which queries it lost. Compare against Google's helpful content self-assessment questions (original info, clearly better than what ranks, clear author, current facts, no padding). Give me a table: page, clicks change, position before/after, verdict (leave / fix snippet / improve / merge / technical fix), and the reason.
6. Draft fixes, do not publish: for pages marked fix, use task_manage action create to stage proposals (for example content_refresh, ctr_fix, consolidate, canonical), then show_approval_cards so I can approve or dismiss each one. Do not touch pages marked leave.
7. End with a 90-day plan and a reminder to compare changed pages against untouched pages in 4 to 8 weeks.