[Solved?][NEW] More Eyes on Website, Improve SEO with Cloudflare Subfolder instead of Subdomain

Hello all,

As you may know, search engine optimization (SEO) on Bubble needs improvements, even after correctly applying the standard SEO settings in Bubble. To allow the use of a subfolder (AppNameHere.com/subfolder) instead of a subdomain (subdomain.AppNameHere.com), @lindsay_knowcode and I are developing a solution to get your website in front of more eyes.

The reasoning behind this for SEO and subsequent brief to achievability can be found (1) Cloudflare Part 1 and (2) Cloudflare Link 2. (3) Here is a forum post previously mentioning this matter.

If you are interested in finding out the solution, have a strong desire to achieve this, want to help fund, or have additional resources, please reach out via this thread or direct message. Those interested in helping or promoting the cause will get access to the solution for free, others will have to pay for it later. To promote, reply to this post or like this post to get the solution for free - will be making a list of users next Saturday.



See the increase in results for your SEO. Huge if you want to get traffic and customers without paying an arm and a leg.

1 Like

I sent you guys a message there is currently a solution for this built into bubble.


Perhaps post your solution here as well?
If not, do you mind private messaging me the solution as well?


I’ll have a talk with them to ensure I’m not wrong about what they’re doing, if so we will potentially collab on a video walkthrough

We’ve achieved this simply by building the blog functionality on bubble and migrating from ghost.
see what we got here No-code blog by Zeroqode

Levon Terteryan
Founder @ Zeroqode
#1 Bubble Publisher and Developer


:file_folder: 130+ Bubble Templates
:mortar_board: 25+ Bubble Courses
:gear: 300+ Bubble Plugins
:iphone: Convert Bubble app to iOS & Android
:man_technologist:t4: No-code Development Services

1 Like

Interested in solution. Love to see what you guys upto. Let me know how I can part of this apart from helping you guys fund.


@tyler7 awesome! Would love to know what will be your solution.
I’ve met @Emmanuel and he said SEO is not on their roadmap so we will have to figure out ourselves :slight_smile:


There is a misunderstanding… I didn’t say it wasn’t on our roadmap, I said it wasn’t on the near immediate roadmap. It’s definitely on the list of things we want to improve, just won’t be able to do this in the coming weeks.


What’s the ETA? Will there be the ability to host websites from other website builders to be hosted in the subfolders of the Bubble app (i.e. Ghost)?

Are the methods mentioned in Cloudflare Part 1 and Cloudflare Link 2 achievable solutions in the interim?

Built using an iFrame, correct? The domain you’re adding the iFrame to doesn’t get credit (no increase in domain authority) for the SEO within the iFrame. How does this benefit SEO? Solely the number of keywords on your website?

Referencing this article: iFrames and SEO

no iframes, all in a bubble app using Bubble’s functionality


Okay awesome. Can you please provide insight how you migrated from Ghost to the functionality built in Bubble?

I’m unclear on the challenge. Is that you have a Bubble app on AppNameHere.com and:

  1. a separate blog system (Ghost, etc.) on blog.AppNameHere.com?
  2. a separate Bubble app on blog.AppNameHere.com?

Well you’re literally just building a Ghost clone in Bubble. Sure it can’t do absolutely everything Ghost can and some SEO features like subdirectories to show topic clustering aren’t really possible in Bubble without playing around with URL rewrites, but if you want a blog with h tags, image alt text, link attributes etc, then Bubble can definitely do that.

The one key thing is finding a text editor that outputs HTML and displaying your blog as a HTML block instead of a text block. However in saying that there’s nothing stopping you from creating a blog built on a repeating group (if you really wanted to).

In short, it works.

However if there is a reliable solution that enables users to use Ghost instead of building their own blog functionality in Bubble, then that’s going to be more robust from an SEO perspective. Only caveat is it’s just a bit harder if they’re trying to create a seamless visual experience between their blog and the rest of their site.

I have a Bubble app on AppNameHere.com and want to have a seperate blogging system on AppNameHere.com/blog instead of blog.AppNameHere.com.

However, for performance and SEO, it seems having the home and landing pages on W e b f l o w will be more beneficial.

This would move the W e b f l o w website to AppNameHere.com and I intend to move the Bubble app to AppNameHere.com/marketplace instead of marketplace.AppNameHere.com.

Got it @juicebox. Currently have a blog built in Bubble, you can see it here. I thought @levon meant migrating date from a Ghost blog into a Bubble built one which had me confused. I realize now he means that he used to use Ghost but built the functionality on Bubble, and now uses Bubble instead of Ghost.

I’ll provide a bit more context on where my concern lays:

I checked my website on SEMrush, a leading SEO tool and it doesn’t recognize the keyword “ATV” in the body, title, H1 or meta tags. Which I find bizarre considering my entire website is about ATV, UTV, Jeep, motorcycle, boat and jet ski rentals. But when you inspect outrec.com it shows the keywords in the the body, title, H1 and meta tags.

That combined with the GTmetrix score of an “F” and PageSpeed Insights score of 15 for mobile and 17 for desktop along with other forum posts here, here, here and this article, it raised a few concerns. I remade the same page on W e b f l o w, and it performed better on GTmetrix and PageSpeed Insights with a mobile score of 51 and a desktop score of 99. I then compared the performance of my website to Ghost. For this test, I used a builtwith.com to find blogs that used Ghost. The GTmetrix score was 100% and the PageSpeed Insights scores were 79 for mobile and 95 for desktop.

The attached screenshots are from my SEMrush account.


That leaves me assuming W e b f l o w for the home and landing pages and Ghost for the blog.

The issue lays in moving from blog.AppNameHere.com to AppNameHere.com/blog; moving the Bubble app from marketplace.AppName.com to AppNameHere.com/marketplace. Which is why Cloud Flare is needed.

Without it, we miss out on the exponential increase organic traffic moving from blog.AppNameHere.com to AppNameHere.com/blog

1 Like

This doesn’t entirely surprise me, tools like SEMrush and Ahrefs have historically struggled with webpages that are reliant on client-side javascript to build the page. This is because they’re just scanning the page source and not actually rendering the page.

Yeah I don’t think anyone is disputing that Bubble really struggles with Lighthouse and GTmetrix (which also uses Lighthouse). Using a platform like Ghost would drastically increase these scores and more importantly from an SEO perspective, Core Web Vitals.

So yeah, we’re keen to see how you might achieve this with Cloudflare workers as it’s been tried before by @stephane but it just got too hacky in the end to be a reliable solution.

1 Like

The plan now is to have the Webflow domain as the main domain. Bubble for the app functionality. Ghost for the blog. Webflow as the main domain may allow this to work. Will research the Webflow forum and report back.

In the mean time, here are some additional resources. Courtesy of Webflow customer support.

Medium Article on Reverse Proxy
Cloud Flare Reverse Proxy Defintion
Additional Proxy Info, see excerpt below

How a reverse proxy works

Step 1: To setup a reverse proxy you’ll need to access your .htaccess file on your main website. Essentially you’re asking your main domain to return a request for /subfolder/ from the subdomain.
Step 2: Once you have the same content on /subfolder/ as you do on your subdomain you need to make sure there’s no chance of getting penalised for duplicate content. To do this you’ll need to ensure that no subdomain pages are being indexed.
Step 3: Then you’ll also need to transfer over your link juice that’s pointing to the original URLs. To do this you’ll need to implement a canonical tag that points to the /subfolder/ URL for each of the subdomain URLs.
Step 4: To ensure search engines aren’t crawling the old URLs, you’ll also have to add a disallow directive in the robots.txt file hosted on the subdomain.

**UPDATE: Found someone on the Webflow forum who has done it between two websites.