Is Your Staging Website Private, or Just Marked noindex?

· 6 min read

Published by AKSIS · general educational information

How AKSIS handles editorial review

AKSIS publishes practical website and search guidance for small business owners. Our editorial policy covers source support, claim boundaries, clarity, human responsibility, and small-business usefulness.

General information only—not legal, financial, medical, or platform policy advice.

Read the AKSIS editorial policy.

A preview website marked noindex can still be open to anyone who has its address. Search exclusion and visitor access answer different questions. If a draft must be private, ask your developer how access is restricted, rather than accepting “it is hidden from Google” as proof.

A staging site is a separate place to review a website before launch. You might want only your team to open that preview, while everyone can open the finished site. Those two addresses need different acceptance checks. The fictional example below shows why a good preview result does not establish that the public site is ready.

First decide who should be able to open the page

Google distinguishes password protection from noindex: the former can restrict visitors, while the latter concerns whether content appears in search. An otherwise public page can still be opened directly or reached through a link. See Google’s guide to controlling what you share.

For a private draft, write an access requirement such as “only invited reviewers may view this preview.” Have the developer identify which hostnames, pages and linked files that restriction covers. A login on one page is not evidence that every alternate address or document has the same protection. This is a scope question, not a security certification.

Four controls that can look similar to an owner

A conceptual comparison, assuming each stated control works as intended.
SetupVisitor accessGoogle search boundary
Access-restricted previewLimited to authorized visitors within the protected scope.Do not infer a live indexing status from the access setting alone.
Public preview with noindexPeople can open the public address.Google must crawl it to see the exclusion rule.
Public page blocked in robots.txtCrawl rules do not restrict human access.A discovered URL may still appear without its content.
Public page omitted from a sitemapOmission does not restrict access.Links can still lead Google to the page.

Google documents noindex in page metadata or an HTTP response header. Blocking crawling can stop Google from seeing that rule; putting noindex in robots.txt is unsupported. Its robots.txt guide explains the crawl-versus-indexing distinction. A sitemap helps discovery; inclusion does not guarantee indexing, and omission is not an exclusion rule.

Worked launch decision: two addresses, two outcomes

Imagine a fictional local repair business replacing its website. Its preview is preview.example.com and its intended public site is www.example.com. These are illustrative addresses and assumed observations, not a performed test, customer incident or AKSIS result.

The owner’s requirements are: invited staff can review the draft; other visitors cannot view that draft; and the finished public pages can be opened and considered for Google indexing. The preview must remain private after launch because further draft work will happen there.

  1. Preview access looks correct. Assume an invited reviewer can sign in, while a separate signed-out visit cannot open the protected draft. The developer also accounts for the draft’s linked documents and alternate preview address. This supports the stated preview requirement for those checked resources. It says nothing about production: that is another host.
  2. Production opens, but the launch is not ready. Assume the public homepage and service page open without a login, but the developer finds a noindex response header on both. Removing a visible page-level tag would leave that header untouched. The owner should hold this launch decision and ask for the production exclusion to be corrected, with fresh evidence for the actual public pages. Removing the preview restriction would solve the wrong problem.
  3. The two requirements can be accepted separately. Now assume fresh checks show the intended public pages open without a login, have no unintended indexing exclusion in their page or response, and are not unintentionally crawl-blocked. Their canonical addresses and sitemap use the public host. A separate check still finds the preview restricted to reviewers. Those observations support this bounded launch decision; they do not establish that Google has crawled, indexed or ranked the public pages.

The useful handoff is therefore two short records, each naming its exact address, intended audience, checked resources, observation and date. A screenshot of the preview or a generic “SEO enabled” setting cannot stand in for production evidence. Ask for the unresolved item and the next check whenever a result is unknown.

If an unfinished page is already in search

Start by identifying the exact address and whether it must be private or simply excluded from search. Do not assume adding a crawl block will let Google read a new noindex instruction. Nor should anyone promise an immediate search change after a setting is updated. Have the developer choose and verify the appropriate correction for that address while preserving the intended public site.

For the opposite problem—a finished public page missing from Google—use our website visibility troubleshooting guide. It covers the wider discovery checks after launch. This preview decision is one part of a release, not a replacement for reviewing the site’s content, accessibility or working contact path.

Bring the preview requirement into the website brief

Name the reviewers, the exact preview and public addresses, what should remain restricted, and who will confirm each launch result. Add those requirements to your website brief before the handoff.

If you are planning an AKSIS Managed Website design or rebuild, discuss that handoff with us. Website care is included for an AKSIS-built Managed Website; the preview, launch and ongoing responsibilities should be clear in your project scope.