Search demotion is reduced visibility caused by ranking systems, technical barriers, quality problems or a manual action that needs diagnosis.
Scope and boundary
A search demotion is reduced visibility caused by ranking systems, technical barriers, quality problems or a manual action; diagnosis must identify the mechanism first.
Practical workflow
Build a dated baseline of affected URLs, query groups, indexing state, directives and releases. Check Manual actions before labelling a change algorithmic; crawl affected paths and compare an unaffected control group.
Apply Pessimisation to a concrete condition
A demotion investigation starts by separating possible mechanisms. For example, if a set of pages loses impressions after a release, compare the release time with canonical, robots, response and rendering changes before looking for an algorithm label. If only queries or demand changed while pages remain indexable, document that difference instead of applying a global template change. Use a matched unaffected page set so that normal seasonal variation is not confused with a site-wide technical cause.
What to verify
For a release example, compare HTML, canonical tags, robots directives and status codes before and after the suspected deployment for a small affected set. If the route is now redirected, blocked or materially thinner, that is a concrete repair target; if those signals match the prior state, broaden the investigation cautiously. Keep the timeline of observation separate from the explanation. A coincident date does not establish that an update caused a visibility change.
Common mistakes
Avoid broad rewrites, disavowals or noindex changes based on a chart alone.