> For the complete documentation index, see [llms.txt](https://help.listly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.listly.io/getting-started/extension-features/url-builder.md).
# URL Builder
When you need addresses for a bunch of pages that share the same URL pattern (like product pages numbered 1, 2, 3…), you can generate the URLs from that pattern instead of gathering them by hand. **URL Builder** creates the full list of addresses from just a few examples, then opens them as tabs or hands them off to Deep Extract.
{% stepper %}
{% step %}
## Open URL Builder
In the Listly panel, click **URL Builder**.
{% endstep %}
{% step %}
## Add your addresses
There are two ways to get addresses into the builder:
* **Pick from a tab** — Open two or more pages from the same domain, and Listly detects the shared pattern and shows it here automatically.
* **Type your own** — Paste your addresses into the box on the right.
{% hint style="info" %}
Not sure where to start? Click **Try the example** to load a sample and see how it works.
{% endhint %}
{% endstep %}
{% step %}
## Find the URL pattern
Once you've entered **two** or more addresses that follow the same pattern, Listly recognizes it. For example:
```
https://test.listly.io/goods/0
https://test.listly.io/goods/1
```
Listly recognizes the pattern as `test.listly.io/goods/{number}`. Click **\[Fill in the rest]** to open the address fine-tuning panel on the left.
{% endstep %}
{% step %}
## Fine-tune the numbers
Once the pattern is detected, use the **Numbers** panel to control exactly which addresses get created.
* **Start** — the first number
* **End** — the last number
* **Step** — how much to increase the number each time
For example, a **Start** of `0`, an **End** of `10`, and a **Step** of `1` produces 11 addresses (0 through 10). Change the **Step** to `2` and you'll get 6 addresses instead (0, 2, 4, 6, 8, 10).
The generated addresses appear on the right, with a running total shown next to **Addresses**.
{% endstep %}
{% step %}
## Extract your data
When your address list looks right, you have two choices at the bottom of the window.
### 1. Open as tabs
If you'd like to review the pages before extracting, click **Open as tabs**. This is handy when you want to check the pages first.
In the **Open as tabs** window, choose how many tabs to open (up to 100), then click **Start opening**.
Once the tabs are open, as shown below, you can collect data from them using [**Extract Tabs**](https://help.listly.io/~/revisions/ScBxF6uM8ptF0F6sGlHY/getting-started/extension-features/extract-tabs).
### 2. Extract
Click **Extract** to automatically run Deep Extract on every generated address. This is the fastest way to pull data from all the pages. For details on how it works, see the [**Deep Extract**](https://help.listly.io/~/revisions/ScBxF6uM8ptF0F6sGlHY/getting-started/extension-features/deep-extract) guide.
{% endstep %}
{% endstepper %}
---
# 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://help.listly.io/getting-started/extension-features/url-builder.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.
