> For the complete documentation index, see [llms.txt](https://docs.intelligems.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intelligems.io/get-inspired/test-your-hero-image-and-headline.md).

# Test your hero image and headline

## Find the first impression that sells by testing your hero product

Your hero is the first thing every visitor sees. A stronger image or headline moves more of them deeper into your store, and a test shows you which one wins on real traffic.

#### How to set it up

1. Go to Content and create a new content experience.
2. Pick the page with the hero you want to test, usually your homepage.
3. Open the Visual Editor on the test group and click the hero image, headline, or button to change it.
4. Leave the control group as your current hero.
5. Preview on desktop and mobile, split traffic evenly, and start the test.

<figure><img src="https://2052204893-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2SvefuMLsJyJPAcVXeWc%2Fuploads%2FNDBSUmWh4r0RQQYpgN5T%2Fhero-product-test.png?alt=media&amp;token=0a7b1e8a-9ec8-4442-a439-b4205a71f686" alt=""><figcaption></figcaption></figure>

[Create this experience now →](https://app.intelligems.io/content)


---

# 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.intelligems.io/get-inspired/test-your-hero-image-and-headline.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.
