Appearance
Return
Understanding URL params and paths
Use the URL to load the right record, build clean links, and handle dynamic pages.
Steps at a glance
- Understand the page path (the part after your domain).
- Use URL parameters to pass values like an ID.
- Read those values to load the right data.
1) Paths vs parameters
- Path: the route to a page (for example
/products). - URL parameters: extra values in the URL (for example
?search=shoes).
To read a URL parameter like search in your app, create a variable of type Query with the same name.
Learn more about URL parameters →
2) Use parameters to load data
Common pattern:
- User clicks a link like
/product?id=123. - Your page reads
id. - Your page loads the record with that ID.
In WeWeb, you usually put the ID in the page path instead, for example product/{{id}}. Read id in the binding window under Page → From path in current page, then pass it to a table view that returns the matching record.
Learn how to build a dynamic page step by step →
3) Keep links consistent
- Use the same parameter name everywhere (for example always use
id). - If you change it, update every link to avoid broken navigation.
Common pitfalls
The page loads but shows no data
- Confirm the URL has the parameter you expect.
- Confirm the parameter value matches an existing record.
You can't add a path parameter to your home page
- The home page is the root
/page, so it can't have path parameters. Put the dynamic content on a separate page, for exampleproduct/{{id}}.

