# Landing Page Setup

Send us one public HTTPS landing page URL.

Examples:

```
https://www.example.com
https://example.framer.website
https://landing.example.com
```

The landing page can live on your root domain, `www`, a subdomain, Framer, Webflow, or another public HTTPS URL. The login buttons must point to the tenant root domain we configure for you.

## Required Button Links

Your landing page should send users to the correct tenant login route.

| Button               | URL                                          |
| -------------------- | -------------------------------------------- |
| Brand login/signup   | `https://<rootDomain>/continue?role=brand`   |
| Creator login/signup | `https://<rootDomain>/continue?role=creator` |

Use your real root domain.

## Normal HTML Buttons

For normal HTML links, use `target="_top"` so the login page opens in the full browser tab.

Brand:

```html
<a href="https://<rootDomain>/continue?role=brand" target="_top" rel="noopener">Brand Login</a>
```

Creator:

```html
<a href="https://<rootDomain>/continue?role=creator" target="_top" rel="noopener">Creator Login</a>
```

## Embedding Requirements

Your landing page must allow itself to be embedded by your tenant root domain.

We display your landing page inside the tenant shell so visitors stay on your tenant domain. The page cannot block that shell from loading it.

Avoid response headers that block embedding, such as:

```
X-Frame-Options: DENY
X-Frame-Options: SAMEORIGIN
```

If you use Content Security Policy, allow the tenant root domain in `frame-ancestors`.

Example:

```
Content-Security-Policy: frame-ancestors https://<rootDomain>
```

## Send Us

* Final landing page URL.
* Confirmation that brand buttons use `/continue?role=brand`.
* Confirmation that creator buttons use `/continue?role=creator`.
* Confirmation that the page can be embedded by your tenant domain.


---

# Agent Instructions: 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:

```
GET https://docs.anwhitelist.com/landing-page-iframe.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.