> 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 %}
CategoryA/B TestURL Test
How changes are madeContent is changed dynamically on the original pageVisitors are distributed to a separate URL for each variation
Best suited changesIndividual elements such as buttons, copy, images, and colorsOverall structure such as design, layout, and page composition
How to prepareImplement the change logic on the original pageBuild and host the modified pages separately
Where to useWeb and appWeb pages
### 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 ``. {% 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.hackle.io/en/ab-test/url-test/url-vs-a-b-test.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.