WordPress plugin intelligence profile

Staging Bot Block

Prevent search engines from indexing staging sites by blocking or redirecting bots, with a clear admin warning banner.

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 6.9
Current version1.0.1
WordPress coverageTested up to WordPress 6.9
Minimum stackWP 4.6 · PHP 7.2
Directory statusactive
Last directory update13 Dec 202510mo ago
Active installationsNewAdoption metric — not a quality score
WordPress.org ratingNo WordPress.org ratings yet
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records Staging Bot Block version 1.0.1 as active, updated 10mo ago and tested up to WordPress 6.9.

Overview

About this plugin

Staging sites often get accidentally indexed by Google or Bing, leading to duplicate content, keyword cannibalization, and production pages being outranked by staging domains. This plugin prevents that from happening.

Staging Bot Block can:

* Block search engine bots with a 403 response and proper X-Robots-Tag headers.

* Redirect bots (or bots and users) to your production domain when needed.

* Display a persistent warning banner inside the WordPress admin so developers never forget that staging protections are active.

* Support additional user agents through an easy settings field.

Important Notes for Staging Environments

If your hosting platform or CDN uses full-page caching (such as Cloudflare APO, WP Rocket’s page cache, or server-level varnish), cached HTML may be served directly without loading WordPress. When this happens, Staging Bot Block cannot inspect user agents, block bots, or send redirect headers.

To ensure correct behavior:

* Disable Cloudflare APO or create a Cache Rule to bypass cache for the staging subdomain or for Googlebot/Bingbot.

* Clear or disable caching plugins on staging.

* Avoid server-level caching for staging domains.

Once caching is disabled or bypassed, all HTML pages will properly return a 403 for blocked bots or a redirect when configured.

WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • bot block
  • redirects
  • robots
  • seo
  • staging
Compatibility & maintenance

Compatibility & maintenance

Tested up to WordPress 6.9

Not yet marked as tested with WordPress 7.1. WordPress.org currently lists Tested up to 6.9.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to6.9
Minimum requirementsWordPress 4.6 · PHP 7.2
Update activity13 Dec 202510mo ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

No tracked version or compatibility changes have been recorded by WP PlugIndex yet.

Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.