WP Updates Notifier
by Scott Cariss 4.2 (35 reviews)

WP Updates Notifier

Get an email when your WordPress site has core, plugin or theme updates waiting.

WP Updates Notifier ranks #1,175 among WordPress.org plugins with 20,000+ active installations, is #63 of 1,658 in the Performance category, a 4.2/5 rating from 35 reviews, and was last updated Oct 27, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.4
v2.0.0 Current Version v2.0.0
Updated 1 week ago Last Update on 27 Oct, 2026
Refreshed 1 week ago Last Refreshed on
#63 of 1,658 in Performance Top 5% by installs Downloads -82.7% this week Actively maintained
View on WordPress.org
Rank
#1,175
— No change
Active Installs
20K+
-38.6%
KW Avg Position
73.3
0.3 worse
Downloads
249.8K
+66 today
Support Resolved
0%
— No change
Rating
84%
Review 4.2 out of 5
4.2 (35 reviews)

Next Milestone 30K

Total Progress 75.1%
20K+ 30K+
92
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

  • Exact install estimates within tiers
  • Track install growth over time
  • Milestone progress predictions
Upgrade to Pro
Need 2,494 more installs to reach 30K+

Rank Changes

1,116 1,146 1,175 1,204 1,234 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
1,026 1,068 1,110 1,152 1,195 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
Current #1,175
Change
Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

50 100 150 200 250 300 350 400 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
0 1K 2K 3K 4K 5K 6K 7K 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
Downloads
Growth
Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

4.2
35 reviews
Overall 84%
5
23 (66%)
4
6 (17%)
3
0 (0%)
2
1 (3%)
1
5 (14%)

Security History

Source: WPVulnerability

No known vulnerabilities on record for WP Updates Notifier. Checked 2 weeks ago.

TL;DR

AI summary of the plugin's readme

This plugin is for WordPress site owners and administrators who don't log in regularly or who manage client websites. It solves the problem of missing important core, plugin, and theme updates by monitoring for them and sending email notifications.

  • Configurable update check interval
  • Email notifications for core updates
  • Email notifications for plugin updates
  • Email notifications for theme updates
  • Notify only active themes/plugins
  • Remove upgrade nag message
  • Filters and actions for advanced users
  • Set custom from/to email addresses

Frequently Asked Questions

Common questions about WP Updates Notifier

Check these in turn: Was it already reported? Each channel is told about each version once. See How notifications work.
Does a setting leave it out? On the General tab, the setting for that kind of update must not be No, and if it is limited to active plugins or themes, the plugin or theme must be active. Check the channel's Routing column too. Did the send fail? Last delivery shows Failed and the reason. Has the check run? Last checked on the General tab says when. If it is old, see the next entry.
Emails only arrive after someone visits the site The schedule is run by WP-Cron. WP-Cron is not a real clock. WordPress only looks for due tasks when a page is requested, so on a site that few people visit, a check due at 03:00 can wait until someone arrives at 09:00. A forum user put it as "I only receive emails after someone has logged in". To fix it, run WP-Cron from the server's own clock. See How do I run the check from a system cron?.
There are two ways. Use the first unless you have a reason not to. Request wp-cron.php Stop WordPress starting WP-Cron on page loads by adding this to wp-config.php: define( 'DISABLE_WP_CRON', true ); Then have the server request wp-cron.php on a regular schedule, for example every 15 minutes: */15 * * * * curl -fsS https://example.com/wp-cron.php > /dev/null WP-Cron then runs the plugin's check at the Frequency to check you chose, and WordPress's own update tasks too. Fire the check yourself The plugin's check can also be started from code with the sc_wpun_run_check action. For example, with WP-CLI: */30 * * * * cd /path/to/site && wp eval "do_action( 'sc_wpun_run_check' );" This runs the same check as the schedule, and anything already reported is not sent again. It does not move the WP-Cron schedule, so Next check on the General tab does not change. If you rely on this alone, the time of your cron entry is the schedule. Things to know: The plugin does not lock checks against each other. If this overlaps another run, the same update can be sent twice. This is a known trade-off, and rare. See How notifications work. A check started this way is not a WP-Cron run, so WordPress lets plugin and theme data get up to 12 hours old before it refreshes it. A check started by wp-cron.php allows 2 hours. See Why is the update data hours old?.
On every check the plugin asks WordPress to refresh what it knows about updates. WordPress asks api.wordpress.org, but it does not do so every time. It skips the request when it has asked recently: The schedule, or wp-cron.php - Core updates: 1 minute; Plugins and themes: 2 hours Check for updates and notify now, or wp eval - Core updates: 1 minute; Plugins and themes: 12 hours So a scheduled check can see plugin and theme data up to two hours old, and a manual check up to twelve. WordPress also asks again early if the plugins or themes you have installed, or their versions, have changed. To get current data before a manual check, open Dashboard → Updates in WordPress first. That page refreshes the data if it is more than a minute old. Note: These limits belong to WordPress, not to this plugin. They keep your site from calling api.wordpress.org too often.
Send test on the Channels tab says "Test message sent" when WordPress has handed the email to your mail system. That does not mean the message was delivered. Check the spam folder first, then look at how your site sends mail. The From address. With From address empty, the email uses the WordPress default, which is wordpress@ followed by your site's domain. If you set one, it must be at a domain your server is allowed to send mail for. Mail that claims to come from a domain the server has no permission for is often rejected or sent to spam. SPF, DKIM and DMARC. These DNS records tell mail providers which servers may send for your domain. If your domain publishes a strict DMARC policy and the From address does not line up with the server that sends, providers can reject the message. Ask your host or mail provider for the right records. The server's mail. Many hosts block or throttle the basic mail function WordPress uses. Install an SMTP plugin, or a plugin for a mail service, so WordPress sends through an authenticated mail server. Then send a test again. Upgraded from 1.x? Versions before 2.0.0 sent from the administration email address unless you set another. If your From address was that same address, the upgrade cleared it, so mail goes from the WordPress default. Set From address if your mail setup needs one. If WordPress itself fails to send, the reason appears in the notice after the test and under Last delivery.
The address in a message is your site's home address, the Site Address (URL) in Settings → General. The link to the Dashboard → Updates screen is built from the WordPress Address (URL). Both can be wrong if wp-config.php sets WP_HOME or WP_SITEURL from the request, for example from $_SERVER['HTTP_HOST']. The check then runs in a request from a system cron or a visitor, and the address follows whichever host that request used. Set WP_HOME and WP_SITEURL to fixed addresses, or remove them and use the settings in Settings → General.
WP Updates Notifier 2.0.0 does not send Slack notifications, and your Slack settings are kept. If a Slack channel was switched on, the plugin tells you once by email, shows a notice on its settings page that you can dismiss, and adds an item to Tools → Site Health. The notice and the item stay while a Slack channel is switched on.
Each channel is told about each new version once. If you don't install it, nothing more is sent unless you switch on daily or weekly reminders for that channel. See How notifications work.
Not yet. Version 2.0.0 supports single sites only.

Sign In / Register

You need to sign in or register to use this feature.