Tired of aggressive WordPress admin notices? Learn why they happen and explore three battle-tested methods—from a simple plugin to a powerful mu-plugin—to reclaim your dashboard for good.

Death by a Thousand Banners: Reclaiming Your WP-Admin Dashboard

I remember a frantic Slack message from one of our junior engineers. We were an hour from launching a major client’s e-commerce feature. The message was just a screenshot of the WordPress dashboard, plastered with a giant, blinking “UPGRADE TO PRO NOW FOR 75% OFF!” banner from a new SEO plugin he’d just installed on staging. The client, who had editor access, saw it and thought we’d installed malware or broken the site. My coffee went cold. We spent the next 20 minutes calming everyone down and explaining that no, the site wasn’t compromised; it was just a victim of horrifically aggressive marketing. That day, I decided we needed a standard operating procedure for this nonsense. The WordPress dashboard is our workshop, not a billboard.

The “Why”: What’s Actually Happening Here?

Before we jump into the fixes, you need to understand the root cause. This isn’t a bug; it’s a feature being abused. WordPress provides a core hook called admin_notices. Legitimate plugins use this to display important information, like “Your caching plugin needs its settings updated” or “WooCommerce database update required.”

The problem is, plugin developers realized they could also use this hook to inject persistent, annoying advertisements, review requests, and upsell banners directly into your workspace. When you have 15, 20, or even 30 plugins running, it becomes a free-for-all, a digital shouting match where the only loser is you, the user trying to get work done.

The Fixes: From Band-Aid to Surgery

I’ve seen teams handle this in a few different ways, each with its own trade-offs. Let’s walk through them, starting with the simplest and moving to the most robust.

1. The Quick Fix: The “Install a Plugin to Fix Other Plugins” Method

I saw a Reddit thread the other day about a little plugin called “Clean Admin,” and it’s a perfect example of this category. The idea is simple: you install one more lightweight plugin that’s designed to find and hide the notices injected by others. It’s a quick, effective solution, especially for less technical users or situations where you can’t or don’t want to touch code.

It usually works by using CSS or JavaScript to hide the notice `div` elements. It’s fast, easy, and requires zero configuration. But let’s be honest, it’s a band-aid. You’re still loading the code that generates the notices; you’re just hiding it from view.

Pro Tip: This is a great solution for client sites where you want to provide a clean experience without adding complex custom code they might accidentally break later. It’s a low-risk, high-reward cleanup.

2. The Permanent Fix: The “MU-Plugin” Method

This is my preferred approach and what we use at TechResolve as part of our standard WordPress boilerplate. We create a “must-use” plugin (a PHP file in the /wp-content/mu-plugins/ directory) that surgically removes the unwanted actions at the source.

Instead of just hiding the output with CSS, you’re telling WordPress not to even run the functions that generate the notices in the first place. It’s more efficient and gives you granular control.

Here’s a simple but powerful snippet to get you started. Create a file like techresolve-admin-cleanup.php inside /wp-content/mu-plugins/:

<?php
/*
Plugin Name: TechResolve Admin Cleanup
Description: Removes non-critical admin notices to declutter the dashboard.
*/

function tr_remove_all_admin_notices() {
    // Don't run this for network admins, they might need to see everything.
    if ( is_network_admin() ) {
        return;
    }

    // Only run for users who can't manage plugins.
    // Let the admins see notices so they know when updates are needed.
    if ( current_user_can( 'manage_options' ) ) {
        return;
    }

    remove_all_actions( 'admin_notices' );
    remove_all_actions( 'all_admin_notices' );

    // You could add a specific notice back here if you wanted to.
    // For example, add_action('admin_notices', 'my_custom_important_notice');
}

add_action( 'admin_init', 'tr_remove_all_admin_notices', 99 );

This code is smart. It removes all notices, but only for users who aren’t administrators. This means your clients (Editors, Authors, etc.) get a pristine, clean dashboard, while you, the administrator, can still see important messages about plugin updates or potential issues on `prod-web-01`.

3. The ‘Nuclear’ Option: Client-Side CSS Injection

Sometimes you’re on a locked-down system where you can’t add mu-plugins or you just want to clean up your own view without touching the site’s code. This is a hacky, “in the trenches” solution, but it’s incredibly effective for a development team’s internal sanity.

You use a browser extension like Stylus or Tampermonkey to inject your own CSS rules on any WordPress admin page you visit. You’re not changing the site; you’re changing how your browser renders it.

Here’s a simple CSS snippet you could load via a browser extension:

/* My Personal WP-Admin Cleanup */
div.notice,
div.updated,
div.error,
div.update-nag {
    display: none !important;
}

/* Make an exception for truly critical stuff, like from WooCommerce */
div.woocommerce-message {
    display: block !important;
}

Warning: This is a sledgehammer. The display: none !important; rule is aggressive and can hide legitimate error messages. Use it with caution and be prepared to disable it if you’re debugging something on `staging-db-02` and can’t figure out why an error isn’t showing up.

Which Solution is Right For You?

There’s no single best answer; it depends on the context. Here’s how I break it down for my team:

Ultimately, our job is to build stable, usable systems. A chaotic dashboard filled with ads isn’t usable. It introduces noise, confuses clients, and buries critical information. Take ten minutes, pick a method from above, and give yourself—and your clients—the clean workspace you deserve.

Darian Vance

Lead Cloud Architect & DevOps Strategist

With over 12 years in system architecture and automation, Darian specializes in simplifying complex cloud infrastructures. An advocate for open-source solutions, he founded TechResolve to provide engineers with actionable, battle-tested troubleshooting guides and robust software alternatives.

🤖 Frequently Asked Questions