> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/product/settings/security/content-security-policy-csp/frame-ancestors-csp.md).

# Frame Ancestors CSP

By default, Limio paages have the **X-Frame-Options** header set to `'sameorigin'` as a security measure. This prevents unauthorised embedding of pages on external sites. However, you can define specific domains where you want to allow Limio pages to be hosted, enabling you to embed Limio pages within an iframe on other sites.

To embed a Limio shop page on an external site, follow these steps:

1. Navigate to **Settings** > **Allowed Hosts**.
2. Locate the **Allowed Ancestors** section.
3. Specify the domain(s) where you want to allow the page to be embedded.

Ensure that the URL starts with `"https://"` and does not include any trailing slashes (`"/"`).

<figure><img src="https://3320508512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAw9J8ugfVIqzNtzPQiWO%2Fuploads%2Fgit-blob-afcd34b5c9b186c188f580d567c3d15793c8d203%2Fimage%20(224).png?alt=media" alt=""><figcaption></figcaption></figure>

If you are using multiple domains, make sure to add the URLs for all the domains where you plan to host the Limio component via an iframe.


---

# 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.limio.com/product/settings/security/content-security-policy-csp/frame-ancestors-csp.md?ask=<question>&goal=<user_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.
