SiteGuard Pro: Staging Site Protection | LionScripts

The most common WordPress SEO disaster is a staging site getting accidentally indexed. Google then ranks the staging version, you spend a week figuring out what happened, and even longer cleaning it up. SiteGuard Pro prevents this in one click. It's free.

What it does

Adds X-Robots-Tag: noindex, nofollow at the HTTP-header level.
Adds <meta name="robots" content="noindex, nofollow"> at the HTML level.
Adds Disallow: / to the robots.txt.
All three together, so you're protected even if one is overridden by a theme or plugin.

Why all three layers matter

Search engines respect different signals. The HTTP header is the strongest. The meta tag covers cases where pages are scraped by less-strict bots. The robots.txt is a courtesy that good bots respect. Belt-and-suspenders is the right approach because the cost of getting indexed by accident is high and the cost of triple protection is zero.

Setup walkthrough

1. Install on staging

Upload to your staging WordPress, activate. The plugin defaults to "off" — you have to explicitly enable protection.

2. Toggle protection ON

One toggle in the settings panel. Verify it's enabled by curling the staging URL — you should see x-robots-tag: noindex, nofollow in the response headers.

3. Set up a reminder for when you push to production

The most common failure mode is forgetting to disable SiteGuard when staging becomes production. Add a deployment checklist item: "verify SiteGuard Pro is disabled on prod."

When else to use it

Beta launch period. When you want to soft-launch without ranking yet.
Site rebuilds. Old structure being replaced; you don't want the temporary state ranked.
Internal-only sites. Knowledge bases, intranets, etc.

Don't use it for production

Obvious but worth saying — SiteGuard Pro is for sites that shouldn't rank. If you accidentally enable it on production, you're invisible in Google. Always verify after enabling.