PLAYBOOK
Traffic dropped.
Here's how to find out why.
A drop in organic traffic has a short list of possible causes. The hard part is working through them in the right order, before the guessing starts. This playbook takes you from "something's wrong" to a named cause and a fix, using the data SEORCE already holds for your site.
Traffic is down, and nobody knows why yet.
Organic visits are well down on last week, and someone has already asked you why. At this point you can't say whether it's the site, Google, the season or the tracking. You need a cause before you can give an answer, and guessing in the meantime tends to make things worse.
"Organic traffic is down, and I don't know where."
The total has dropped. You can't yet say which pages, which searches or which day it began.
"Did something change on the site last week?"
There was a release. Nobody is sure what was in it, or whether it touched anything that matters for search.
"Is this a Google update, or is it us?"
One of those you can fix today. The other you can't. Until you know which, you can't plan anything.
Five steps, in this order.
Each step rules something out, which is why the order matters. Skip one and you can spend a week fixing the wrong thing.
Confirm the drop
Check the tracking before anything else. Compare your analytics with Search Console clicks. If only one of them fell, the problem is measurement.
Search Console analytics →AI search analytics guide →Where it fell, and since when
Narrow it down by channel, then by section, then by page. Find the day it began. A drop that starts on one day points to an event.
Page performance →Traffic sources →What changed on that day
Compare the crawl before and after. Then check rankings and lost links for the same pages. Work down the list until something matches the date.
Site audit →Lost links →Free: Redirect chain tracer →Free: Robots.txt conflict checker →Repair the cause
Safe fixes are applied on the live site. Anything in a template or on the server goes to your team with the change worked out.
AutoFix →Automated technical SEO guide →Mark it and watch
Add a marker on the day the fix went live. Then follow the same pages until they are back where they were.
SEO uplift →SEO reporting guide →Rule out the obvious while the crawl runs.
Test one affected URL by hand. A redirect that loops, or a robots rule that blocks pages in your sitemap, will show up straight away.
What each step looks like in practice.
Ledgerly is our demo account, a B2B accounting tool for agencies. This is its drop, worked through.
Confirm the drop
Tracking breaks more often than people expect. A release that removes the analytics script looks exactly like a traffic collapse.
- Two sources, side by sideSearch Console counts clicks at Google. Your analytics counts visits on the site. They should move together.
- Only organic, or everything?If every channel fell on the same day, look at the tracking first.
- The same week last yearSearch Console history goes back 16 months, so you can rule out the season.
Where it fell, and since when
A total hides everything useful. The drop almost always belongs to one section, and it almost always has a start date.
- By section and pageSort landing pages by the change in visits. The losers usually share a template or a folder.
- By querySee which searches lost clicks, and whether position or impressions fell with them.
- The day it beganA sudden step down points to an event. A slow slide points to competition or ageing content.
What changed on that day
Now you have pages and a date. Check each possible cause against them, starting with your own site.
- The crawl, before and afterCrawl history shows which issues are new since the last run, so a release's damage stands out.
- Rankings on the same pagesIf positions fell, the cause is on the page or in the links. If they held, look at the results page itself.
- Links lostCheck whether referring domains to those pages dropped away.
- AccessConfirm that robots.txt still lets search bots reach the section.
Repair it, then mark the day.
A canonical tag that points at the wrong page has one correct answer, so software can apply it. The template still needs fixing at the source.
- Fixed on the live pagesAutoFix corrects the tag on each page and logs the before and after.
- The source goes to your teamThe template fault is passed on with the exact change to make.
- Checked on the next crawlIf a deploy overwrites the fix, it comes back as a new finding.
- A marker on the chartAdded on the day of the fix, so recovery is read against it.
<link rel="canonical" href="https://ledgerly…/"><link rel="canonical" href="https://ledgerly…/features/multi-currency">Reading the pattern: what Search Console is telling you
| What you see | Clicks | Impressions | Position | Most likely cause |
|---|---|---|---|---|
| Everything fell together | Down | Down | Down | Rankings were lost. Look for a technical fault, lost links or a stronger competitor. |
| Clicks fell, the rest held | Down | Steady | Steady | Fewer people click. The results page changed, for example an AI Overview now sits above you. |
| Clicks and impressions fell | Down | Down | Steady | Fewer people are searching. Check the season and the same week last year. |
| Search Console is steady | Steady | Steady | Steady | Your analytics is wrong. Check that the tracking script is still on the page. |
| One section fell, the rest held | Down | Down | Down | Something changed on that section. Check the last release and its template. |
What the team knew before and after.
Traffic hasn't recovered at this point, and that's normal. What has changed is that the team can name the cause and has already acted on it.
When the drop was spotted
- –Organic traffic was down on last week
- –Nothing about which pages or which searches
- –Nothing about when it began, or why
- –Three theories, and no way to choose between them
A few hours later
- ✓The drop was confirmed, and organic only
- ✓It was 86 feature pages, since Tuesday's release
- ✓Canonical tags were pointing at the homepage
- ✓The pages were fixed, and the template was with engineering
We haven't shown the recovery. How quickly rankings return is up to the search engine, and no playbook controls that.
The same steps, whoever is holding the problem.
How do you recover from a traffic drop with SEORCE?
Work through five steps in order. Confirm the drop by comparing Web Analytics with Search Console clicks. Locate it by section, page and start date. Diagnose it by comparing the crawl before and after that date, then checking rankings and lost links. Fix the cause, with AutoFix applying the safe changes on the live site. Then add a marker and watch the same pages recover.
Key facts
- Check the tracking first. A missing analytics script looks the same as a collapse
- A drop that starts on one day points to an event, such as a release. A slow slide points to competition or ageing content
- If clicks fall while position holds, the results page changed. Your pages did not
- SEORCE keeps crawl history, so issues that are new since the last run stand out
- Search Console history goes back 16 months from the day you connect, which lets you rule out the season
- No tool controls how quickly rankings return after a fix
Last reviewed 15 October 2026 by the SEORCE team.
Frequently asked questions.
A sudden drop usually has one of five causes: a tracking fault, a technical change on your site, lost rankings, a change to the results page, or a fall in demand. A drop that begins on a single day points to an event, most often a release.
Compare two sources. Search Console counts clicks at Google, and your analytics counts visits on the site. If Search Console is steady and analytics fell, the tracking is broken.
Look at the shape. A problem on your site usually hits one section, starting on the day of a release. A change at Google tends to affect pages across the site, with no change in your crawl. Check your own site first, because that is the part you can fix.
Yes. When an AI Overview appears above the results, fewer people may click through even though your position hasn't moved. In Search Console that shows as falling clicks with steady impressions and position.
It depends on the cause and on the search engine. After a technical fix, the pages have to be crawled again before rankings can return, which takes days to weeks. No tool can promise a date.
For safe fix types, yes. AutoFix applies fixes such as canonicals, meta tags and schema on the live site and logs each one. Anything in a template or on the server goes to your team with the change worked out.
No. SEORCE has no GA4 connection. It connects to Google Search Console, and Web Analytics collects visits from one line of code.
For individual checks, yes. The redirect tracer, the robots.txt and sitemap conflict checker and the sitemap indexability checker each check one thing, and the browser extension audits the page you're on. Finding which pages dropped needs your analytics and Search Console data.
Find what changed on your site.
Add your site and connect Search Console. You'll see where traffic comes from, what the crawl found, and what is new since last time.
Not ready for an account? Use the free browser extension or any of the free tools.