by Tony Zeoli 0 (0 reviews)

Greenskeeper

Name: Greenskeeper
Author: Tony Zeoli

Manage WordPress updates, filter comment spam, send branded email reports, and configure SMTP delivery — for single sites and Multisite networks.

Greenskeeper ranks #55,447 among WordPress.org plugins with 0+ active installations, is #1,985 of 3,341 in the Communication category, and was last updated Sep 3, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 7.0.4 (Current: 7.1)

v2.4.1 Current Version v2.4.1

Updated 1 week ago Last Update on 03 Sep, 2026

Refreshed 7 hours ago Last Refreshed on

#1,985 of 3,341 in Communication Downloads -83.5% this week

View on WordPress.org

Rank

#55,447

— No change

Active Installs

— No change

KW Avg Position

N/A

— No change

Downloads

1.7K

+2 today

Support Resolved

— No change

Rating

Review 0 out of 5

0 (0 reviews)

Next Milestone 10

Total Progress 30%

0+ 10+

23,023

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 7 more installs to reach 10+

Rank Changes

Current #55,447

Change

Best #

Upgrade to Pro

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

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

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

Upgrade Now

Reviews & Ratings

0.0

0 reviews

Overall 0%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 2.4.1
Last Updated: Sep 03, 2026
Requires WP: 5.8+
Tested Up To: 7.0.4
PHP Version: 8.0 or higher
Author: Tony Zeoli

Support & Rating

Rating: ☆ ☆ ☆ ☆ ☆ 0
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

email maintenance multisite smtp updates

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,752

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

WP Mail SMTP by WPForms - The Most Popular SMTP and Email Log Plugin

4M+ installs

#12

MC4WP: Mailchimp for WordPress

1M+ installs

#34

Hostinger Reach – AI-Powered Email Marketing for WordPress

1M+ installs

#44

Popup Builder & Popup Maker for WordPress – OptinMonster Email Marketing and Lead Generation

Joinchat – Enhanced "click to chat"

700K+ installs

#88

Click to Chat – HoliThemes

600K+ installs

#92

View all Communication plugins

Frequently Asked Questions

Common questions about Greenskeeper

Yes, from version 1.9.1. Greenskeeper hooks into WordPress's upgrader_process_complete action, which fires for any update that runs through WordPress's standard Plugin_Upgrader or Theme_Upgrader — including updates made from the WordPress Updates screen, the Avada plugins dashboard (for Avada Core and Avada Builder), or any other standard WordPress update mechanism. These external updates are logged automatically with a session labelled "External" in the Update Log, and are included as a separate "Updates Made Outside Greenskeeper" section in the next maintenance report email.

Greenskeeper handles Avada-related updates in two ways depending on the update type: Avada theme, Avada Core, and Avada Builder updates — once your Avada license is registered, these appear in the standard WordPress updates list and can be updated from either the WordPress Updates screen or the Avada plugins dashboard. Both routes fire WordPress's standard upgrade hooks. Greenskeeper detects and logs these automatically and includes them in the maintenance report email. Avada Patches — patches applied through Avada's own Maintenance → Plugins & Add-Ons dashboard use Avada's proprietary update mechanism and

automatically. They should be documented manually using the Additional Manual Updates field on the Email Reports page before sending the report. The Updates page also shows a contextual notice when the Avada theme is installed, explaining the required update order: Avada theme first, then Avada Core, then Avada Builder.

An external update is one that Greenskeeper detected automatically because it went through WordPress's standard update mechanism (Plugin_Upgrader or Theme_Upgrader). These are logged and included in the email without any action from you. A manual update is one that Greenskeeper cannot detect — for example an Avada Patch, a plugin updated through a vendor's own proprietary dashboard, or an FTP file replacement. These must be documented using the Additional Manual Updates field on the Email Reports page.

Yes, with important notes. Avada Core and Avada Builder appear in the standard WordPress plugin update list once your Avada license is registered, and the plugin

installed, explaining the required update order: Avada theme first, then Avada Core, then Avada Builder. A confirmation prompt appears if you select the Avada theme for update, reminding you to follow up with the companion plugins. Avada Patches are managed separately through Avada's own dashboard (Avada → Maintenance → Plugins & Add-Ons) and do not appear in the standard WordPress update API, so they cannot be detected or applied from this plugin. The Updates page includes a direct link to that dashboard so you can check after completing your regular updates.

Yes. It can be network-activated by a Super Admin to cover all sites simultaneously, or activated per-site by individual Administrators. Each site maintains its own isolated database tables, update log, and email log. The plugin handles cross-site AJAX correctly on Multisite so email sending always reads from the correct sub-site's log table.

If you upgraded the plugin by uploading new files without deactivating first, the database schema may not have been upgraded. Open Update Log, expand the Database Diagnostic panel at the bottom, and click Force DB Upgrade Now. The panel shows both database tables with their column lists highlighted in green (present) or red (missing). After the upgrade click Refresh — all sessions should appear.

By default WordPress sends email via PHP's mail() function, which many hosting providers block or which major inboxes mark as spam. Go to Settings → SMTP & Email Delivery and configure a dedicated SMTP provider. Use Send Test Email to verify your connection before sending a real report. See the SMTP Setup Guides section below for step-by-step instructions for each supported provider.

Premium and licensed plugins that require a valid license key for automatic updates will fail with a mapped error message. The Update Log and email reports both include a plain-English explanation and an action recommendation. These items must be updated manually through the vendor's dashboard or by providing a valid license key.