FastPages — Bubble.io SEO Fix & Speed Optimization | PageSpeed 20 → 95+ | Fast Performance for Google Page Rank + Real Multilingual Seo on Autopilot

Showcase
21

That sounds amazing.

Just to confirm; the changes on Cloudflare will not break our app, so we can safely have go?

22

A couple of questions:

Your background Data API sync polls the database every 5 minutes. That’s thousands of external API calls a month. How heavily does this background sync impact the monthly Bubble WU costs?

Since Google officially deprecated its support for Dynamic Rendering (serving flat HTML to bots but heavy JS to real users), how do you guarantee a site won’t get flagged or penalized for cloaking?

23

Thanks for posing those insightful questions @senecadatabase . On that note @Xodera are there more under the hooks considerations to be aware of?

24

Here is the most up-to-date, official stance from Google regarding Dynamic Rendering and Cloaking, sourced directly from Google Search Central documentation: [1]

  1. Official Stance on Dynamic Rendering (Current Status)

Google officially classifies dynamic rendering as a temporary workaround, not a recommended long-term solution. [1]

Google explicitly advises against using dynamic rendering for new setups, recommending server-side or static rendering instead due to the complexities and resource demands it introduces. [, 2]

  1. Official Stance on Cloaking vs. Dynamic Rendering

Google confirms that properly implemented dynamic rendering is not considered cloaking, provided the content served to users and bots is substantially similar. [1]

  • Content Parity: The key requirement is that the server produces identical, or near-identical, content for both bots and users.
  • Definition of Cloaking: Violations occur only when different content is served with the intent to manipulate search rankings.
  • Technical Errors: Serving a blank page due to a rendering failure is considered a technical issue, not a deliberate, malicious cloaking attempt. [1, 3, 4]
25

No! You can try it yourself on any test project (if you are afraid and want to test it). It is free to try, no need to pay before you test it. Go try it yourself!

26

It impacts WU usage slightly and only initialy during first and main DB synch. Almost no impact afterwards. You can try it yourself and it is free to try!