@Kasra_Dash Prerendering is a stop gap solution until they implement something similar or go full SSR (which will cause a host of other problems like security vulnerabilities). We’ve been able to index and rank hundreds of Lovable sites doing this
@TheGMRep@tomeromrix@Base44 It’d be a very expensive feature for something only about 5% of the user base would need.
You can use my solution called Hado SEO, it will fix the issue using pre-rendered static HTML served to social media crawlers.
@SergeyGrim@Lovable It renders the page to HTML and serves it to crawlers, doesn’t provide anything you can export to another platform like Webflow or Wordpress though
@stanlyyaa@Lovable All the best AI platforms output React/Vite apps unfortunately. You can use Hado SEO to pre-render your sites into static HTML for crawlers, it works well for marketing sites without having to migrate to Next.js/Claude code
@MrSulcs You have bug in your code that is serving 404 to prerender io before the content is loaded. The 404 page is snapshotted and served to crawlers, not the movie content.
Common problem on Lovable sites (they develop like a Jr. developer).
@tomeromrix@Base44 This is misleading users who think “unique & automatic” meta tags and social share means that they get working social previews for individual pages on social media, when it’s just an automatic thing Base44 injects with no SSR/pre-rendering
@WizKidTechX@JohnnyNel_ Client-side rendering (Lovable, Replit) vs Server-side rendering (Wordpress)
Client-side rendered apps relies on the browser to render the app. Server-side rendered apps are rendered (to static HTML) on the server before it reaches the browser (or to search engines)
Doesn't matter how optimized your SEO tags and content are if your Lovable site's foundation is built with leftover popsicle sticks and off-brand school glue.
Things like: invisible race conditions, unoptimized queries, lack of pagination/lazy loading.
Guide soon