> For the complete documentation index, see [llms.txt](https://docs.locoia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.locoia.com/embed-white-label-portal/embed-admin-setup/5.-testing.md). # 5. Test Embed Configuration Pre-Deployment testing options Before integrating Embed you might want to check that all the settings are correct and the iframe looks as expected for an end user. ### Local testing In order to open an Embed in a local html page (i.e. where the URL is a file path), you need to specify `file://*` in the **allowed domains**. ### Testing on Google Sites One can also test embedding the iframe in Google Sites. In order to allow it to open there the **allowed domains** need to be set to: ``` sites.google.com www.gstatic.com *.googleusercontent.com ``` {% hint style="danger" %} The **allowed domains** settings above should be used solely during the testing phase, where it's absolutely needed. Remove it from the allowed domains once you're going to your staging or production environment as it adds a potential security risk. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.locoia.com/embed-white-label-portal/embed-admin-setup/5.-testing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.