> For the complete documentation index, see [llms.txt](https://support.quizkitapp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.quizkitapp.com/building-a-quiz/creating-a-quiz/draft-questions-and-pages.md).

# Draft questions and pages

Best practices for drafting questions for your quiz.

In this section you'll find best practices and suggestions for drafting quiz questions, building pages, and&#x20;

## How many questions should I ask?

We recommend drafting 5–7 key questions. If a quiz is too long, then customers have a higher chance of dropping off.&#x20;

Also, it's a good idea to keep questions conversational:

* “How would you describe your skin?”
* “What is your main skin concern?”
* “What is your age range?”

## Build your pages

**Intro Page:**\
Keep it simple: use a short headline that explains the benefit and one clear “Start Quiz” button. If most of your visitors are on mobile (95% or more), you can skip the intro.

**Questions:**\
Use images with text for lifestyle products. Use sliders for questions about preferences like price or strength.&#x20;

**Forms & Email:**\
Ask for an email only after showing some value (like "See your routine and get 10% off").

{% hint style="info" %}
**Note:**

Older quizzes have the email/SMS collection form set up from the quiz's **Settings** page, under the **Email / SMS Page** tab. Using this setting adds the page to the end of your quiz.&#x20;
{% endhint %}

**Results:**\
At minimum, show a main image, 1–3 recommended products, and a call-to-action to buy. If you’re selling high-end items, consider hiding prices until users are more interested.


---

# 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://support.quizkitapp.com/building-a-quiz/creating-a-quiz/draft-questions-and-pages.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.
