> ## Documentation Index
> Fetch the complete documentation index at: https://docs.goguardian.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Wildcard Rules in Policies

> Reference for wildcard syntax in the Website URLs section of GoGuardian Admin policies.

Administrators use wildcard rules in the Website URLs section of a policy to block or allow any URL that matches a pattern, not just an exact address.

## Review Wildcard Behavior

An asterisk (`*`) matches any sequence of characters in a URL, including subpaths, query strings, and subdomains. Place it anywhere in a pattern to capture variable content.

**Implicit wildcard at the end of every rule.** All URL entries have an implied `*` appended automatically. Blocking `website.com` behaves the same as blocking `website.com*`, which blocks `website.com`, `website.com/page`, and any other URL that begins with that string.

<Note>
  Block rules and allow rules use identical wildcard syntax. The examples below use block rules, but the same patterns work for allow rules: they allow the matched content instead of blocking it.
</Note>

<img src="https://mintcdn.com/goguardian/6oeTNHuO5gzC1O1Y/images/screenshots/filtering-with-wildcards/step-01.png?fit=max&auto=format&n=6oeTNHuO5gzC1O1Y&q=85&s=bfec83cd39a3cecad02fe8fa5154f025" alt="Review Wildcard Behavior" width="2874" height="1188" data-path="images/screenshots/filtering-with-wildcards/step-01.png" />

## Look Up Wildcard Patterns

| Pattern type       | Example                                   | What it matches                                                                                                                        |
| ------------------ | ----------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| Direct keyword     | `*proxy*` or `*proxy`                     | Any URL containing the string `proxy`                                                                                                  |
| Multi-word keyword | `*game+of+thrones*` or `*game+of+thrones` | Any URL containing the phrase "game of thrones" (the `+` represents a space character in a URL)                                        |
| Subdomain block    | `*.mlb.com`                               | Subdomains such as `yankees.mlb.com` and `dodgers.mlb.com`, but not the root `mlb.com`                                                 |
| Search filtering   | `*search*term` or `*search*term*`         | Only search results containing "term" on Google and YouTube, not every page with "term" in the URL                                     |
| Multi-word search  | `*unblocked*games`                        | Google and YouTube searches for "unblocked games," and any URL that contains both terms in that order with any characters between them |
| Google Images      | `*tbm=isch` or `*udm=2`                   | Google Images results pages (`tbm=isch` is the classic parameter, `udm=2` is the newer equivalent)                                     |

<Tip>
  If a wildcard rule unintentionally blocks a legitimate site, add that site as an allow rule in the same policy. Allow rules take precedence over block rules, so the specific allow entry overrides the broader wildcard block.
</Tip>

<Tip>
  Short keyword patterns can produce unexpected results. Blocking `*games*` also blocks `coolmathgames.com` and any educational site with "games" in its URL. Terms like `proxy` or `vpn` may also appear in legitimate URLs such as Google Docs or Google Drive share links. Use the most specific pattern that covers the intended target.
</Tip>

## Keep Search Filtering Active

The `*search*term` pattern targets only search result pages, which makes it useful for filtering specific queries without blocking the broader site.

Do not add `Google.com`, `Google.com/search`, or `YouTube.com` to the allow list. Adding those addresses directly to the allow list bypasses search filtering.

## Apply Common Block Patterns

GoGuardian recommends adding the following wildcard patterns to your default block policy. These patterns target common circumvention tools and high-traffic restricted sites.

| Pattern       | What it targets                                    |
| ------------- | -------------------------------------------------- |
| `*proxy`      | Proxy and proxy-finding sites                      |
| `*search*vpn` | URLs where users search for VPN services           |
| `*bypass`     | Sites advertising bypass or circumvention tools    |
| `*unblock`    | Unblocked-games directories and unblock-tool sites |
| `*agar`       | Agar.io and related variants                       |
| `*slither`    | Slither.io and related variants                    |
| `*splix`      | Splix.io and related variants                      |
| `*sl4sh`      | Sl4sh.io and related game variants                 |
| `*123movie`   | 123Movies and mirror sites                         |
| `*putlocker`  | Putlocker and mirror sites                         |

## Resources

<CardGroup cols={2}>
  <Card title="Create a Filtering Policy" href="/products/admin/create-a-filtering-policy">
    Add wildcard rules to a new or existing policy.
  </Card>

  <Card title="A Site Is Blocked Unexpectedly" href="/products/admin/site-blocked-unexpectedly">
    Troubleshoot blocks caused by wildcard rules or category filtering.
  </Card>
</CardGroup>