OutscoreAgent Publisher is officially on WordPress.org

Today we crossed a line that matters more than it might look. The OutscoreAgent Publisher plugin passed the WordPress.org plugin review and is now in the official WordPress.org plugin directory. If you have used the plugin before, the change for you is small but real: the zip upload step is gone. If you haven't, this is the cleanest possible way in.

What changed for you

Before today, getting the OutscoreAgent Publisher onto your site meant downloading a zip from our site, opening WordPress admin, clicking Plugins → Add New → Upload Plugin, picking the file, waiting for the upload, then clicking Activate. It worked. It also looked like exactly the kind of step that makes a careful site owner pause and ask whether the code is safe.

From today, the flow is:

1. Open your WordPress admin.
2. Plugins → Add New.
3. Search "OutscoreAgent."
4. Click Install Now → Activate.

That's it. No download, no upload, no zip file sitting in your downloads folder. The plugin is hosted by WordPress.org itself, signed by the directory, and updates flow through the same auto-update channel you already trust for every other plugin on your site.

Why this matters more than "convenience"

The WordPress.org directory is one of the very few trust marks that buyers recognize without having to think about it. Stripe for payments. Google for sign-in. WordPress.org for plugins. Getting in is not automatic. The plugin team reviews every submission: code quality, security boilerplate (nonces, capability checks, sanitization), licensing, naming, conflicts with other plugins, behavior on a clean install. A lot of plugins try, not all get through.

For a small SaaS publishing into a category full of "AI SEO" tools, official directory presence does three things at once. It is a third-party audit you can point at when a customer asks "is this safe to install on our production WordPress site?" It is a permanent backlink from one of the highest-authority domains on the web. And it is the cleanest possible install path, which means fewer customers stalling out between sign-up and first published article.

The .zip is not going away

If you are on a managed host that blocks plugin directory installs, or you want to review the code before installing on a production site, the manual zip is still available. From your integrations page the .zip link is now labeled "advanced" and lives below the primary "Install from WordPress.org" button. Same plugin, same version. Just two install paths now instead of one.

Updates work the way you'd expect

Because the plugin is now in the official directory, version updates flow through the standard WordPress update channel. When we ship a new version, your WordPress admin will tell you about it on its next check, alongside whatever theme and core updates you already have queued. No more "is my plugin out of date" question, no more manual re-downloads.

If you have auto-updates enabled in WordPress admin, the plugin will update itself. We will continue to keep the changelog readable so you know what each release ships.

What's next

This release does not change the plugin's behavior. It still publishes articles from OutscoreAgent into WordPress as Gutenberg blocks, sideloads featured images, renders Pexels and Unsplash attribution, hosts your IndexNow key file, and fires lifecycle webhooks back to OutscoreAgent so the dashboard knows when publication succeeds or fails.

What it does change is the floor of the trust conversation. If you have been on the fence about wiring OutscoreAgent to your production WordPress site, the answer to "what code am I installing" is now: code that the WordPress plugin team reviewed and signed off on.

Head over to /wordpress-plugin for the install walkthrough, or just open your WP admin and search "OutscoreAgent" right now. The whole installation, including pasting your API token, takes under two minutes.

Thank you to everyone who installed the zip version in the early months. Your bug reports made the directory submission ready — literally. The reviewers asked clarifying questions about edge cases that real users had already surfaced.