> 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/troubleshooting-and-faq/widget-not-appearing.md).

# Widget not appearing

Work through these checks in order.

## Shopify

1. Confirm the correct live theme is being viewed.
2. Open the theme editor and confirm **Try-On (store-wide)** is enabled under **App embeds**.
3. Select **Save** in the theme editor.
4. Confirm the product page supplies a featured product image.
5. In the Shopify App, confirm the plan is active and the feature includes that product.
6. If using the manual app block, re-copy its key and URL values from Selvette.

## Custom site

1. Confirm the widget script request returns successfully in the browser Network panel.
2. Confirm `data-tryon-key` is present.
3. Replace any example `data-tryon-product-image` value with the real HTTPS image.
4. Confirm the page's exact origin is listed under **Widget → Install → Allowed origins**.
5. If placement is `hidden`, add an element with `data-tryon-trigger`.
6. Confirm the page performs a full reload or remount when moving between products in a client-side app.

## Product availability

* If image try-on uses **Selected products**, enable this product.
* An explicit product **Off** overrides the store default and selected collections.
* A product marked as Live AR makeup does not show image try-on.
* An AR makeup product with no shades shows no Selvette launcher.

## Browser console messages

* **origin not allowed** — add the exact scheme and hostname.
* **product image still contains the placeholder** — supply the dynamic product image.
* missing key or script request — copy the install values again from your own account.

If the theme's normal Add to cart still works, Selvette is failing open as designed.


---

# 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/troubleshooting-and-faq/widget-not-appearing.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.