Staging for marketing sites: keep it simple

Keep staging private and publish only from production.

Staging environment illustration

Staging is where you practice. Production is where you publish.

The key is keeping it boring and predictable.

Two core rules

1. Password protect staging using Basic Auth

Use simple username/password credentials to keep staging private. The goal is not to secure sensitive data—it's to keep Google and random people out.

Basic auth screen asking for user/pass
Basic auth screen asking for user/pass

I recommend obvious username/password combinations that are easy to share with stakeholders without creating friction.

2. Prevent pushing staging content to production

Maintain a one-way flow: code flows through staging to production. Content does not.

Never push staging content to production to avoid overwriting live sites or triggering unwanted workflows.

Common problem users

I've identified two problematic user types:

  • "Anxious Andy" — Paralyzed by fear of breaking staging
  • "Burned-out Brianna" — Bypasses staging entirely due to friction

Both stem from overcomplicated staging systems.

Keep it simple

Maintain production as the single source of truth. For managed platforms like WP Engine or Vercel, use their built-in staging tools. Don't overthink it.

Want help with your site?

Let's see where you're at and what's possible.