How to Password Protect a Website Made with Claude

Claude can create a website, but Claude does not automatically decide how that website is protected. Access depends on the publishing method. A public Claude Artifact has no simple shared-password gate, while exported HTML, CSS, and JavaScript can be hosted behind real access control.

For a client-only site, ask Claude for browser-ready files and publish those files through Revdoku with a password or verified-email login.

Choose the right publishing path

If you publish through Claude Artifacts, read Claude Artifacts vs Revdoku and review the current Publish dialog. Public Artifact pages may be available to anyone online and can appear in search.

Ask Claude for a clean website export

A useful request is:

Create a browser-ready static website folder. Include index.html and all required CSS, JavaScript, images, and assets. Use relative paths. Do not include API keys, secrets, private prompts, or customer data. Add a short README that explains how to open and test the site locally.

Before publishing:

1. Open the exported index.html locally.
2. Click every navigation link and button.
3. Check mobile and desktop layouts.
4. Search the files for tokens, passwords, email addresses, and private notes.
5. Remove sample data that should not reach a client.
6. Confirm that any form or API feature has an appropriate backend.

A static export cannot safely contain secret API keys. Anything shipped to the browser should be treated as visible to the visitor after access is granted.

Publish the Claude-made site with Revdoku

1. Put the final website files in one folder.
2. Upload the folder or ZIP to Revdoku.
3. Choose Password for a shared secret or Verified email for identity-based access.
4. Optionally allow only named email addresses or approved domains.
5. Publish and open the link in a private browser window.
6. Confirm the access gate appears before the website or downloads.
7. Share the protected link with the client.

Revdoku hosts the exported website. It does not place a password in front of an existing public Claude URL.

You can receive visitor notifications and review page, click, and download activity. When Claude creates a revision, replace the files behind the same Revdoku URL. The client keeps one stable address while the content changes.

For a general walkthrough, see How to password protect a website.

Password or verified email?

A password is quick when several trusted reviewers can share one secret. Verified email is better when you need to know which approved person entered. An allowlist can limit access to specific addresses or company domains.

Neither method prevents an authorized viewer from taking a screenshot or copying content. Access control limits entry; it does not create digital rights management.

Do not embed a fake password in the code

A JavaScript form that compares a password in the browser is not secure. The password or protected content may be visible in the page source or network requests. The host must check access before serving the private files.

Bottom line

Use Claude to build the website and use the host to control access. For a public marketing page, ordinary hosting may be enough. For client work, publish the exported Claude files through Revdoku to add a password, verified-email login, allowlists, activity tracking, and stable updates.

codex mcp add revdoku --url https://app.revdoku.com/mcp
codex mcp login revdoku

claude mcp add --transport http revdoku https://app.revdoku.com/mcp
claude mcp login revdoku