How an algorithmic demotion works
Google’s ranking systems classify pages and sites continuously. When a classifier decides that something falls short — about a page, or in some systems about a site as a whole — it can rank that material lower or stop showing it for queries it used to win. No person reviews the case, no notice is sent and nothing appears in Search Console, because from Google’s point of view nothing has been done to you: the systems simply scored you differently this time.
That is the difference from a manual action, which is applied by a human reviewer, carries a message in Search Console, names the policy breached, and can be appealed once fixed. A demotion has none of those features. It is a change of judgement rather than a sanction, and it is far the more common of the two.
Why algorithmic demotion matters
Because the diagnosis is entirely yours to do. With no message to read, the drop has to be reconstructed from evidence: which pages and which queries lost ground, when the change started, whether it lines up with an announced update, whether a redesign or a migration happened in the same week, and whether competitors moved at the same time.
It also sets the recovery expectation. Fixing the cause does not switch rankings back on. Google has to re-crawl the changed pages and, for some systems, reassess the site on a later run, so the gap between doing the work and seeing the result can be long — and there is nobody to ask about it while you wait.
Where algorithmic demotion goes wrong
The most expensive mistake is guessing. A drop gets blamed on whatever the team read about most recently, work starts, and nothing improves because the real cause was a template change that quietly removed internal links. Establish the date and the shape of the loss before touching anything.
The second is calling every drop a demotion. Traffic falls for duller reasons too: seasonality, a competitor publishing something better, a core update re-ranking a whole topic, a broken tracking tag, a page left on noindex after a redesign. The third is making small changes every week, which destroys your ability to tell what worked.
What to do about it
Start with the Manual Actions report, because a message there means this is not an algorithmic problem at all. Then compare like with like in Search Console: the same period year on year, split by page and by query, so you can see whether the loss is site-wide or concentrated. A loss confined to one section usually points at something you changed; a loss spread across everything usually points at a judgement about the site.
Fix the substance rather than the symptoms, make changes in a dated batch, then leave it alone long enough to read the result. Where the cause is content quality rather than a technical fault, expect months rather than weeks, and treat any promise of a quick reversal with suspicion. Work of this kind is what penalty recovery covers.