No subdomain, how to host index page elsewhere?

Need help App Organization
1

Hello,

Usually my bubble projects are hosted on a subdomain like app.domain.com BUT, for this one, I’d like something else.

What I’d like :

Is that feasible?

Thanks

2

Yes, you just have to create another page called “my page” and create your app there.

3

Could have mydomain/page be a figma page with the bubble app (using bubble-provided domain name) in an iFrame.

IMO the subdomain is better for SEO and potential browser restrictions around embedding and CORS.

1 Like
4

Sorry but I didn’t understand anything you said.. your question was if it was possible and it is..

5

@mario11 did we both have the same answer? mine just has more fancy buzzwords :stuck_out_tongue:

6

My issue is with DNS records. Having both bubble & figma DNS pointing to the same domain.

In both your explanations, how would you handle this?

Thanks

7

Obviously you can’t have DNS of:

But you can have:

Also you can have:

Can you say more of what your goal achieves?

8

Thanks for the clarification

That confirms that what I wanted is indeed impossible, which was :

On top of the DNS records pointing to different servers, there is another thing that was indeed impossible in my request → to not display “index” in the URL while the index page has a data type. ex: domain.com/my_thing_slug, is indeed impossible, as bubble forces domain.com/index/my_thing_slug

domain.com/

9

@bonjour_17 I didn’t consider reverse proxy for what you’re looking for

10

Here’s the answer for hosting Bubble on a path (domain.com/mypage) while keeping the root domain elsewhere:​

Problem: User wants domain.com (root) to host a Figma site, while domain.com/mypage hosts the Bubble app. The challenge is DNS records - both services need to point to the same domain.

Solution:

The DNS Issue:
You can’t point the same domain to two different servers with A records. DNS doesn’t work that way - you can only have ONE A record pointing to ONE IP address for your root domain.

What WILL Work:

Option 1: Reverse Proxy (Best Solution)

  • Point domain.com DNS to a server you control (VPS, Cloudflare Workers, etc.)

  • Set up reverse proxy rules:

  • This way ONE server handles routing to both destinations

  • Use Cloudflare Workers, Nginx, or Apache

Option 2: Keep Bubble on Root, Embed Figma

  • Point domain.com to Bubble (in Domain settings)

  • Create an “index” page in Bubble

  • Use HTML element with iframe to embed your Figma site on the index page

  • domain.com → Bubble index page (with embedded Figma content)

  • domain.com/mypage → Your actual Bubble app

Option 3: Use Subdomain (Recommended)

  • app.domain.com → Bubble app (A record to Bubble IP)

  • domain.com → Figma site (A record to Figma IP)

  • This is cleanest, no conflicts, better SEO

Why You Can’t Do It Directly:
DNS A records for domain.com can only point to ONE IP address. You’d need either:

  • A reverse proxy to route traffic based on path

  • OR host everything through Bubble and embed external content

If You Must Use Paths:
Use Cloudflare Workers (free tier available):

  • Route domain.com/* through Workers

  • Workers check the path and proxy to correct destination

  • This is the professional solution for path-based routing with different backends