When wp-admin fills with banners, the usual responses are: live with it, paste a CSS snippet that hides everything, or install a white-label admin plugin. Here's the honest breakdown against all three.
Doing nothing costs nothing and trains everyone to ignore the top of the dashboard — which is exactly how the one banner that mattered gets scrolled past. CSS hide-everything snippets (.notice { display:none } and friends) make the dashboard quiet by hiding blind: your own “settings saved” feedback vanishes, security warnings vanish, and nothing is logged anywhere. White-label admin plugins do a different job well — they change how wp-admin looks, its logos, colours and menus, but the notices still say what they say. WP Nag Silencer (this site) governs what wp-admin says: it captures every notice, attributes it to the plugin that shouted it, suppresses the noise into a log you can read, keeps form feedback and core security notices safe by hard rule, and reports what was hidden in a weekly digest — per role and per notice on Pro, with a branded report and PDF for the retainer file.
| Feature | WP Nag Silencer | Doing nothing | CSS hide-all snippet | White-label admin plugins |
|---|---|---|---|---|
| Knows which plugin shouted each notice | ✓ Attribution built in | ✗ You read them all | ✗ Hides blind | ✗ Not its question |
| Quietens the dashboard | ✓ Rule by rule, you choose | ✗ Eleven banners stay | ✓ Brutally | ◐ Some hide notices site-wide, all-or-nothing |
| Keeps a log of what was hidden | ✓ Everything, with its owner | ◐ Nothing hidden to log | ✗ Gone without record | ✗ No log |
| Form feedback still shows | ✓ Always — hard rule, no toggle | ✓ Everything shows | ✗ “Settings saved” vanishes too | ◐ Depends on the plugin |
| Security & core update notices safe | ✓ Shown unless you explicitly opt in | ✓ Shown (among the noise) | ✗ Hidden silently | ◐ Depends on the plugin |
| Different view per role | ✓ Clients calm, admins informed (Pro) | ✗ Everyone sees everything | ✗ Everyone sees nothing | ◐ Menus yes, notices rarely |
| Proof nothing important was lost | ✓ Weekly digest + fail-open guard | ◐ Nothing lost, nothing gained | ✗ Hoping | ✗ Hoping |
| Client-ready evidence | ✓ Branded report + PDF (Pro) | ✗ Nothing | ✗ Nothing | ✗ Nothing on paper |
| Rebrands wp-admin's look | ✗ Different job — pair them | ✗ No | ✗ No | ✓ That's the job |
| Cost | From $49/yr · $599 lifetime | Free | Free | Free to ~$100/yr |
You're the only person who ever logs in and the noise genuinely doesn't bother you — doing nothing is free and honest. And keep your white-label plugin: rebranding wp-admin is real work done well by tools built for it, and Nag Silencer pairs with them without overlap — white-labelling changes how wp-admin looks, Nag Silencer governs what it says. The one alternative we'd talk you out of is the CSS snippet: it hides your own settings feedback and the security notices along with the nags, keeps no record, and fails hidden instead of failing open.
Clients log in to dashboards you look after, and you want every notice captured, attributed to the plugin that shouted it, and silenced on your terms — with form feedback and security notices protected by hard rules, a weekly digest proving nothing was lost, and, on Pro, clients seeing calm while admins see everything, plus a branded report for the retainer file. That's us.
One honest line: hidden means logged, not deleted — and the safety rules are not settings you can trip over. Form feedback always shows, core security notices need an explicit opt-in to hide, the plugin's own licence notices stay visible, and any unexpected error fails open and shows everything. Suppressing wrongly is worse than noise.