Release control · 2026-08-05
Why the publication stays non-indexed before launch
A deployed preview is not the same as an approved public release. Indexing remains an explicit decision so unfinished claims, test content, and commercial paths do not quietly become the public record.
01 · What changed
The implementation move.
- 01Kept robots metadata set to noindex and nofollow at the root layout.
- 02Maintained a development-preview marker that rendered-route tests can verify.
- 03Separated preview deployment, editorial approval, affiliate configuration, analytics, newsletter operation, and public indexing into distinct decisions.
- 04Added project maturity and next-gate language so a preview cannot be mistaken for a released product.
02 · Evidence
What supports the current claim.
- The root metadata explicitly prevents indexing in the current review build.
- The repository documentation states that production DNS, public indexing, analytics, and newsletter submission are not enabled by the repository.
- The test suite verifies the development-preview metadata before checking substantive routes.
03 · What I learned
The reusable lesson.
04 · Security and control impact
How the authority or release boundary changed.
- Unapproved pages do not enter search by accident.
- Affiliate destinations remain centralized and independently reviewable.
- Public project records can expose useful lessons without exposing private implementation or claiming maturity that has not been earned.
Current limitationNoindex prevents organic discovery. It is a temporary release control, not a long-term marketing strategy.
Next decisionPass the exact project-hub validation, approve the sanitized preview, then make indexing a separate owner-controlled launch decision.
Related records