/index`. This is a last resort, so `ecom/{slug}` still wins over
`ecom/index` for `/ecom/cart`.
A pattern matches only when **both** of these hold:
* Its **static prefix** — everything before the first `{` — is exactly the URL
prefix being tested.
* Its **number of placeholders** equals the number of segments left over.
A page whose slug has no braces is never wildcard-matched. A plain page at
`app` will not catch `/app/anything`; only `app/{slug}` will.
***
## Setting up a wildcard route
### 1. Create the page
Give the page a slug that contains the placeholders, e.g.
```
app/guided-courses/{course}/{module}
```
* **Fixed part:** `app/guided-courses`
* **Dynamic parts:** `{course}` and `{module}`
```bash theme={null}
ef pages create "app/guided-courses/{course}/{module}"
```
### 2. What matches
| URL | `route_params.course` | `route_params.module` |
| - | - | - |
| `/app/guided-courses/foundations/module-1` | `foundations` | `module-1` |
| `/app/guided-courses/advanced/lesson-5` | `advanced` | `lesson-5` |
| `/app/guided-courses/intro/welcome` | `intro` | `welcome` |
The bare prefix `/app/guided-courses` does **not** match this page — two
placeholders require exactly two trailing segments. If you want a landing page
at the prefix, create a separate page with the slug `app/guided-courses` or
`app/guided-courses/index`.
***
## Rules and limits
**Placeholders must all be trailing.** The static prefix stops at the first
`{`, so any literal segment written *after* a placeholder is ignored when
matching:
| Slug | Behaves as | Matches | Does **not** match |
| - | - | - | - |
| `blog/{slug}` | prefix `blog`, 1 param | `/blog/hello` | `/blog/2024/hello` |
| `blog/{cat}/posts/{id}` | prefix `blog`, 2 params | `/blog/tech/5` | `/blog/tech/posts/5` |
To keep a literal segment in the middle, put it in the fixed part instead:
`blog/tech/posts/{id}`.
**A slug cannot start with a placeholder.** Matching always tests at least one
literal leading segment, so a slug like `{hl}/about` never matches any URL.
Start the pattern with a real segment (`docs/{topic}`).
**Sibling patterns are disambiguated by prefix.** `blog/{slug}` and
`blog/category/{slug}` can coexist: `/blog/hello` picks the first,
`/blog/category/news` picks the second, because each pattern's static prefix
must equal the URL prefix exactly.
**Offline and deleted pages are skipped**, and at most 50 candidate patterns
are considered per prefix.
**Wildcard pages are never listed in [`sitemap.xml` or `llms.txt`](/pages/seo)** — a
`{param}` slug stands for many URLs, not one. Link to concrete URLs from a
listing page you *do* publish.
***
## Reading the segments
Two values are available once a wildcard route matches:
* **`route_params`** — an object keyed by your placeholder names, e.g.
`{ course: 'foundations', module: 'module-1' }`.
* **`route_slug`** — the whole remainder as one string, e.g.
`foundations/module-1`.
Both are `null` when the page was reached by an exact slug, the domain index,
or the folder-index fallback.
The keys of `route_params` are always your placeholder names. There is no
`segment_0` / `segment_1` — name the placeholder whatever you want to read
(`{slug}` → `route_params.slug`).
### In a template
```html theme={null}
Course: {{ route_params.course }}
Module: {{ route_params.module }}
```
### In a backend script
`route_params` arrives on the request object:
```js theme={null}
// efmeta:{...}
const { course, module } = request.route_params || {};
```
### Guarding
On a non-wildcard URL `route_params` is null, so guard before reading it:
```html theme={null}
@if(route_params and route_params.course)
@set(course = getCourseBySlug(route_params.course))
@endif
```
***
## Use paths, not `?id=`
For any page that renders **one of many** records — a product, a course, a
blog post, a category — put the identifier in the **path** via a wildcard
route rather than in a query string.
| | Wildcard route | Query string |
| - | - | - |
| URL | `/shop/product/blue-widget` | `/shop/product?code=blue-widget` |
| Indexed by search engines | Yes, as distinct pages | Usually collapsed to one URL |
| Shareable / readable | Yes | Poorly |
| Analytics | One row per product | One row for every product |
| Cacheable at the edge | Yes | Query strings often bypass the cache |
| Ad platforms | Clean destination URLs | Params get stripped or rewritten |
Query strings still make sense for things that **modify** a view rather than
identify it: `?page=2`, `?sort=price`, `?hl=en`, and UTM tags.
### Product detail pages
Build the page once with a placeholder:
* **Page slug:** `shop/product/{code}`
* **Template:**
```html theme={null}
@set(product = getProduct(route_params.code))
@if(product)
{{ product.title }}
{{ product.price | formatPrice:product.currency }}
@endif
```
`getProduct()` accepts a product **id or code**, so the segment can be either.
Link to it from your catalog with the **`productUrl`** filter, which emits
`//-`:
```html theme={null}
@foreach(product in getProducts())
{{ product.title }}
@endforeach
```
That produces `/shop/product/blue-widget-42`, so pair it with the slug
`shop/product/{handle}` and split the trailing id in a backend script:
```js theme={null}
const handle = (request.route_params || {}).handle || '';
const id = handle.split('-').pop();
```
See [Products and shipping](/backend-template-engine/products-and-shipping)
for the full product API.
### Course detail pages
* **Page slug:** `app/guided-course/{course}`
* **Template:**
```html theme={null}
@set(course = getCourseBySlug(route_params.course))
@if(course)
{{ course.title }}
@endif
```
`getCourseBySlug()` also falls back to the URL on its own when you call it
with no argument: it reads `?slug=`, then `route_params.course`, then
`route_slug`. Passing the value explicitly is clearer, and required when your
placeholder is named anything other than `course`.
***
## Examples
### One placeholder — record by slug
* **Page slug:** `app/guided-course/{slug}`
* **URLs:** `/app/guided-course/foundations`, `/app/guided-course/advanced`
* **In template:** `route_params.slug` (or `route_slug`, same value here)
### Two placeholders — course + module
* **Page slug:** `app/guided-courses/{course}/{module}`
* **URLs:** `/app/guided-courses/foundations/module-1`
* **In template:** `route_params.course`, `route_params.module`
### Three placeholders
* **Page slug:** `learn/{topic}/{level}/{lesson}`
* **URL:** `/learn/javascript/beginner/01-variables`
* **In template:** `route_params.topic`, `route_params.level`,
`route_params.lesson`
***
## Summary
| You want… | Page slug | In template |
| - | - | - |
| One dynamic segment | `shop/product/{code}` | `route_params.code` |
| Named segments | `app/guided-courses/{course}/{module}` | `route_params.course`, `route_params.module` |
| The whole remainder as one string | any wildcard page | `route_slug` |
| A landing page at the prefix | `shop/product` or `shop/product/index` | — |
Use **`{name}`** in the slug for each dynamic part, then read
**`route_params.name`** (or **`route_slug`**) in the template or
`request.route_params` in a backend script.
## Related
* [Products and shipping](/backend-template-engine/products-and-shipping) —
`productUrl`, `getProduct`, and the product fields to render.
* [Internationalization (i18n)](/pages/internationalization) — `route_params.hl`
and `route_params.locale` are the highest-priority locale hints, ahead of
`?hl=`.
* [Rendering pipeline](/pages/rendering-pipeline) — where route resolution sits
relative to the template engines.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.