Plugin Check (PCP)
Plugin Check is a tool for testing whether your plugin meets the required standards for the WordPress.org plugin directory. With this plugin you will be able to run most of the checks used for new submissions, and check if your plugin meets the requirements. Additionally, the tool flags violations or concerns around plugin development best practices, from basic requirements like correct usage of internationalization functions to accessibility, performance, and security best practices. The checks can be run either using the WP Admin user interface or WP-CLI: To check a plugin using WP Admin, please navigate to the Tools > Plugin Check menu. You need to be able to manage plugins on your site in order to access that screen. To check a plugin using WP-CLI, please use the wp plugin check command. For example, to check the “Hello Dolly” plugin: wp plugin check hello.php Note that by default when using WP-CLI, only static checks can be executed. In order to also include runtime checks, a workaround is currently necessary using the --require argument of WP-CLI, to manually load the cli.php file within the plugin checker directory before WordPress is loaded. For example: wp plugin check hello.php --require=./wp-content/plugins/plugin-check/cli.php You could use arbitrary path or URL to check a plugin. For example, to check a plugin from a URL: wp plugin check https://example.com/plugin.zip or to check a plugin from a path: wp plugin check /path/to/plugin The checks are grouped into several categories, so that you can customize which kinds of checks you would like to run on a plugin. Keep in mind that this plugin is not a replacement for the manual review process, but it will help you speed up the process of getting your plugin approved for the WordPress.org plugin repository, and it will also help you avoid some common mistakes. Even if you do not intend to host your plugin in the WordPress.org directory, you are encouraged to use Plugin Check so that your plugin follows the base requirements and best practices for WordPress plugins. Plugin Namer Tool Plugin Check now includes an AI-powered Plugin Namer tool (accessible via Tools > Plugin Check Namer) that helps plugin authors evaluate plugin names before submission. This tool checks for: Similarity to existing plugins in the WordPress.org directory Potential trademark conflicts with well-known brands Compliance with WordPress plugin naming guidelines Generic or overly broad naming issues The Plugin Namer provides instant feedback with actionable suggestions, helping you choose a clear, unique, and policy-compliant name that stands out in the plugin directory. This feature requires WordPress 7.0+ and configured AI connectors. Important: The Plugin Namer tool provides guidance only and is not definitive. All plugin name decisions are subject to final review and approval by the WordPress.org Plugins team reviewers. SVN Checker Tool Plugin Check also includes an SVN Checker tool (accessible via Tools > Plugin Check SVN) that scans a plugin’s WordPress.org SVN repository for unexpected files, folders, and zip archives. This helps plugin authors and reviewers ensure that only the intended files are present in the plugin’s trunk, tags, and assets directories before or after a release. Checks reviewed by AI When AI analysis is enabled, Plugin Check can review selected results to help identify likely false positives. Related issues are grouped and analyzed with prompts tailored to the type of check, using the surrounding code as context. The AI review does not remove or change the original results, but adds an additional summary that highlights which findings may need human review before taking action.
Staatic – Static Site Generator for WordPress
Staatic turns WordPress into a practical static site generator. Keep editing posts, pages, menus, media, and settings in WordPress, then publish a static copy made of HTML, images, CSS, JavaScript, and other assets. The public site can be served without WordPress, PHP, or a database in the visitor request path. That can improve performance, reduce origin load, and shrink the public attack surface while preserving the familiar WordPress editing workflow. This is especially useful for a private-origin, public-static setup: WordPress remains available for editors and publication work, while visitors receive prebuilt files from your chosen hosting target. Staatic includes the publication workflow and deployment methods needed to run a self-hosted static WordPress site. Features of Staatic include: Crawls your WordPress site and builds a static publication from the pages and assets it discovers. Publishes from WordPress Admin, with publication status, logs, resource details, and downloadable output. Deploys to Local Directory, Amazon S3 or S3-compatible storage, GitHub, Netlify, SFTP, or a zip archive. Supports redirects, custom 404 pages, additional URLs and paths, exclude rules, and HTTP headers. Includes a WP-CLI command for command-line publication workflows. Works with WordPress Multisite, WPML, and HTTP Basic Auth protected WordPress origins. Helps separate the public site from WordPress admin, plugin runtime, and database-backed page generation. Provides integration hooks and compatibility improvements for common WordPress setups. Staatic Premium and Staatic Cloud add features such as forms integration, search integration, scheduled publications, change-based publications, and managed static WordPress hosting. The Community edition remains suitable when you want to generate and deploy a static version of a WordPress site yourself. Staatic Premium Staatic Premium supports ongoing development and adds functionality for teams that need more than the Community edition. Premium features include forms integration, search integration, scheduled publications, change-based publications, additional automation, and Staatic Cloud deployment options. For more information, visit Staatic.
