Protected staging
Protected staging keeps your review site private. Only people signed in to Echo who are members of your workspace can open it. Set it up in Website → Versions → Staging.
Switch it on
- Enter the review site's address: the staging build, for example client.pages.dev. It must differ from the live site.
- Switch on Protected staging.
Anyone else who opens the staging address is sent to Echo's sign-in first, then straight back to the page they asked for. A session lasts 12 hours. Someone removed from the workspace loses access within a minute.
Add the gate
The review site checks with Echo through a small gate from the Allsite CMS. The site's developer, or their AI tool, adds it once. Copy setup for AI in Echo gives the exact instructions.
- Cloudflare Pages: add a file
functions/_middleware.jscontainingexport { onRequest } from '@allsite/cms/gate';. - Cloudflare Workers with static assets: in the staging Wrangler config, set
main = "node_modules/@allsite/cms/src/gate.mjs", and give the assetsbinding = "ASSETS"andrun_worker_first = true.
Echo shows Protected once the gate works, otherwise Not protected yet.
Good to know
- Protected pages are marked noindex, so search engines leave them out.
- Use it only on staging, never on the live site.
- If Echo can't be reached, the review site asks visitors to reload in a minute rather than opening.
See Versions for what each publish changed, and Edit your website for connecting the site.
Something wrong or out of date? Write to hello@echo-aeo.com and we'll fix it.