Site Visibility

Site visibility controls who can read a published site. It does not publish or unpublish the site by itself. Find it in Site Settings → Visibility.

Public

Anyone can open a public site without signing in.

• Pages can appear in the site's XML sitemap.
• Search engines are allowed to index accessible pages.
• Published search, document libraries, file previews, and exports are available to visitors when those features are present on the page.
• A verified custom domain serves the same public content as the generated BaseBlocks address.

Use Public for documentation, knowledge bases, and other information intended for the open web.

Private

Private sites require a signed-in BaseBlocks account that belongs to the site's team.

• Anonymous visitors receive a generic access screen, never the site content.
• Signed-in users outside the team are denied.
• Private pages are omitted from XML sitemaps and marked noindex, nofollow.
• Page content, navigation, search results, libraries, files, and document exports are checked independently at the server boundary.
• Switching from Public to Private takes effect on new requests immediately.

The authenticated private-site address is:

https://your-team.baseblocks.dev/[site-slug]

Private access currently uses this BaseBlocks address because the BaseBlocks session cookie can be verified securely across BaseBlocks subdomains. If a private site also has a custom domain, that domain directs team members to the authenticated BaseBlocks address.

Use Private for internal documentation or sensitive information that must stay inside the team.

Changing visibility

Choose Public or Private in Site Settings → Visibility. The access change is applied independently of the draft/published status.

For the strictest shutdown, choose Private and then Unpublish. Unpublishing removes the entire published surface while keeping the editor content.