Fix 404 and 403 Errors on Your Hosted Pages

Who it's for

• Anyone whose share link returns 404 Not Found or 403 Forbidden
• Creators who changed access settings and now see unexpected errors
• Users troubleshooting why visitors can't open a page

Steps

1. Open the link in a private/incognito window — this rules out cached redirects or stored credentials.
2. Check the exact URL — a typo in the slug (e.g., share.htmlput.com/p/abc12 vs abc123) causes a 404. Copy the link from History to be sure. See Understand your share link.
3. Verify the page still exists in History — if you deleted it, the link returns 404. Sign in and use History to confirm.
4. Confirm access setting — a Password page returns 403 (or shows a gate) when opened without credentials. Switch to Public if you want open access. See Choose Public vs Password Access.
5. Test with the correct password — if the page is password-protected, enter the exact password (case-sensitive). See Visitors see a password gate.
6. Check for moderation blocks — a banned page returns 403. Review Understand Page Bans and Violation Scores and submit an appeal if needed.
7. Re-create if necessary — if the page was removed or the slug changed, host the HTML again and share the new link.

Gotchas

• 404 = not found (deleted, wrong slug, never created). 403 = forbidden (password required, banned, or access revoked).
• Private/incognito mode is the fastest way to distinguish a real 403 from a cached public view.
• Changing a page from Password → Public is instant; no need to re-host.