Get your plugin listed

The three things that matter

1. Tag the repository with the GitHub topic wordpress-plugin. That is the primary hunt query and the fastest way in.
2. Keep the main plugin file at the repository root with a standard header (Plugin Name:, Description:, Version:, Author:). The confirm step reads only root-level PHP files.
3. Publish GitHub Releases with a zip asset attached. Source tarballs do not count downloads and their folder names break installs. A release named 1.4.0 carrying your-plugin.zip gives you download counts, an active-site estimate, and a working one-line install command on your listing.

Nice to have

• A README.md whose first paragraphs say what the plugin does. The classifier reads them.
• Requires at least, Requires PHP and License headers.
• An Update URI: header, so WordPress knows updates come from you and never from a same-named directory plugin.

Self-hosting updates

The pattern most listed plugins use: a manifest.json in the repository, a small updater class that feeds site_transient_update_plugins, and a release zip whose URL the manifest points at. Here is a walkthrough. Git Updater and Plugin Update Checker are the two common libraries.

Already tagged and still missing?

The crawl runs on a schedule and new repositories are confirmed in star order, so a brand new repo can take a while to appear. If yours is still missing, or something about your listing is wrong, email feedback@wpmanifest.xyz with the repository URL and it gets queued by hand.

Something wrong with a listing?

Same address: feedback@wpmanifest.xyz. The things most worth reporting:

• Your plugin is listed but you would rather it was not. Say so and it comes down.
• It is filed under the wrong category, or the description reads badly.
• It is marked as a mirror or a documentation repo and it is neither. That call is made automatically and it does get things wrong.
• Someone else has republished your plugin under their own account. That listing should not be here.