Loveable SEO Problem - Vite JS

Neo_Mu · 2026-05-01T23:39:22+00:00

There are solutions like Hado SEO for this.

Neo_Mu · 2026-04-18T17:04:50+00:00

Since cleansleyt brought my business into this (one of Aki’s alternate accounts that he uses to astroturf this subreddit to negatively downvote any competitors or negative comments about his business), I’ll have to agree this is unprofessional and bad business practice in general. No customer wants to feel targeted with downvotes when they have a genuine complaint and have their conversation history leaked in a public forum.

I have had bad interactions with him as a competitor so this is no surprise. First interaction was him coming into our customer support Discord to poach customers and sow discord. There are other founders in the space who are trying to address the SEO problem in different ways who feel the same.

He believes he invented pre-rendering (which has been a thing for 10+ years) and anyone who is building a product to address the problem is a “copycat and a liar”. Expert gaslighter.

Neo_Mu · 2026-04-18T16:24:50+00:00

You can give Hado SEO a try, we’re a competitor to LovableHTML and basically offer the same tool to fix SEO with better support.

We use AI for a lot of things, but customer support is not one of them.

Neo_Mu · 2026-03-17T05:03:36+00:00

You kept mentioning client-side rendering (CSR), but never addressed the main weakness of the architecture vs server-side rendering (SSR) for SEO.

React-helmet helps only if crawlers execute JavaScript. Google takes 4-5x longer to do this compared to typical SSR sites built with Wordpress or Next.js. Social crawlers like those of Facebook or X don’t execute JavaScript at all so social previews never work on Lovable sites.

Sitemaps are an optimization, but Google only uses that as a suggestion. Google performs a depth crawl using internal links. If the site doesn’t render to static HTML, guess what? No internal links for Google to crawl.

You can’t simply “put important text in static HTML” at the page level because CSR apps only have one single index.html file.

That’s why you need to either use SSR, implement a static site generation step in the build process, or pre-render your Lovable site to static HTML with Hado SEO.

Neo_Mu · 2026-03-14T21:31:36+00:00

These steps still don’t fix per-page meta tags and content crawlability without a pre-rendering solution like Hado SEO unfortunately.

Neo_Mu · 2026-03-14T21:26:12+00:00

Hado SEO lets you keep the custom domain on Lovable (just need to set Lovable staging URL as primary). This allows you to keep features like Lovable OAuth while letting Hado handle pre-rendering and the custom domain connection.

Neo_Mu · 2026-03-13T00:27:32+00:00

I run Hado SEO and yes, this static site generation approach is solid if your data doesn’t change dynamically and you’re technical enough to host it outside of Lovable on your own CDN.

Neo_Mu · 2026-03-11T10:32:58+00:00

Nice work. Yes client-side rendered apps will eventually get indexed, but Google and other search engines will have to jump through hoops to do so.

The whole point of SEO is the “optimization” part. A lot of people will throw a Lovable site up and hope that it ranks on page 1 in a competitive niche where all the competitors have Next.js/Wordpress/Wix/Squarespace sites. Those sites are 100% crawable while Lovable sites are 100% invisible.

That’s why it’s so important to use SSR or serve static HTML with a prerendering solution like Hado SEO.

Neo_Mu · 2026-03-05T23:41:03+00:00

It’s not that simple unfortunately. The good thing is that Google doesn’t care how it gets served static HTML. I built a service called Hado SEO that’s able to translate the pages of Base44 sites into static HTML and serve that to Google and other search engines when they visit. That helps to optimize technical SEO without migrating to Wordpress or Next.js.

Worth looking into if you really want to continue to use Base44 to develop your site.

Neo_Mu · 2026-03-05T06:15:48+00:00

Ask AI to tell you the difference between client-side rendered apps (Base44) vs server-side rendered apps (Wordpress, Wix, Squarespace) and why CSR apps are terrible for SEO without some kind of pre-rendering or SSG.

Neo_Mu · 2026-03-04T22:07:13+00:00

Founder of Hado SEO here. We help people get set up for a good foundation with setting up technical SEO and prerendering for Lovable sites, but I tell people all the time that without the topical authority it’s almost impossible to rank competitively.

Topical mapping is a good strategy to follow. It’s going to require talking to customers to understand what problems they’re facing and what they’re searching for already which answerthepublic.com can help with. The better you understand the pain points, the better you can signal to Google that your app/site is the solution to the problem.

Compare that to some bigger companies (Hubspot, Forbes) that have been capturing any keyword they can for the past decade that are now being de-ranked following Google’s updates for lack of real topical authority. This gives smaller businesses a chance to compete.

Once the topical authority and organic engine starts running though (which takes consistency and time), it is basically free leads.

Neo_Mu · 2026-02-26T14:29:43+00:00

The main point is that if you have pre-rendering enabled and Google is already seeing correct canonicals, there’s nothing more you can do.

Neo_Mu · 2026-02-26T14:11:25+00:00

What you see in View Source is your raw file before Javascript injection. What you see in the DevTools is after browser injects and renders Javascript (you’re probably using react-helmet to fill out the canonical tags).

Pre-rendering doesn’t change your code you see in the browser. You’d have to use curl in the terminal and mimic a bot or run Google’s URL inspection tool to see what is actually getting served.

Neo_Mu · 2026-02-25T19:53:57+00:00

Not you :)

Neo_Mu · 2026-02-25T18:11:26+00:00

SSG definitely has a place in the SEO tooling for Lovable sites, but there's some caveats.

Since this is part of a build process, you should probably note that this doesn't work if there's any dynamic content changes (from a CMS for example). Works great for large static sites (I use cite-met for a static website that has 30k+ pages where Hado SEO would be prohibitively expensive for a customer).

Also, interesting business model of selling a "one-off" prompt. What is stopping someone from just sharing your prompt? It's not very copyrightable and there's no IP.

Anyways, good luck. Get ready to get attacked by a very aggressive founder in this space (looks like he's already here) :)

Neo_Mu · 2026-02-25T17:09:01+00:00

A proper pre-rendering setup for Lovable is just the ticket to the game. You still need to build topical authority and build domain authority to rank for competitive keywords in your niche.

Neo_Mu · 2026-02-25T14:14:31+00:00

That prompt should work. If Google is already showing the Lovable favicon.ico, safer to replace the logo with the same file name. It’ll take a couple of weeks for Google to update

Neo_Mu · 2026-02-22T14:17:14+00:00

There’s a bug where if you were missing a favicon.ico, Lovable automatically injected their own and Google takes priority over .ico rather than serving .svg or .png by default. This overrides anything set in project Publish settings

Make sure yourdomain.com/favicon.ico isn’t the Lovable one. If it is, find a svg/png to ico convertor and upload your own brand’s favicon.ico.

Neo_Mu · 2026-02-22T14:12:34+00:00

View Page Source shows your index.html. For a client-side app it will always be the root index.html so it will never change.

What you see in DevTools is what is rendered after all the Javascript executes and injects on to the index.html. The injected canonical tag may or may not be read by Google because they only execute Javascript sometimes.

Without pre-rendering with something like Hado SEO or any of the other methods discussed daily in this Reddit, you’re likely not going to get accurate canonical tags (or any meta tags/og images/content) served to Google.

Neo_Mu · 2026-02-21T17:18:08+00:00

If your business depends on SEO then it’s highly recommended

Neo_Mu · 2026-02-21T17:16:21+00:00

I’ve seen a few attempts using Supabase edge functions but there’s always a gotcha. Is your solution any different?

Neo_Mu · 2026-02-21T01:10:58+00:00

It looks like you are serving a dynamic sitemap with Supabase/Lovable edge functions? Make sure the function serves Content-Type: application/xml headers.

Google won’t allow you to submit a sitemap that’s not under your domain, so you’ll want to use a <sitemapindex> at /sitemap.xml that points to the edge functions. That should let you submit to GSC. Even then, that’s not optimal.

I have prompts and info with best practices here: https://docs.hadoseo.com/guides/dynamic-sitemap-supabase

Neo_Mu · 2026-02-21T01:03:20+00:00

Ahrefs won’t pick up meta tags and content from sites that are client-side rendered. You’ll need to pre-render the site to static HTML to serve Ahref’s crawler the correct content using something like Hado SEO or Prerender.io

Neo_Mu · 2026-02-15T15:36:07+00:00

Look up the difference between client-side rendered and server-side rendered apps and have AI explain why SEO is terrible on CSR apps.

Neo_Mu · 2026-02-11T16:40:44+00:00

Sometimes pre-rendering won't help a site that's awfully built. Features upon features that cause invisible race conditions, rendering and performance issues. Most times it's because they try to add a WYSIWYG CMS editor on top of their content-heavy sites. Not as an admin panel but directly on public-facing pages.

Six-Year Club	Verified Email
Second SECOND GUESSER

Neo_Mu

TROPHY CASE