How website projects work
When you create a website project, Huddlekit loads your site inside a secure frame so your team can browse it and leave feedback without any installation. This approach works well for most public websites, but some sites actively prevent this.
Common reasons a site may not load
The site blocks external embedding
Many websites include security headers that prevent them from being displayed inside other tools. This is a standard security measure used by banks, large e-commerce platforms, and enterprise sites. It is set by the site owner, not something Huddlekit can override.
If the site blocks embedding, you will typically see a blank page or an error instead of the site content.
The site requires a login
Website projects only work with publicly accessible pages. If a page requires you to sign in to view it, Huddlekit cannot load it. Use a Web App project instead — you install a small widget directly on your site, so it works inside authenticated areas.
The site uses aggressive security (shared hosting)
Some hosting providers, particularly shared hosting platforms, apply extra security rules that interfere with external tools. SiteGround shared hosting is a known example. Sites hosted there often cannot be loaded reliably in website projects regardless of the URL.
Mixed content or redirect loops
Sites that redirect HTTP to HTTPS in unusual ways, or that load resources over mixed protocols, can sometimes fail to render correctly.
What to try
- Check if the site loads in a private browser window — if it does not load there either, the site may have restrictions that apply broadly.
- Try a specific page URL rather than the root domain. Some pages have fewer restrictions than others.
- Switch to a Web App project if you need to review content behind a login or on a site with strict security settings. See Website vs. Web App.
When website projects work best
Website projects are ideal for:
- Public marketing sites and landing pages
- Staging or preview URLs that are not password-protected
- Sites you built yourself or control (where you know embedding is allowed)
If your site falls outside these cases, a Web App project is the right choice.
