Treat the URL as part of the visitor experience
Visitors may want to bookmark a topic, share a search result or return to a feed after reading an article. A useful filter should keep the controls and the displayed results in agreement when a page opens from a link.
Version 4 uses the WordPress Query scope for public filter parameters. Internal block identifiers stay inside the saved blocks instead of becoming long public URL keys. You can inspect the address after filtering to see which Query and source it belongs to.
Read the filter and pagination parameters
A category selection can look like ?query-4100-taxQuery-category=guides. Here 4100 is the Query ID, category is the taxonomy and guides is the selected term slug. Your Query ID and taxonomy names may differ.
Search and sorting use keys such as query-4100-search and query-4100-sort. Numeric and date ranges use explicit bounds. Pro custom-field controls identify their source in the key rather than showing a block UUID.
Core Query pagination uses query-4100-page=2 for the second page of that feed. Changing a filter returns the feed to its first result page so a narrower selection does not strand a visitor on an empty later page.
Check a shared link from a fresh page
Filter the feed to a topic with several results. Add a search if that combination is useful, copy the address and open it in a new browser tab. Confirm both the selected controls and the post titles match the original view.
Try a filter with no results and use Reset to recover. Unrelated page parameters should survive the interaction. Do not manually invent a Query ID: build the link from the address generated by the actual feed.
The unreleased development URL formats are not a public compatibility contract. Use the readable links generated by the current version rather than storing links with internal UUIDs or the early development envelope. Released legacy blocks keep their own supported behavior.
Test pagination and browser history together
Add the core Query Pagination blocks to the result layout. Open page two, apply a category and confirm the first page of the filtered result is shown. Then choose another result page and verify the filter remains active.
Use browser Back and Forward through those states. Check that the selected topic, search text and results return together. Repeat the flow on a phone, including Apply and Cancel if the design uses a popup.
Current WordPress supports updates within the page; supported older WordPress versions may use ordinary GET navigation. In either case, the visitor should reach the correct results. With JavaScript disabled, the form’s Apply action provides a normal navigation fallback.
Keep multiple feeds independent
A page can contain more than one Query Loop. Each feed needs a distinct Query scope. Filter the first feed and make sure the second feed does not change. Resetting the first should clear only its own filter and pagination state.
If two controls use the same source in one Query, the plugin assigns distinct numbered public keys. Keep the saved control order deliberate and test the generated link after a structural edit.
Begin with a category feed, then check the styling guide to make the active state easy to recognize.