If your Search Console graph looks like it drank three espresso shots, relax. Core updates do that.
The bad response is panic edits. The worse response is content spam dressed up as “AI strategy.”
What happened
Google confirmed a May 2026 core update rollout on the Google Search Status Dashboard. These rollouts can take time. Your analytics will wobble while it settles.
Earlier this month, Google also updated its Search Essentials spam policies to call out two things a lot of marketers are currently flirting with:
- Scaled content abuse. Publishing tons of pages with little effort, little originality, and little value.
- Manipulating AI answers. Creating content primarily to influence how your brand shows up in generative AI responses.
If your core update plan is “publish 60 new AI blog posts,” you are not fixing anything. You are adding risk.
The move people will regret this week
Here is the sequence that keeps repeating:
- Traffic dips during a rollout.
- Someone declares the website “stale.”
- A tool turns on the content firehose.
- You publish a pile of near-duplicate pages that read fine but say nothing.
- Now you have two problems: volatility and bloat.
This is how you get yourself into a scaled-content mess. If you need the blunt warning label, read the policy directly: Google spam policies: scaled content abuse.
And if you are trying to game AI answers with “GEO content,” also read this part: Google spam policies: manipulating generative AI responses.
That policy language matters because it matches what we are seeing in the wild: people trying to brute-force AI citations with template pages.
A no-panic triage plan
Here is what to do instead. It is boring. It works.
Step 1: Save the baseline before you touch anything
Screenshot the trend lines. Export your last 28 days of Search Console queries and pages. Write down what changed on the site this month. Real changes, not vibes.
If your tracking is already messy, fix that first. Start here: UTMs Without the Tears.
Step 2: Separate brand demand from everything else
If branded traffic drops, you might have a trust problem, a visibility problem, or a tracking problem. If non-branded drops, you might have a relevance problem.
Do not treat those as the same problem. You will choose the wrong fix.
Step 3: Identify the pages that lost, then read them like a skeptical prospect
Pick five pages that used to pull impressions and clicks. Now read them cold.
- Do they answer the real question, or do they circle it?
- Do they show proof, or do they say “we deliver results” and hope nobody asks for receipts?
- Would you send a friend to this page, or would you apologize first?
If you want a strong content fix that is not “add more words,” build proof assets. Case studies, before-and-after examples, real constraints, real outcomes. Here is a template: Case Studies That Close Deals.
Step 4: Consolidate. Delete. Noindex. Be decisive.
If you already published a stack of thin pages, do not keep them “just in case.” That is content debt.
Merge duplicates into one good page. Redirect the rest. If a page exists only because a tool could generate it, it probably should not exist.
Step 5: If you use AI, force it to earn its keep
Use AI to speed up drafting, editing, and formatting. Fine. But do not let it invent your point of view.
Minimum standard for any AI-assisted page:
- One clear claim you can defend.
- At least one concrete example from real work, a real workflow, or a real decision.
- A reason to exist that is not “we need more content.”
If you need a lightweight governance rule set, steal this: AI Content Provenance.
How to make AI actually quote you
If your plan is “publish the same answer 40 times with different headings,” you are building a landfill.
If your plan is “publish a few pages that have real structure, real authorship, and real proof,” you have a shot. Start here:
- GEO: How to Become the Business AI Recommends
- AEO: How to Make AI Quote You Instead of Guessing
- Google Search Is Becoming an Action Engine
Need a calm core update plan?
We can help you diagnose what changed, fix what matters, and keep your content system from turning into a panic project.