> For the complete documentation index, see [llms.txt](https://docs.selvette.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.selvette.com/custom-sites/allowed-origins.md).

# Allow your storefront origin

Selvette only starts widget sessions from storefront origins you allow.

## Add an origin

1. In Studio, open **Widget → Install**.
2. Under **Allowed origins**, enter one origin per line.
3. Select **Save settings**.

An origin includes the scheme and hostname, but no page path:

```
https://shop.example.com
https://www.example.com
```

Add every hostname that serves a real product page. Preview and staging domains need their own entries.

## Values that are rejected

* bare hostnames such as `shop.example.com`;
* paths such as `https://shop.example.com/products`;
* wildcard entries; and
* origins that do not match the page's actual scheme and hostname.

If the browser console reports that the origin is not allowed, copy the product page's origin exactly and add it here.

Next: [Connect add to cart](/custom-sites/add-to-cart.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.selvette.com/custom-sites/allowed-origins.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.