Publish a Password-Protected Website with Revdoku

Publish a Password-Protected Website with Revdoku

By Updated
Table of Contents

TL;DR: Claude builds and publishes a small Revdoku website, protects it with a password, then adds email collection so the owner can see who visited.

Watch the video or follow the screenshot walkthrough.

What this gated website tutorial shows

  • Asking Claude to build and publish a website with Revdoku.
  • Opening the generated site.
  • Republishing the site with a password.
  • Confirming that the password gate blocks access before the site loads.
  • Switching to Require Email access.
  • Checking visitor information after visitors access the site.

1. Ask Claude to build a website

Start with a clear website prompt. Here, Claude builds a San Francisco weather dashboard with dynamic data storage.

Include the site goal, data sources or file names, and publishing requirement so the agent creates a hosted Revdoku site.

Claude prompt for the weather website

2. Let the agent prepare files and data

Claude creates the website files and supporting data before publishing to Revdoku.

Agent prepares website files and data

3. Open the first live Revdoku preview

After publishing, open the Revdoku URL and confirm the site renders before adding protected access. Here, the weather dashboard loads as a public page first.

Live weather site preview

4. Check the site before the protected update is ready

If the site is unpublished or a protected update is still running, the URL may show a “not available” message. Wait for Revdoku to finish publishing before testing access.

Site not available before publishing completes

5. Ask Claude to republish with a Revdoku password

Tell Claude to republish the site with a Revdoku password. Here, the password is 12345.

Agent republishes with password

6. Test the website’s password gate

Open the site URL again. Visitors now see a Revdoku password gate before the weather dashboard loads.

This is a real gate on the hosted bucket. It is enforced by Revdoku access controls, not by JavaScript inside the generated website.

Password-protected site gate

7. Switch to Require Email to share private site access

For visitor attribution, ask Claude to republish the same site with Require Email access. The visitor enters an email address and verifies it with a one-time code. No shared site password is needed.

Example email-access form for the Magic Stories presentation. The visitor verifies their email instead of entering a shared password.

8. Enter and verify an email address as a visitor

Test the visitor flow by entering an email address and verifying it with a one-time code. The consent copy explains that the owner can track which pages and documents the visitor accesses.

Visitor enters an email address

9. Ask Claude to list protected site visitors

After a visitor accesses the site, ask Claude to list visitors or open Revdoku analytics to review them. The owner can see who opened the site, when, and whether Revdoku captured an email address.

Agent lists site visitors after access

  • Use Public when the site is ready for anyone.
  • Use Password when you need a shared gate without visitor identity.
  • Use Require Email when you need visitor attribution.

Revdoku lets you publish an AI-generated website, protect access, and choose the right access mode. You can start public, switch to password-only for private sharing, and use Require Email when visitor attribution matters.

Just ask to “publish to Revdoku” to publish your as a fast and secure website

from your Codex, Claude or another AI apppublish files or folders

Paste this into your AI app.

Free · Public or protected · Visitor analytics · Forms and email alerts Building websites for clients? Explore Revdoku for agencies

Frequently Asked Questions

Should I publish the site publicly before adding a password?

It is useful to publish and open the site once before gating it. This confirms that the generated website works correctly, so any later access issue is easier to separate from a build or publishing problem.

Is the Revdoku password gate part of the website code?

No. The password gate is enforced by Revdoku access controls on the hosted site, rather than by JavaScript inside the generated page. That makes it more appropriate for private sharing than hiding content with frontend-only code.

When should I use password-only access?

Use password-only access when you want a simple shared gate and do not need to know exactly who visited. It works well for private previews, internal drafts, or temporary review links.

When is Require Email the better option?

Use Require Email when visitor attribution matters. It lets the owner review which email addresses accessed the protected site and when, which is helpful for client reviews, stakeholder previews, or controlled document sharing.

What should I do if the site says it is not available?

Wait for the Revdoku publish process to finish, then reload the URL. A not-available state can appear while the site is unpublished or while a protected update is still being applied.

Can I change the access mode after publishing?

Yes. The workflow shown starts with a public site, then republishes it with a password, and later switches to Require Email. This makes it practical to adjust access as the site moves from testing to private sharing.

What visitor information can the owner review?

After someone passes the gate, the owner can ask Claude or check Revdoku analytics for visitor details. The available information can include who opened the site, when access happened, and whether an email address was captured.

Share:
Markdown version

Related Articles

↧
Loading PDF…