Angry Launch Guard

Description

«Before you hand over the site, check everything.»

Every agency has launched a site that still said «Discourage search engines», ran in WooCommerce «coming soon» mode, sent order emails from wordpress@, or left a public debug.log behind. Angry Launch Guard runs 41 launch checks in one go and gives you a clear verdict:

  • READY: no errors, no warnings
  • WARNING: nothing blocking, but worth a look
  • NOT READY: fix the errors first

Each check shows its status, a one-line explanation, and either a Fix button (only where it is safe), clear How to fix instructions, or a link to the right WordPress screen.

What it checks

  • Visibility & SEO: search engine visibility, a blocking robots.txt, plain permalinks, site icon, default tagline, sample content («Hello world!», «Sample Page», the default comment), privacy policy page, and leftover development/staging domains (site URLs, menus, content, Elementor layouts, widgets, theme settings).
  • Security: «admin» username, administrators still using agency email addresses, debug mode and displayed errors, the file editor, a public debug.log, XML-RPC, public user listing through the REST API.
  • Configuration: HTTPS site address, basic mixed content, timezone, administration email, site language, comments.
  • Content & maintenance: inactive plugins and themes, pending updates, missed scheduled posts, trash, post revisions.
  • Server: PHP version, memory limit, upload limit, max execution time, WP-Cron, SSL certificate expiry, persistent object cache.
  • Email: send a test email and see if it was accepted; detect a custom mailer/SMTP setup.
  • WooCommerce (only when active): coming soon mode, store pages, payment gateways left in test/sandbox mode, store address and currency, the «From» address of store emails.

Built for handover

  • Ignore (intentional): mark a check as intentional with a note; it is greyed out and doesn’t affect the verdict.
  • Fix log: every one-click fix is recorded with time, user and the exact change.
  • Copy as Markdown: the full report (verdict, every check, ignored items with notes, fix log) ready to paste into a handover email or ticket.
  • Print view: a clean printable report.
  • Agency settings: your agency’s email domains and development domains, so the checks can spot what still points to you.
  • Optional dashboard widget with the last verdict.

Safe by design

  • Nothing changes unless you press a Fix button, and every fix first shows exactly what it will change.
  • No file is ever edited (wp-config.php, .htaccess). The only file it can delete is wp-content/debug.log, after confirmation.
  • Two optional hardening settings (disable XML-RPC, hide the users REST endpoint from visitors) are off by default and removed when you deactivate the plugin.
  • This plugin makes requests only to your own site. No tracking, no external services.

Screenshots

Installation

  1. Install and activate the plugin.
  2. Go to Tools Launch Guard.
  3. Optional: add your agency email domains and development domains in the Settings tab.
  4. Press Run audit.

FAQ

Does this replace Site Health?

No. Site Health checks whether WordPress runs well on the server. Launch Guard checks whether a site is ready to hand over to a client: search visibility, sample content, staging leftovers, agency addresses, WooCommerce test modes and so on. Where the two overlap (PHP version, HTTPS) Launch Guard keeps it short and links to Site Health.

Does it change my site?

Only when you click a Fix button and confirm. Running the audit is read-only. The fixes are listed in the Fix log tab and in the Markdown report.

What is the «Angry Hub» menu?

A small page that lists the Angry Parrot plugins installed on your site, with a link to each one’s settings, plus our other plugins. It is built into the plugin (no remote requests) and is shared: with several Angry Parrot plugins installed you still get one menu.

Does it send data anywhere?

No. The plugin makes requests only to your own site: a few «loopback» requests (for example, to see what a logged-out visitor sees at /wp-json/wp/v2/users) and a TLS handshake with your own domain to read the SSL certificate’s expiry date. Update information comes from WordPress’ own cached update check. The test email is sent only when you press «Send test email», to the address you enter.

Some checks say «Could not check».

Those checks need the site to load its own pages. Some hosts block these loopback requests. The rest of the audit still runs; Site Health also reports loopback problems.

The payment gateway check missed my gateway’s test mode.

It looks for the common «testmode» and «sandbox» settings. Some gateways use other names, so always double-check each gateway before launch.

Can I add my own checks?

Yes. Use the angry_lg_checks filter to add objects implementing AngryParrot\LaunchGuard\Check (or remove built-in ones).

Reviews

There are no reviews for this plugin.

Contributors & Developers

“Angry Launch Guard” is open source software. The following people have contributed to this plugin.

Contributors

Translate “Angry Launch Guard” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

1.0.0

  • First release.