0052. Staging gets a noindex copy of the public site on a host of its own, with no redirect
- Status: Proposed. That the public site and its docs can be checked on staging is the maintainer’s decision of 2026-11-20, Accepted and not reopened. How the copy is hosted, below, is Proposed.
- Date: 2026-11-21
Context
Section titled “Context”- ADR 0042 gives the public site one environment, production. Staging got no copy because a second public copy of the legal pages and docs could be indexed and quoted as the real one, and because a build is previewed locally before a deploy.
- On 2026-11-20 the maintainer asked for a state that can be checked completely on staging, the site and the docs included. A local preview does not show the deployed Worker, its custom domain, its response headers, or the links between the site and the staging app.
- The staging hosts are under
dev.<domain>, in the same DNS zone as production’s. Production’swww.redirect is configured for the whole zone, and production owns that configuration. - Search engines drop a page from their results when it answers with
X-Robots-Tag: noindexor carries<meta name="robots" content="noindex">. Both work only if the crawler can fetch the page, sorobots.txtmust not disallow it.
Decision
Section titled “Decision”- Staging has a copy of the public site. It is the same build, with staging’s values, on a host of its own under
dev.<domain>, such assite.dev.<domain>. The host comes from configuration, never from code. The build refuses a staging build whose site or app host is not underdev., and a production build whose host is, so neither environment’s values end up in the other’s links. - The copy is never indexed. Every response has
X-Robots-Tag: noindex, and every page has a robotsnoindexmeta tag. Production’s build has neither. The build sets both from its environment, and each environment’s deploy command builds for the Worker it deploys to. - The copy has a Worker of its own and no redirect. It shares no Worker with production, and each Worker is deployed from its own build output, so neither can be given the other’s build. Staging adds no
www.host and no redirect, and never changes production’s redirect configuration. - This replaces ADR 0042’s “One environment” rule. The rest of ADR 0042 stands.
Consequences
Section titled “Consequences”- A change to the site or the docs can be deployed to staging and checked there before production.
- The legal pages exist at a second public URL. noindex keeps it out of search results, but it does not stop a reader who has the link from quoting it.
- Staging’s site has no
www.host. A redirect added later is still added to production’s ruleset only, and cannot be checked on staging first. - The copy is static like production’s, sets no cookies, and is open to anyone who knows its host.