John Mueller answered a question on Reddit that a lot of people fixing a traffic drop need to hear. Recovering rankings after you fix the underlying problem can take many months, and with disavow files specifically he pointed to a window of roughly three to six months. Here is what he said, why the delay happens, and how to run your recovery so you actually learn something from it.
What Mueller Said
The question came from someone in the r/SEO subreddit dealing with a ranking drop and wondering how long a disavow file would take to have an effect. Mueller's answer, given on September 3, 2026, was that he would expect it to take somewhere in the range of three, four, five, or six months.
On the broader point, he said fixing issues tied to bigger algorithmic changes can take quite some time, and sometimes many months.
He also gave a piece of advice that is easy to skip past. Get the disavow file into the shape you actually want it in, then go look for other potential reasons for the drop. In other words, do not treat the disavow as the answer and then sit and wait.
The Caveat That Matters Most
Mueller pointed out that if your rankings dropped within days, that drop is probably not related to your disavow submission at all.
This is the detail I would underline. A fast drop and a slow recovery mechanism do not fit together. If your traffic fell off a cliff over a weekend, the disavow file you uploaded is almost certainly not the cause, and not the fix either.
One of the biggest mistakes I see is somebody watching traffic fall, immediately uploading a disavow file, and then treating every week without recovery as evidence the file needs more domains added to it. That is how you end up disavowing links that were helping you.
Why Recovery Is Slow
The delay is not Google being difficult. It comes from how the systems actually work.
- Links get reprocessed incrementally. Google does not re-evaluate your entire link profile the moment you upload a file. It works through links over an extended period, so the effect arrives gradually rather than on a switch.
- Broader updates need time to reassess your site. When a spam or core update is involved, the system has to encounter and reassess your content, which does not happen in a day.
- Large technical problems need complete fixes. A partial fix on a site-wide issue produces a partial signal, and Google has to crawl enough of the site to see the change.
How To Run A Recovery You Can Learn From
If the feedback loop is three to six months long, the way most people approach a recovery guarantees they will never know what worked. Here is the process.
- Write down the date the drop started. Not the week you noticed it. The actual date in your Search Console data.
- Match that date against known updates before you touch anything. Check it against the May 2026 core update and the August 2026 spam update. If your drop lines up with a confirmed update, that is your most likely explanation and no disavow file is going to address it.
- Change one thing at a time, and log it with the date. With a multi-month lag, five simultaneous changes give you one ambiguous outcome. One change gives you an answer.
- Keep working while you wait. Mueller's own advice was to keep looking for other causes. Waiting is not a strategy.
- Set a real review date. Put a calendar reminder three months out. Checking rankings daily during a multi-month reprocessing window only makes you anxious and impatient.
My Take On Disavow Files In General
I would use a disavow file far less often than most people do. It is a tool for a specific situation, which is a genuine unnatural link problem, usually one you or somebody working for you created. It is not a general purpose recovery button.
If you did not build spammy links and you have no manual action in Search Console, a disavow file is very unlikely to be your fix, and now you know it will cost you three to six months to find that out.
The good news? A drop that lines up with an update often recovers on its own or with content work rather than link surgery. The July 11 update partially reversing itself is a good reminder that not every drop is a verdict on your site.
From there, the durable move is the same as always. Doing the keyword research and fixing the fundamentals beats waiting six months on a file that was never the problem.
Question to Answer:
Do you know the exact date your traffic started dropping, and does that date line up with a confirmed Google update?
In Summary
Mueller put disavow file effects in a three to six month range and said broader algorithmic recovery can take many months. He also noted that a drop happening within days is probably unrelated to a disavow submission, which is the part most people miss.
Find your drop date, check it against confirmed updates first, then change one thing at a time and write down when you did it. A long feedback loop only teaches you something if you can tell which change caused what.
0 comments