Slugs and URL path for better SEO

Need help
1

Hi everyone :waving_hand:

I’m currently building a Bubble app and I’m having trouble configuring slugs to achieve a specific URL structure. I would like my final URLs to look something like this:

website.com/page1/page2/product/page3

Here are a few details that might help you understand the issue:
All the pages involved are of the same data type: Product.
I want to nest slugs dynamically to reflect a deeper hierarchy (e.g., category > subcategory > product > details).
I’ve read a few posts about slugs and URL parameters, but none of them seem to explain how to structure a multi-level path like this.
Ideally, I want to avoid URL parameters (?id=) and use clean, SEO-friendly paths with /slug-name.

  1. Is it technically possible to create this kind of nested path structure in Bubble?
  2. Should I rethink my page structure, or is there a known workaround (e.g., using reusable elements or custom domain routing)?
  3. How can I keep the data source consistent across these nested pages when they’re all based on the same data type?

I’d be grateful for any guidance, best practices, or even examples from your own projects. Thanks in advance for your help! :folded_hands:

2

@joffrey
Totally possible if you can implement SPA combining with slug

3

I have an element in my plugin Data Jedi called Path List Extractor that allows you to set up to 5 path list ‘object types’. What this does is whenever the url path list contains a value that matches the unique field value of one of the 5 types, it exposes that ‘object’ as the selected thing.

I built this because of years of having to setup URL path list structures like this for clients, was just too cumbersome. The need to conditionally represent the URL path list item # as representative of data type A or data type B is inefficient, and adds layers of complexity. Additionally, Bubble doesn’t have the ability to auto detect the path list ‘object’ in the same way they do with URL parameters, so the plugin element solves for that problem as well.

What it makes possible is easy setup for a developer to implement URL structures like

  1. www.website.com/electricians/massachusetts/boston/hvac
  2. www.websote.com/electricians/massachusetts/boston
  3. www.website.com/electrcicians/boston/hvac
  4. www.website.com/electricians/hvac
  5. www.website.com/electricians/boston
    etc. etc., without ever needing to conditionally specify which url path list item is representing which type of internal data.

It also makes it much easier to use dynamically structured templates for the SEO meta title, description etc. There is also a plugin element for breadcrumbs as well so you can easily and dynamically show the breadcrumb path to the user.

But without the plugin it can be done…just time consuming

Yes, but you can not use the ‘page content type’ as when you are going to navigate to the page if using go to page action, the data to send needs to be text and be the URL path list you want, so you can not be forced by bubble to send data as is required when the page content type is used.

No need to rethink page structure. I don’t know of any workarounds.

It is one page, or at least should be. So you have a single page that is setup to have a reusable element that is your search feature, and another that is your product display feature. You should name the page ‘product’ and go for url of www.website.com/product/category/subcategory/product_name/details
This is necessary so that conditionally, if the details is not in URL path list, you show the search function, but if it is you show the product details feature, and you can dynamically filter your search based on the URL path list, so that as they select a category and subcategory, you do not change pages, and when they are done looking at details and press back button, they are exactly where they would expect to be with the search and filters still in tact as they were before selecting one product to look at the details.