Keep a site, or just some pages, private
Lock a draft, a client page or course material behind a passcode, or let in only the people you name. On Builder and up, you can also lock a few pages and leave the rest of the site public.
Say to your AI
“Put a passcode on my site.”
Three ways to protect
Pick the one that fits who should get in.
A passcode for the whole site
One 6-digit passcode, or a longer password, for everyone you share it with. Good for drafts and previews.
Your AI sends you a private link, valid for 15 minutes, where you type the code yourself, so it never has to appear in the chat. You can also just tell your AI the code.
“Lock my site with a passcode.”
Members only, on Prompter and up
Only the email addresses you name can open the site. They sign in with that email, with no new password to remember.
Remove someone and they’re signed out straight away.
“Make my site members-only and let ana@example.com in.”
Locked pages on a public site, on Builder and up
Lock one section, such as everything under /lessons, with a passcode or a list of emails. The rest of the site stays open.
Builder can lock up to 3 sections per site and Team up to 10. They share one passcode or one email list: add a section and it uses the same one, and changing it changes all of them. Company can lock up to 10 sections, each with its own passcode or email list. On Free and Prompter, lock the whole site instead.
Emails on locked sections count in the same members-only visitors total as people let into a whole site.
If your plan ends, you get 14 days with everything working and two emails. After that, locked sections over your plan go offline and visitors see “not available right now”. They are never made public. Upgrade and they come back. Before a downgrade you start yourself, you see what changes and choose to lock the whole site instead or take those pages offline.
“Lock the /lessons pages for my students.”
An example: a driving school
The home page, prices and booking page are public so new learners can find them. The lesson notes and theory videos under /students are for current learners only (locking part of a site is on Builder and up).
Public
/ · /prices · /book · /contact
Anyone can read these, and search engines can find them.
Locked
/students and every page under it
Learners sign in with the email the instructor added, or type the class passcode. A learner who finishes is removed and loses access at once.
Say: “Lock everything under /students. Let in sam@example.com and priya@example.com.”
How it’s kept safe, in plain words
- Passcodes are never stored as writtenWe keep only a one-way scrambled version (a scrypt hash). Nobody at Page Lemon can read your passcode back.
- Guessing is slowed downAfter 10 wrong tries in 15 minutes, a visitor has to wait, and a site that gets too many wrong tries in an hour pauses new attempts.
- A signed pass, not a stored passwordAfter unlocking, the visitor’s browser keeps a signed pass for 30 days, sent only over HTTPS and hidden from scripts. Change the passcode and every old pass stops working.
- Old public copies are clearedWhen you protect a site or a section, any copies saved by our content network are cleared, so the pages aren’t served from a cache afterwards.
- HTTPS everywhereEvery page, passcode and sign-in travels encrypted.
- Where your data livesOur servers run in London, UK. Site files and backups are stored in the EU.
More detail: Security (plain answers) and Trust (how it’s built, providers and what isn’t done yet).
By plan
| Plan | Free | Prompter | Builder | Team | Company | Enterprise |
|---|---|---|---|---|---|---|
| Passcode for the whole site | ||||||
| Members-only visitors (across all your sites) | 25 | 100 | 250 | 500 | Set per contract | |
| Locked sections per site (passcode or email list) | 3, sharing one | 10, sharing one | 10, each with its own | Set per contract |
Members are counted once per person, however many of your sites they can open. Compare plans
Questions
Is a passcode enough for confidential documents?
A passcode keeps casual visitors and search engines out, and anyone with the code can get in. For anything sensitive, use members-only, so each person signs in with their own email and you can remove them one by one.
Do my members need a password?
No. They sign in with the email address you added, so there’s no new password to remember.
Will search engines show my locked pages?
No. Locked pages show a sign-in or passcode screen instead of your content, to search engines as to everyone else.
Can I change or remove the passcode later?
Yes. Ask your AI. Changing it signs out everyone who used the old one.