Hi.
You could somehow manually create a sitemap or, like a user in this forum have suggested, have a page listing all the unique URLs for the site, but I think the problem is that those unique URLs are still not pre-rendered when a user (or most importantly, Google) requests them. Or are they?
That’s something only the Bubble team could answer. I’ll be interested to know that too or if someone has come up with some solution to do pre-rendering for bot requests for a bubble app.
Been waiting for someone to bring this up. @Bubble @neerja @emmanuel
Will integration with this work? If I create a plug-in will it do it or does it need to be tied in from your end?
While we are on this topic, I would also like to understand the impact of doing this form of pre-rendering on the server side (via directly or some plugin) from app performance perspectives. Would it significantly downgrade the server performance and require a need to add more capacity for instance.
@romanmg don’t you have a youtube tutorial on adding your own sitemap to your bubble site? Can you link that here?
I don’t think any plugin will allow you to do server side rendering. It has to come from Bubble directly.
But to be fair, I have actually watched the whole video that article is based on (https://www.youtube.com/watch?v=EZtCgrpa6ss), and it is not as alarming as the article portraits it.
Basically, as far as I understand it, Google recommends not to do too much client side JavaScript rendering because it can lead to bad user experience (JavaScript files taking too long too download, visual elements taking too long to display…), which is what is actually happening right now with Bubble sites.
If you run a Lighthouse analysis on any Bubble site, you will find that the site takes too long to become visible for the user, it has too many DOM elements, etc, resulting in a very poor score. This results in bad ranking.
Ideally Bubble so do some server side rendering, purely to minimize the amount of JavaScript to download (perhaps just the layout).
It’s also worth noting that for the bots, it is much simpler to understand html than JavaScript, hence it helps to do some server side rendering.
@duke.severn this video shows how to expose your sitemap in Bubble and upload it to Google Search Console.
Thanks for the video.
Unfortunately, Bubble only generates links for the pages, not for the unique urls based on the ids that those pages take.
So basically, this is valid for static pages, but not for dynamic pages.
The solution is, as one person in the forum suggested, to manually create a sitemap containing all the unique urls for the site, or have a page that lists the links to all those unique urls.
@miguel What happens if you have a link that is sending data to the page?
I am trying to make sure that all of my product pages and blog post pages ( all of which are dynamically created ) are indexed and crawled by google.
I’ve been reading that the only way to get crawled is to have links to the page. I assume that in my search results page ( which shows all products ) I can put a link in the repeating group cell and have that link “send data” to the page. This works by actually linking to and sending me to the correct product page.
What I am curious about, is if google would recognize each link as a unique link to a unique page and crawl it.
Would this be the correct approach to optimizing for SEO?
Hi Miguel,
Basically, Google does not like JavaScript pages that are not pre-rendered server side.
Unfortunately that’s how Bubble currently works. Bubble only pre-renders the title and description, but the rest of the page is within JavaScript code, and rendered client side.
Isn’t this solved by this feature?
As far as I know, Bubble only sends the pages to Google, but not each instance of the pages (an instance being a specific record shown in a page).
So you might have a page to display a car (Thing), but there can be many different instances of a page (each instance being a record in the car table).
I presume Bubble only sends 1 page to Google, but not each instance of the page. Google must crawl your website to get each instance, but since Bubble is not very SEO friendly, Google will have a hard time reading each instance of the page.
Bubble only sends the pages to Google
I am sure that’s correct 
If you want all instances of the page being rendered and/or indexed by Google, you should make sure they all have a unique URL by, for example, assigning a type of content to use for generating unique readable URLs.
Only problem left is that you can’t automatically generate a sitemap that contains these URLs, because Bubble doesn’t provide a way to do so. Might be a nice feature to add as an option in the SEO/Metatags tab of the application @emmanuel ?
Besides that the (readable) URL paths are never “clean” since they always contain the data record’s ID after the “readable” part of the path, which is not user (and therefore SEO) friendly from a cosmetic point of view I suppose.
Sudsy plugin might be a solution too here, didn’t try it yet though.
I did. See here. 
Replying to follow-up this thread on updates if any on pre rendered pages.
Does anyone know if these features can be used on free plan?
Hi @emmanuel this needs more work I think, bad comments on the forum, personally suffering. Launching and I cant find myself in google even if i google our literal site name. rentmies.com i love your product until now, but I want to sell and not being index, or found is not in line with that. pls fix lol
