> For the complete documentation index, see [llms.txt](https://docs.hackle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackle.io/en/ab-test/url-test/url-vs-a-b-test.md).

# URL Test vs A/B Test

{% hint style="info" %}
Choose an **A/B Test** when you are changing small elements within a page. A **URL Test** is a better fit when the entire page changes.
{% endhint %}

<table><thead><tr><th width="140.84375">Category</th><th>A/B Test</th><th>URL Test</th></tr></thead><tbody><tr><td>How changes are made</td><td>Content is changed dynamically on the original page</td><td>Visitors are distributed to a separate URL for each variation</td></tr><tr><td>Best suited changes</td><td>Individual elements such as buttons, copy, images, and colors</td><td>Overall structure such as design, layout, and page composition</td></tr><tr><td>How to prepare</td><td>Implement the change logic on the original page</td><td>Build and host the modified pages separately</td></tr><tr><td>Where to use</td><td>Web and app</td><td>Web pages</td></tr></tbody></table>

### A/B Test

Shows different content to each visitor on the original page.

The server or the client randomly exposes button label Option A or Option B.

{% hint style="success" %}
Use it to validate hypotheses like these.

* Will changing the button copy increase the conversion rate?
* Will changing the product image increase clicks?
* Does the color or order of a specific section affect performance?
  {% endhint %}

### URL Test

Creates a separate URL for each variation and randomly distributes visitors between them. It is also called a redirect test or a split test.

Because the modified pages are operated separately, you do not need to implement change code for each element of the original page. You can start the experiment by adding the prepared URLs and the integration code to `<head>`.

{% hint style="success" %}
It is a good fit for situations like these.

* When you have completely redesigned the design concept of a landing page
* When you have significantly changed the page layout or its components
* When you want to compare separate pages built with a web builder
  {% endhint %}


---

# 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.hackle.io/en/ab-test/url-test/url-vs-a-b-test.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.
