A traffic drop near a Google update is a reason to investigate, not proof of a penalty. Compare equivalent data periods, check the update's official status, and rule out technical or measurement changes before rewriting the entire website.
01
Establish the timing and scope
Record when the decline began and whether it affects the whole site, a section, a device type, or particular queries. Check Google's announced update dates. Its core-update guidance recommends assessing performance after rollout rather than reacting to incomplete changes. Compare similar weekdays and note seasonal demand, campaigns, holidays, and major news that could alter search behavior.
02
Check what changed on your side
Review recent deployments, redirects, indexing directives, outages, analytics settings, and page removals. A broken template or accidental noindex can look like a ranking problem. In Search Console, compare clicks with impressions and query coverage. Fewer searches, lower positions, and fewer clicks on the same exposure are different diagnoses and call for different next steps.
- List affected URLs and representative queries.
- Check indexing and access for the most important pages.
- Keep a dated record of fixes and content changes.
03
Improve the problem you can demonstrate
If a service page no longer answers the query well, improve its substance, evidence, and usability. If a technical error blocks it, repair that error first. Do not remove useful material solely because a third-party tool shows a temporary fluctuation. Evaluate meaningful changes over a suitable period and keep expectations realistic: improvement is not guaranteed by reversing one suspected factor.
Frequently asked questions
Does a core update mean our site broke a rule?
Not necessarily. Broad ranking changes and specific policy actions are different. Check relevant Search Console reports before making that conclusion.
Should we change every page immediately?
No. Identify the affected patterns first. Simultaneous unrelated changes make it harder to determine what helped, and rushed edits can reduce useful content.
Continue with your next step
Related guides on this topic
Sources and policies
Check the current policy before submitting a request.
You do not have to figure out the next step alone.
Share the URLs and explain your concern. We will review the context and explain which options are worth assessing.
Request a confidential reviewOr call (307) 429-2531Educational information, not legal advice. Outcomes depend on the facts and decisions made by third parties.