I always build an SEO-friendly path URL structure with apps that I create, even for pages behind authentication. i.e.
domain.com/page/privacy
Here’s how I do it without plugins…
1. Page Structure
While each app is different, more often than not, I’ll take a hybrid approach.
I split pages by function/feature and then hide/show groups based on the URL path.
Why? This is typically a middle ground between minimizing page reloads & lightweight pages.
2. Group Visibility
Make the sections of your page visible based on the URL path.
i.e., if I have a page called Onboarding and a section called Questions, and I wanted my URL to look like
domain.com/onboarding/questions
3. Navigation (Simple)
Whether you’re using a Link or Go To workflow action, all you need to do is type in the path like this ![]()
4. Navigation (Nested)
What happens if you have multiple layers to your page, say category/questions
So your URL would look like
domain.com/onboarding/category/questions
It works like this ![]()
5. Why do this?
- SEO friendly if the page is indexed in Google
- Deep link to particular page states, bookmark friendly!
- Improved UX as your page won’t reload
- Full history in the users browser
- Browser back/forward buttons work without reload
- Dynamic page titles
Josh @ Support Dept
Helping no-code founders get unstuck fast
save hours, & ship faster with an expert
on-demand



