What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
WordPress can email the site’s Administration Email Address after plugin or theme automatic-update attempts. Those messages report success, failure, or mixed results; they are not advance alerts for every update that is waiting. To receive a daily list of pending core, plugin, and theme updates, you need a separate update-notification plugin or another monitoring service.
Set the address WordPress uses for update mail
- Sign in to WordPress with an administrator account.
- Open Settings > General.
- Find Administration Email Address and enter the inbox that should receive site-administration messages.
- Save the change and complete any confirmation WordPress requests.
This address is for site administration notifications, including site updates and maintenance. It is separate from the email address on an individual user’s profile, so changing a user account’s email does not necessarily change where site update messages go.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
WordPress Multisite Administration | $34.38 | Buy on Amazon |
| 2 |
|
Mon Site WordPress – Volume 2 – Administration & Utilisation (French Edition) | $9.90 | Buy on Amazon |
| 3 |
|
WordPress 24-Hour Trainer | $3.95 | Buy on Amazon |
| 4 |
|
Teacher Record Book | $4.89 | Buy on Amazon |
Understand what the built-in emails actually report
WordPress’s native plugin and theme auto-update emails are outcome notices. WordPress.org documentation says that, by default, owners receive email when plugins and themes are automatically updated, with messages covering successful, failed, or mixed results.
Recommended Free Tools
Automatic updates are enabled separately for each plugin or theme. When enabled, WordPress normally runs those updates twice per day. That is the update task’s default cadence, not a guarantee that an email will arrive at a particular hour or that every pending update will produce a message.
#1 Best Overall
What you can expect
- A message after an enabled background plugin or theme update is attempted.
- A success, failure, or mixed-result report for that attempt.
- Delivery to the Administration Email Address, subject to your host and mail provider.
What you will not get automatically
- A guaranteed warning as soon as any new core, plugin, or theme version is published.
- A pending-update inventory when no automatic-update attempt has occurred.
- A delivery guarantee if the site’s outgoing mail is blocked or filtered.
Choose between result emails and advance alerts
| Approach | Timing | Coverage | Configuration and trade-offs |
|---|---|---|---|
| Built-in WordPress emails | After a background plugin or theme automatic-update attempt | Results for those attempts: success, failure, or mixed outcome | Uses the Administration Email Address; no extra plugin, but it is not a pending-update alert |
| Pending-update notification plugin | When updates are detected, according to the plugin’s schedule | The “Site Update Notification” directory listing describes daily checks for WordPress core, plugins, and themes | Requires installation and ongoing compatibility, support, and security checks |
| SMTP or transactional email service | Does not choose events; it handles mail delivery | Can improve transport reliability for messages WordPress already generates | A delivery layer, not a replacement for selecting built-in or pending-update alerts |
Get advance notices with a pending-update plugin
The WordPress.org directory entry for Site Update Notification describes a plugin that checks daily for pending WordPress core, plugin, and theme updates and emails a list of updates that need installation. The listing retrieved on September 30, 2026, showed version 1.0, 60+ active installations, and no reviews. Those volatile figures do not establish quality or suitability.
Check before installing
- Confirm the listing’s current “Tested up to” WordPress version and the plugin’s last update date.
- Review support activity, changelog, security notices, and recent user feedback.
- Test it on a staging site when the production site is business-critical.
- Verify where it sends reports and whether it duplicates the Administration Email Address.
Install and configure it
- Create a current backup of the database and files.
- In the dashboard, open Plugins > Add New.
- Search for Site Update Notification, verify the author and listing details, then install and activate the intended plugin.
- Open the plugin’s settings page (its menu location and recipient fields can change between releases).
- Set the recipient address, save, and use any available test-email or manual-check control.
- Confirm that the report lists the updates you expect and that the message reaches the intended inbox.
Keep the native result emails enabled if you want both an advance list and a post-update outcome report; the two features answer different questions.
Make sure WordPress can deliver the messages
If the Administration Email Address is correct but nothing arrives, first check the site’s ability to send mail rather than changing update settings repeatedly. WordPress.org’s General Settings guidance suggests considering an SMTP plugin or a transactional email service when site email is unreliable. This can address transport and authentication problems, but it cannot guarantee delivery where the host, DNS records, recipient provider, or spam filtering is misconfigured.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Delivery checklist
- Recheck the address under Settings > General, including spelling and confirmation status.
- Look in spam, quarantine, and suppression lists at the recipient provider.
- Send a test message from another WordPress feature to determine whether all site mail is affected.
- Check hosting mail logs or ask the host whether outbound PHP mail is blocked.
- Configure an SMTP plugin or transactional service with authenticated credentials, then send a test and monitor its delivery log.
- Use a mailbox on the same domain and a personal mailbox when testing, because filtering can differ.
Troubleshoot updates that never run
An absent result email may mean that no background update was attempted. Plugin and theme auto-updates depend on WordPress Cron tasks.
Rank #3
- Open Tools > Site Health.
- Review the Status and Info screens for Cron errors, loopback problems, or background-update warnings.
- Open Plugins > Installed Plugins and verify that automatic updates are enabled for the plugins you intend to update. Theme controls are available under Appearance > Themes where supported.
- Check the hosting control panel or server configuration for a disabled or failing WordPress Cron trigger.
- Resolve the Cron or loopback issue, then allow the next scheduled run before judging whether notifications work.
Keep a current backup before enabling or applying updates. If an update causes a compatibility problem, the backup is your recovery path; an email notice does not prevent the underlying change.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Developer controls for custom notification behavior
Code-maintained sites can alter plugin and theme background-update messages with the auto_plugin_theme_update_email filter. It can change the recipient, subject, body, or headers. The auto_plugin_update_send_email filter controls whether WordPress sends a post-update email after background plugin updates.
Rank #4
- Keep track of everything from attendance to test scores
- Spiral bound
- Measures 8-1/2" x 11"
These are developer hooks, not dashboard switches. Put maintained customizations in a site-specific plugin or other managed codebase, document the intended behavior, and test after WordPress and plugin upgrades. Avoid an untracked snippet in a production theme: a theme replacement can remove it, and an incorrectly shaped filter callback can suppress or corrupt notifications.
Quick Recap
Use hooks only for a defined policy
- Route messages to an operations mailbox while leaving ordinary account mail unchanged.
- Add headers required by your organization’s mail gateway.
- Suppress duplicate plugin-result messages when another monitoring system is authoritative.
- Keep a tested fallback recipient so a code change does not silently eliminate all alerts.
A practical setup for most sites
- Set and verify the Administration Email Address.
- Enable automatic updates only for plugins and themes you are prepared to update in the background.
- Keep built-in result emails enabled so failures are reported.
- If you need advance warning, evaluate a maintained pending-update notification plugin and configure its recipient.
- Test outgoing mail and add SMTP or transactional delivery only when delivery is the problem.
- Review Site Health and Cron whenever scheduled updates or reports stop appearing.
- Maintain backups before update activity and test recovery periodically.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
