# Query path not being pushed to the URL

**URL:** <https://community.weweb.io/t/query-path-not-being-pushed-to-the-url/19673>\
**Category:** How do I?\
**Created:** [August 16, 2025, 5:36am UTC](https://community.weweb.io/t/query-path-not-being-pushed-to-the-url/19673 "2025-08-16T05:36:06Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![MappedUp](https://avatars.discourse-cdn.com/v4/letter/m/cdc98d/32.png) [@MappedUp](https://community.weweb.io/u/MappedUp)\
**Post date:** [August 16, 2025, 5:36am UTC](https://community.weweb.io/t/query-path-not-being-pushed-to-the-url/19673/1 "2025-08-16T05:36:06Z")

</div>

Hey all,  
I currently experience a bug where i do have a parent page called “Locations“ which has URL {{param}}=’locations’ in this page i have collection list with rows which include some data. When I click one of the rows I add workflow to navigate me to the same page, same {{param}} but with queries included, it does not push them to the URL, if i change the {{param}} to something else it works but i don’t want to change the {{param}}. Could you please advice how I can handle this ?

Thanks!

 ![image](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/2/2ab580951b933bc57d0cb7bad625b80b049ab08f.png)

---

<div class="post-metadata">

**Author:** ![Agustin\_Carozo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/agustin_carozo/32/13231_2.png) [@Agustin\_Carozo](https://community.weweb.io/u/Agustin_Carozo)\
**Post date:** [August 16, 2025, 1:56pm UTC](https://community.weweb.io/t/query-path-not-being-pushed-to-the-url/19673/2 "2025-08-16T13:56:45Z")

</div>

Hi there, welcome to the community 👋

Can you share a screenshot of your url parameter in your page settings?

I want to check first if everything is set up correctly.

---

<div class="post-metadata">

**Author:** ![MappedUp](https://avatars.discourse-cdn.com/v4/letter/m/cdc98d/32.png) [@MappedUp](https://community.weweb.io/u/MappedUp)\
**Post date:** [August 16, 2025, 2:10pm UTC](https://community.weweb.io/t/query-path-not-being-pushed-to-the-url/19673/3 "2025-08-16T14:10:31Z")

</div>

![image](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/8/87beee2a0c844d1ed333adbbe962d0880dcfdc1e.png)  
This is the main (default) url setting upon login of the page, then i am going to different section called “Locations“:

 ![Screenshot 2025-08-16 at 17.04.08](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/9/99b30586087c175466d8eab4644d60c66d3d92ba.png)  
Upon load the url becomes /dashboard/locations, then inside i have binded collection which has a bunch of rows which can be selected:

 ![Screenshot 2025-08-16 at 17.06.12](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/9/93b3febc56d8fdce355f3dd207b9bd033ab3bd65.png)  
Upomn select of the specific row i need to change the url in order to trigger visibility condition of another section which contains the data that should be displayed based on the queries so on click i perform “Navigate to” wokflowf :

 ![image](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/7/76def05726827588866afec731f5fe8394dc66d5.png)

When i try to test it in order to see the queries in the editors url it does not affect it and stays the same:

 ![image](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/0/0659b7884e7e19d5fa856c92c0c9744b80a9dc5b.png)

---

<div class="post-metadata">

**Author:** ![Agustin\_Carozo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/agustin_carozo/32/13231_2.png) [@Agustin\_Carozo](https://community.weweb.io/u/Agustin_Carozo)\
**Post date:** [August 18, 2025, 2:30pm UTC](https://community.weweb.io/t/query-path-not-being-pushed-to-the-url/19673/4 "2025-08-18T14:30:10Z")

</div>

Hi MApped 👋 thanks for the extra context and the screenshots.

A few things to try/check when navigating to the **same page** with a page param (`param=locations`) and adding **queries** :

• prefer “set query variable” over “navigate to”  
If you’re staying on the same page, the most reliable pattern is to create a **Query variable** (e.g. `loc`) and use **Change variable value → Query → loc** with your row value. That updates the URL and triggers visibility conditions without a route change.

• if you keep “navigate to,” make sure the query actually changes  
Open **Queries → loc → Edit formula** and confirm it returns a non-empty string (e.g. `String(selectedRow.id || selectedRow.slug)`). If it evaluates to `undefined`, `null`, or `''`, the router won’t push anything and the URL will look unchanged.

• editor caveat  
The Editor doesn’t always reflect query updates. Append them manually in the Editor URL for testing (…`?loc=abc`) or test in Preview/Published; the runtime behaves correctly there.

• case sensitivity & name match  
Query names are case-sensitive. If your Query variable is `loc`, the query key must be exactly `loc` (not `Loc` / `LOC`). Same for any variables used in the formula.

• same-URL de-dupe  
If you click two different rows but your formula returns the **same value** as the current `loc`, most routers won’t push a new history entry. For testing, try appending a tiny nonce like `loc = row.slug + '-' + Date.now()` to verify the push occurs; then remove the nonce once confirmed.

• page param collision edge case  
Very rarely, a page param can shadow what you expect from a query update. If you still see no query push, try the non-navigation approach above (“set query variable”). It avoids that collision entirely.

If it still doesn’t update, could you share a screenshot of the **Edit formula** for `loc` (what you’re passing exactly) and the **Variables** panel showing `loc` as a Query variable? That’ll let us spot whether the value is empty, mismatched, or evaluated too early.