Nick Hamze’s Featured Plugins experiment has shaken up how WordPress users discover and install plugins. In just two weeks, the initiative delivered more than 26,000 new installs, marking a staggering 622% increase compared to the prior period.
Launched on February 28, Hamze’s experiment replaced the long-static list of plugins featured in the WordPress admin’s Add Plugin screen with a dynamic rotation of newer plugins. The goal was clear: surface less-established plugins that might otherwise be buried under popular incumbents. Early results suggest the strategy is working.
Data from Hamze’s blog highlights the significant impact of the change. Eight plugins were included in the initial cohort, collectively driving tens of thousands of installs. For comparison, the previous static list struggled to generate this level of engagement over a much longer timeframe.
Why the Featured Plugin Experiment Matters
The WordPress plugin ecosystem has long grappled with discoverability challenges. With over 60,000 plugins available on the [WordPress](https://wordpress.org) repository, newer or niche plugins often fail to gain traction. This experiment directly addresses that issue, offering visibility to plugins that might otherwise languish in obscurity.

Hamze’s approach could signal a shift in how plugin promotion is handled within WordPress core. By rotating featured plugins, the program creates opportunities for lesser-known developers to compete on a more level playing field. The 622% increase in installs underscores the latent demand for fresh solutions when users are presented with them effectively.
What Practitioners Should Know
For developers and agencies, the implications are significant. Plugin creators now have a pathway to reach new audiences through strategic inclusion in the featured list. However, competition for these slots will likely intensify as the program gains visibility.

Agencies managing client sites should monitor trends in plugin adoption stemming from this experiment. The rotating nature of the list means that newly featured plugins may introduce functionality options worth exploring, but also require vetting for stability and compatibility.
Hosting providers should also pay attention. A surge in installs for lesser-known plugins could impact server environments, particularly if certain plugins introduce resource-heavy functionality.
What To Do
- Plugin developers: Apply for inclusion in future cohorts of the Featured Plugin program. Ensure your plugin is well-documented and actively maintained to improve your chances.
- Agencies: Evaluate newly featured plugins for potential client use, but perform compatibility testing before deployment.
- Hosting professionals: Monitor performance metrics on sites adopting plugins from the Featured Plugin program, particularly those with high growth rates.