> For the complete documentation index, see [llms.txt](https://docs.zigpoll.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zigpoll.com/playbooks-for-agencies/cro-audit.md).

# CRO Audit

### When to run this process

1. You're launching a new site for your client and want to catch any issues at go-live quickly
2. You're onboarding a new client for CRO and want to identify quick wins to prove value and build trust
3. You want to add CRO as an additional add-on and want to surface quick wins

### Surveys to run and questions to ask

1. Exit intent survey (all pages)

* Ask something like: "Before you go! Was there anything you found confusing about this site?" (multi choice). Offer answer options like:
  * Navigation was difficult to use
  * Couldn't find what I was looking for
  * Product descriptions weren't clear
  * Other

2. CRO survey (product pages, pop up after \~120 seconds)

* Ask something like "Does this page contain everything you need to know about the product?" (Binary)
  * Ask a follow up like "Anything else to share?" (open ended)

3. Post Purchase survey, ask something like:

* "Was there anything that almost prevented you from making a purchase?" (open ended)
  * then ask any other PPS questions like attribution etc... which would be relevant to customers.

### Spotting opportunities

Use our [Slack](/integrations/slack.md) integration to notify your team of new responses as they roll in.

Use [Analytics, AI, and Reporting](/analytics-ai-and-reporting.md#z-gpt-insights-embedded-ai-summarization-on-surveys) to summarize themes and surface trends quickly.


---

# 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.zigpoll.com/playbooks-for-agencies/cro-audit.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.