Bedrock Disallow Indexing Laravel Package

Product Decisions This Supports

• Environment governance: standardizes a rule that non-production WordPress environments must not be indexed by search engines.
• Launch/readiness checklist: adds a concrete acceptance criterion for staging, preprod, and preview environments before they are shared with clients, QA, or partners.
• SEO and brand risk mitigation: reduces the chance that staging content, duplicate pages, unfinished copy, or customer-visible data appears in search results.
• Build vs. buy: favors adopting a small MIT-licensed Composer package over writing and maintaining custom robots.txt / X-Robots-Tag logic.
• Roadmap support: useful for teams standardizing Roots Bedrock WordPress sites and wanting a repeatable baseline across projects.
• Incident blast-radius reduction: complements access controls by adding a crawler-level guard if a non-production site becomes publicly reachable.

When to Consider This Package

Adopt it when:

• You run WordPress on Roots Bedrock and manage dependencies with Composer.
• You have multiple environments and non-production sites may be reachable by crawlers.
• SEO, brand, or confidentiality risk from indexed staging content is material.
• You want a minimal, standardized noindex safeguard rather than bespoke code.
• You can verify behavior in each environment and include it in launch checks.

Look elsewhere when:

• You are not on WordPress/Bedrock or do not use Composer.
• You need real access control such as SSO, VPN, IP allowlisting, or password protection. This package is not a security boundary.
• You need enterprise-grade crawler policy management, edge/proxy enforcement, or per-environment SEO controls beyond noindex.
• You have low tolerance for small, niche community packages and prefer platform-level configuration.
• You need guaranteed long-term vendor support; assess maintenance and fallback ownership first.

How to Pitch It (Stakeholders)

For executives: This is a low-cost safeguard that helps prevent staging and preproduction sites from appearing in search results. It reduces SEO, brand, and confidentiality incident risk with a small MIT-licensed dependency, and it is quick to add to Bedrock WordPress sites.

For engineering: Add it as a Composer dependency for Bedrock environments and verify that non-production responses include noindex behavior. It avoids custom crawler-blocking code, but it must be paired with SSO, VPN, IP restrictions, or other access controls because it is not a security control.

For product: Treat it as a launch-checklist and environment-governance item, not a customer-facing feature. Measure adoption through environment audits and search-console spot checks; avoid building custom logic unless platform constraints require it.