Update nags, review begs, upsell boxes — WP Nag Silencer captures every admin notice, names the plugin that shouted it, and suppresses the noise into a tidy log. You choose exactly what surfaces, and a weekly digest proves nothing important was lost.
FROM $49/YEAR · LIFETIME OPTION · 14-DAY GUARANTEE
“The client logged in to approve one page and emailed straight back: is the site broken? There are 11 red banners at the top.”— First client login, every agency
Those banners are update nags, review begs and upsell boxes — plugins talking to you, in front of your client. WP Nag Silencer captures every one, names the plugin that shouted it, and lets you choose exactly what surfaces.
The plugin buffers every admin notice before it renders, records who shouted it, and re-prints only what your rules allow. The rest waits quietly in the log — and reports in on Friday.
Each admin notice is captured as WordPress renders it and traced to the plugin or theme that produced it — with its type (update nag, review beg, upsell box), the screen it appeared on and how often it repeats. The dashboard chaos becomes a named list: who shouts, what about, and how much.
Nag Silencer ships in observe mode: for the first week it logs everything and hides nothing. You see a week of real evidence — which plugin nagged, how often, on which screens — before a single rule takes effect. Rules written against evidence, not guesses.
Global show/hide rules per plugin in the free edition; Pro adds per-role rules — clients see calm, admins see everything — and per-notice fingerprint rules for surgical control over one specific banner. Hidden notices go to the log, not the bin. It pairs with white-label admin tools without overlapping them: white-labelling changes how wp-admin looks, Nag Silencer governs what it says.
Form feedback — settings saved, validation errors — always shows. Core update and security notices are exempt unless you flip an explicit opt-in toggle. The plugin's own licence notices stay visible. And if anything unexpected goes wrong, the plugin fails open and shows everything — suppressing wrongly is worse than noise.
Once a week, a digest of everything that was hidden: which plugin, what kind of nag, how many times, plus what was allowed through. Review it in two minutes, promote anything that deserves the dashboard. Pro sends it by email, so silence never turns into ignorance.
Print-ready HTML and a real downloadable PDF in your agency's logo, name and colours: the noise we managed for you this month. The hidden-notice league table, what was surfaced, what was protected — retainer reporting that shows the invisible work you actually did.
The client sees 11 banners and assumes something's wrong. With per-role rules their account sees a calm dashboard — while yours still sees everything you chose to keep.
Handing a finished site to a client? Hand over a dashboard that looks finished — no half-configured plugin begging for a review on day one of their ownership.
Care-plan clients ask what they pay for. The branded digest report answers on paper: the noise we managed for you this month, itemised by plugin, your logo on top.
Inherit a site and the observe week maps the shouting before you touch anything: which plugins nag, how often, on which screens. Then you silence with evidence.
Plugin updates arrive with fresh promo banners attached. Existing rules catch the returning nags automatically, and the digest lists any new voice that appeared.
The same rules, digest and report on every client site, one licence across the fleet. Every dashboard calm, every hidden notice logged, nothing silently lost anywhere.
Eleven banners down to the one that mattered — 23 notices hidden, 1 surfaced, 0 lost. One line the client understands, backed by the itemised log behind it.
Every silenced notice grouped under the plugin that shouted it — nine review nags here, six upsell banners there. This is the answer to “what noise are we actually living with?”, named and counted.
What the rules let through on purpose, like a core update notice. The digest shows both directions, so hiding never becomes hoping — you can see the judgement calls and revisit them.
Everything hidden is in the log with its owner; nothing was deleted. On Pro this whole page becomes the branded report — print-ready HTML and a real PDF in your agency's colours, ready for the retainer email.
The usual options: live with the noise, paste a CSS snippet that hides every notice, or white-label the admin. Here's what changes against the fix most people paste first.
| WP Nag Silencer (us) | CSS hide-everything snippet | |
|---|---|---|
| Knows which plugin shouted each notice | ✓ Attribution built in | ✗ Hides blind |
| Keeps a log of what was hidden | ✓ Everything logged + weekly digest | ✗ Gone without record |
| Form feedback still shows | ✓ Always, no exceptions | ✗ “Settings saved” vanishes too |
| Security & core update notices | ✓ Shown unless you opt in | ✗ Hidden silently |
| Choose per plugin, per role | ✓ Per plugin; per role on Pro | ✗ All or nothing |
| Safe failure mode | ✓ Fails open — shows everything | ✗ Fails hidden |
| Client-ready evidence | ✓ Branded report + PDF (Pro) | ✗ Nothing to show |
| Free to run | ✗ From $49/yr | ✓ Free |
The snippet does make the dashboard quiet — by hiding your own settings feedback and the security notices along with the nags, with no record of any of it. Full comparison →
Every plan includes every Pro feature — per-role rules, per-notice fingerprints, the weekly email digest and the branded report with the PDF. You're only choosing how many sites.
Up to 10 sites
25 sites · for agencies
Up to 100 sites
Up to 100 sites, forever
Prices in USD. Licence keys are domain-based — no accounts, no phoning home. VAT invoices available.
Plugins print their banners through the WordPress admin-notice system. Nag Silencer buffers that output just before it renders, records each notice with the plugin that produced it, and then re-prints only what your rules allow. Everything captured lands in the log with its owner, its type — update nag, review beg, upsell box — and the screen it appeared on. Nothing is deleted; hidden means logged instead of shouted.
Three answers, by design. First, the plugin ships in observe mode: for the first week it logs everything and hides nothing, so you write rules against a week of real evidence. Second, the weekly digest lists every notice that was hidden, so nothing disappears unreviewed. Third, if anything unexpected goes wrong during capture, the plugin fails open and shows everything — suppressing wrongly is worse than noise, so the failure state is a loud dashboard, never a silent one.
Not unless you explicitly ask it to. Core update and security notices are exempt from all rules by default and only ever hidden through a separate opt-in toggle with its own warning. Form feedback — the "settings saved" and validation-error notices your own actions produce — always shows, on every screen, for every role, with no toggle to change that.
It's built not to. Nag Silencer doesn't patch, hook into or modify other plugins — it buffers the shared notice output that WordPress itself renders, which every plugin writes to the same way. There's nothing plugin-specific to break when someone ships an update. And if a plugin does something unusual that the capture doesn't recognise, the rule for that situation is fail open: the notice shows rather than risking a wrong suppression.
For the first week after activation the plugin captures and attributes every notice but hides none of them. You get a full log of what your dashboard actually shouts — which plugin, how often, on which screens — before a single rule takes effect. Then you write rules against evidence instead of guesses. You can end observe mode early or extend it; it's a setting, not a countdown you can't touch.
Free is the full engine: every notice captured and attributed, the complete log, and global show/hide rules per plugin — enough to make any single dashboard calm. Pro (for agencies) adds per-role rules so clients see calm while admins see everything, per-notice fingerprint rules for surgical control over one specific banner, the weekly email digest of what was hidden, and the branded digest report — print-ready HTML and a real downloadable PDF in your agency's logo and colours.
On Pro, yes — that's the headline feature. Rules apply per role: the client's editor account gets the calm dashboard, your admin account still sees every notice if you want it to. The client stops asking whether the site is broken; you stop missing the one banner that mattered.
No, and the two pair well. White-labelling changes how wp-admin looks — logos, colours, menus. Nag Silencer governs what wp-admin says — which notices surface, which are logged instead. Run both: one handles the branding, the other handles the shouting, and neither touches the other's job.
Order through the form and your licence key and invoice arrive by email, usually within the hour. Keys are long codes starting VPC1. — paste the whole thing into the licence textarea rather than typing it. Domain-based, no account, no phoning home, no lock-in.
14-day money-back guarantee, no questions. Email us and we refund you.
Order below and your licence key and invoice arrive by email — usually within the hour. Install it, let the observe week map the shouting, and the next client login lands on a dashboard that says only what you chose.
14-DAY MONEY-BACK GUARANTEE · SUPPORT BY ACTUAL HUMANS