Hi guys,
I want to put some “static” text on some city pages so it gets indexed better by google?
Right now, I have the information as a text field in the database and it loads dynamically whenever that page gets loaded. So different information, for each city at page load.
Is this the most SEO efficient way to do it?
Cheers!
Good question and it’s a bit of a rough answer that’s hard to be certain, but I’ll give you a suggestion (I’m sure there will be more opinions/insights from others on this).
Dynamic text loaded from the database can be fine for SEO nowadays as the Googlebot handles client rendered content well enough now that the static vs dynamic distinction matters a lot less than it used to (for the most part).
But, it might be better to create multiple pages for each city so you have a clean URL structure like yourapp.com/london with static text instead of serving it dynamically from the database to help the crawlers further.
You can then hardcode meta titles and descriptions per city page in your page settings, and make sure your overall page performance is good (fast, mobile ready etc).
Not sure how many city pages you have and the context of your app, but I’m pretty sure Google is wise to websites trying to serve the same or very similar content with a different city name just to get rankings, so I’d only do it if there is a distinct purpose like genuinely different service areas to make sure it’s not a wasted effort on your end.
My 2 cents, likely not an exhaustive list of ways to do it.
Hope that helps,
Reece from CreatorConcepts
If SEO is that important for your use case, look into a prerendering solution. You can basically prerender dynamic pages and then create a custom sitemap that directs users to those prerenders. You would just add all your static cities to the sitemap. I’ve done something similar for my app a month or so ago.
Thanks Parth. Is there an article I can read or documentation on pre rendering?
Check this service out:
They explain it pretty well, and I believe they have some YT videos too!
If you wanted to save money, you could follow what I did and manage your own service.
I used Cloudflare Workers and Browser Rendering to programmatically capture pages to static HTML every week (because marketing pages don’t change often enough) and these are saved as prerenders in Cloudflare KV. I have a custom edge router (check my profile I did a post on this) for my bubble app domain where /sitemap.xml goes to a custom sitemap. That custom sitemap gets updated by the CF Worker. The edge router checks the type of browser agent accessing the page and if it’s a bot it takes them to the prerender otherwise to the actual Bubble app. If you’re not too technical, consider a paid service like the one above or drop this reply into Claude and tell it to help you build this exact thing.
