> For the complete documentation index, see [llms.txt](https://docs.pixiebrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixiebrix.com/developing-mods/developer-concepts/types-of-mods/what-are-url-match-patterns.md).

# What Are URL Match Patterns?

PixieBrix uses URL match patterns to determine whether or not a mod should run on a web page. For each mod, you can define the URL match patterns using a combination of any of the following:

* **Wildcards.** Use wildcards to match any character or sequence of characters.
* **Regular expressions.** Use regular expressions to allow for more advanced filtering.
* **Fixed text strings.** Use \*\*\*\*fixed string matches for exact matches.

### Important Things to Know

* If PixieBrix does not have access to a site, you will be prompted to grant access.
* URL match pattern rules are optional, but if you add them, ensure that at least one URL matches the patterns you add.

### Setting URL Match Patterns

You'll see the URL match pattern in the Starter Brick for each mod. The Starter Brick is the first brick in a mod, and must be one of the following:

* Trigger
* Sidebar
* Context Menu
* Quick Bar
* Button

In the Starter Brick [Configuration Panel](/platform-overview/page-editor/page-editor-components/brick-configuration-panel.md), you'll set the **Sites** value to specify where a mod can run.

<figure><img src="https://2274778196-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fq123bF1HPQPV35s5vHa1%2Fuploads%2FClv5xmu9WOf50XirJo4d%2Fimage.png?alt=media&amp;token=ebf2cd60-ec18-45c1-9eba-c07e1ba12769" alt=""><figcaption></figcaption></figure>

### Related Topics

* [Mozilla URL Pattern API](https://developer.mozilla.org/en-US/docs/Web/API/URL_Pattern_API)
* [Chrome Developer Match patterns](https://developer.chrome.com/docs/extensions/mv2/match_patterns/)


---

# 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.pixiebrix.com/developing-mods/developer-concepts/types-of-mods/what-are-url-match-patterns.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.