Start With The Signal
Make sure the drop is real before you treat it like a crisis
Start by confirming what actually changed. Look at clicks, impressions, rankings, and landing page behavior together. If only one metric moved, or if the timing is unclear, the first job is to validate the signal rather than explain it too quickly.
Operator note
A drop that appears only in one report, one segment, or one annotation window may be a measurement or segmentation issue before it is an SEO issue.
Find The Pattern
Narrow the problem before you widen the investigation
Once the signal looks real, find out where it concentrates. The goal is to reduce the surface area. Check whether the drop is tied to a page type, template, directory, device, country, or keyword cluster. That pattern tells you what kind of checks matter next.
Useful slices
Page groups, templates, devices, locations, brand vs. non-brand, and new vs. established URLs.
Why it matters
A narrow pattern gives you a smaller set of likely causes and stops the team from auditing everything at once.
Check What Changed
Review recent releases, content shifts, and reporting changes
Before assuming the cause is external, review what changed internally. Releases, template edits, CMS changes, navigation updates, migrations, content removals, canonical shifts, and even dashboard logic can all create the appearance or cause of a drop.
Ask these questions
Run Technical Checks
Use a focused technical pass once you know what you are testing
Technical checks are most useful when they are tied to a working theory. If the drop is concentrated in a section, page type, or template, run checks that match that pattern instead of doing a broad audit with no priority.
Crawl and status code changes on impacted URLs
Indexing directives, canonicals, and redirect logic
Template or rendering changes that affect visible content
Internal linking shifts across key page groups
Sitemap coverage and page discovery signals
Measurement changes that may be misreading the drop
Avoid Common Mistakes
Do less guessing and more narrowing
Do not assume every drop is a technical problem before checking scope and timing.
Do not jump straight into a full-site audit when the issue may be limited to one section or template.
Do not change multiple things at once before you understand what you are trying to confirm.