Q&A

Why do some experiences say they're blocked or unavailable?

Some experience owners may view the website using their experiences and issue a take-down request, which may lead to some experiences being taken down or made unavailable on the website.

1. The code might not work after prolonged periods of time, as some might be from unreliable sources. We will do our best to minimize this issue, but for now, please use the Bug Report form if you encounter a problem with an experience.

2. Some companies may change their policy, which may lead to some experiences being blocked because of new embedding policies, which may mean that only specific people with access will be able to get the code from the company with permission, which we do not have. 

3. Normally, you can just refresh the page, and it will work regularly again. If you refresh multiple times and it is still blocked, fill out the form for Bug Reports.

Why aren't there experiences like Roblox or Clash Royale?

Roblox: This is impossible to add because it requires a local client installation and secure browser handshakes that Google Sites can't handle.

Clash Royale: This is also impossible because it uses mobile-native code, and the web versions are usually locked to official portals.

We are doing our best to find workarounds, but the platform makes it a constant battle to bring you the content you want. 

To give you as much content as possible, we have to use "Gadgets" or "HTML Embeds." These act like small windows (iframes) looking into another website. But even this is a struggle:

1. The "Sandbox" Effect: Google puts every embed into its own "sandbox." This means an embedded experience can't save your progress to your browser’s cookies or local storage easily, often resetting your high scores every time you refresh, not saving progress, etc.

2. The Size Limit: Google Sites has strict character limits for embedded code. If an experience's source code is too long, the site simply cuts it off, leaving the experience half-loaded or broken.

Why can't you just add experiences with the link?

Google Sites doesn’t let you fully embed most external experiences websites like CrazyG*mes for a few reasons: 

1. Embedding restrictions

Sites like CrazyG*mes block iframe embedding for security and copyright reasons. Even if you try to insert their link or embed code, it won’t load inside your Google Site.

 2. Google Sites sandbox

Google Sites runs in a “sandbox” that limits scripts, popups, and external content. That means many experience sites won’t work properly when embedded.

 3. Network blocks

Even if you link to a experience site, school Wi-Fi or Chromebooks might block it. Some networks restrict access to experience platforms entirely.

 4. Copyright and hosting rules

You can’t just copy or host experiences from other sites unless they allow it. Only experiences that are open-source or shared with permission can be added directly.

What works better?

Browser-only HTML experiences that are uploaded or hosted safely work best. These experiences:

• Don’t need downloads

• Can run offline (most of the time)

• Are less likely to be blocked

• Work inside Google Sites without breaking