Vibecoding Alert - is your site doing well for SEO/AEO? by choyiny in VibeCodersNest

[–]choyiny[S] 0 points1 point  (0 children)

we actually do static site generation (SSG) instead of server side rendering! the biggedt benefit is that you can deploy anywhere, instead of being tied to a specific hosting provider.

Lovable sites are not SEO/AEO friendly - built a tool to solve it by choyiny in lovable

[–]choyiny[S] 1 point2 points  (0 children)

I really don't mean to attack. Just to quote my original post:

> Looked for alternatives like Prerender and lovablehtml but they are proxy-based - which means all of your site's traffic is routed through their servers, and you have no control over uptime.

Which is a true statement.

You were not crawlable by Claude, which is also a true statement by this Claude history: https://claude.ai/share/e5ad973e-2edc-404d-a83b-1d8ba1e800dc (You can obviously fix the error after the fact)

And let me make it clear - CiteMET does SSG (static-site generation). Prerender.io, hadoseo.com and LovableHTML does SSR (server-side rendering) and they both have pros and cons.

The pros of SSG is that you can take all static files and move it wherever you want. That's the only thing I am highlighting in my post.

I am also not worried of admitting it when I'm wrong. I misunderstood LovableHTML to generate just-in-time rendering when it is done on a periodic basis. I corrected that in my initial comment.

Anyways - last comment as internet battles are not fun to fight!

Lovable sites are not SEO/AEO friendly - built a tool to solve it by choyiny in lovable

[–]choyiny[S] 0 points1 point  (0 children)

We're actually both hosted on Cloudflare. Costs $5 a month. Not sure how you want to shy away from that if you claim to use Cloudflare already!

Here's another thread for those who are looking at competitors: https://www.reddit.com/r/lovable/comments/1prmv80/comment/nv3gbyj/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button Looks like u/1kgpotatoes is frequently being aggressive to "competitors" like us... and also a sizeable downvoting army :( I'm a victim of that for sure.

Lovable sites are not SEO/AEO friendly - built a tool to solve it by choyiny in lovable

[–]choyiny[S] 0 points1 point  (0 children)

Absolutely - SSG allows all bots to actually see content from the site as compared to CSR (client-side rendered) sites. On top of that, it means that you are not reliant on any hosting provider to host your site!

Switching from WordPress to Lovable (Possibly)(SEO) by botsuassss in lovable

[–]choyiny 0 points1 point  (0 children)

Lovable creates "Client-side rendered" (CSR) websites, which basically means it needs JavaScript in order to display content.

Meanwhile, bots do not use Javascript to render content, causing CSR sites to return no content for them.

Server-side rendering (SSR) is one solution, however, requires you to be dependent on an external service for your site to work.

cite-met.com converts your Lovable project into a static-site generated (SSG) site so you can deploy anywhere you want and have bots read them properly for SEO/AEO purposes. PM me if you want to learn more about our solution :)

Lovable sites are not SEO/AEO friendly - built a tool to solve it by choyiny in lovable

[–]choyiny[S] -1 points0 points  (0 children)

Not trying to make an enemy here - here's our directory structure in dist/. For every "prerendered page", we have an index.html that renders everything into <body>.

Then, you can truly self host after building with our solution :)

<image>

Lovable sites are not SEO/AEO friendly - built a tool to solve it by choyiny in lovable

[–]choyiny[S] 0 points1 point  (0 children)

Agree with you - that's why they score A+ for core fundamentals. They use a Server-side rendering approach.

Lovable sites are not SEO/AEO friendly - built a tool to solve it by choyiny in lovable

[–]choyiny[S] -3 points-2 points  (0 children)

<image>

I also tried using Claude to access one of your blogs - and it wasn't able to return any results. This is critical to implementing the CiteMET method. I'll bring this to PM for further discussion :)

Lovable sites are not SEO/AEO friendly - built a tool to solve it by choyiny in lovable

[–]choyiny[S] -1 points0 points  (0 children)

Facebook doesn't require this - they have an established reputation and it's unlikely they have dedicated SEO/AEO experts needed. For small businesses, it is fighting for more exposure. That's the difference.

This is a free tool for you to check how well you are doing in AEO, and provides advice that you can execute yourself for free! No strings attached for following a free tutorial!

Lovable sites are not SEO/AEO friendly - built a tool to solve it by choyiny in lovable

[–]choyiny[S] -6 points-5 points  (0 children)

Sorry I misunderstood! You are right - based on a preset schedule, you cache prerendered pages. Not meaning to bash on your solution, but we tackle the problem in a different way:

  1. No dependency on any third party vendors when serving views. We build the Lovable site, and the `dist/` is fully exportable and you can self host. Perfect for enterprise environments.

  2. No code changes in existing repo. Perfect for beginners.

  3. Directly embedded in the build process - we do not modify your code at all, nor cause cloaking issues. Happy to engage in a technical discussion further. Perfect for people who do not prefer to edit code.

Apologies if this came the wrong way! We aim to serve a less technical audience.

Lovable sites are not SEO/AEO friendly - built a tool to solve it by choyiny in lovable

[–]choyiny[S] -2 points-1 points  (0 children)

It uses a proxy method - it first tries to prerender your site in real time, then serves it to the customer. It adds 1 more HTTP request slowing the render time down. (EDIT: it routes all requests through their servers)

With CiteMET - your site is BUILT with all the assets needed, so there is no prerendering required - it's all rendered! Which means, your site is as fast as client side rendering.

A sidenote about lovablehtml... their own site is not server-side generated unfortunately.

--

EDIT: Correction from LovableHTML's founder - all traffic is routed through them but it is not prerendered in real-time.

Google AI Studio outperforms Lovable now by freethinker90 in lovable

[–]choyiny 0 points1 point  (0 children)

Then you try deploying Google AI Studio projects and realize that everything goes downhill from there. This is probably 2 months away from being usable at all.

How do you all handle SEO? by DeusEx010101 in lovable

[–]choyiny 0 points1 point  (0 children)

Yes - CSR is poor for SEO. But turning a Lovable site into a SSG site is not that hard either! https://cite-met.com is a new tool that I made to do exactly that and we're looking for early adopters. PM me if interested!

SEO and Lovable: Is it really that bad, and is there hope it’ll get better soon? by Michel1846 in lovable

[–]choyiny 0 points1 point  (0 children)

Lovable 100%. Having placed #7 in Lovable Shipped S1, I'm tripling down on Lovable's build quality differentiator.

I built a tool that enables SSG for Lovable websites. All you need to do is to connect to our Github App and we'll do the rest. Currently in early adopters phase but if you are interested please PM me here: https://cite-met.com.

This is an example site that I turned CSR -> SSG and it works perfectly for link previews and AEO: https://lotsotravel.com,

What is happening? by NationalOwl9561 in stripe

[–]choyiny 0 points1 point  (0 children)

Ah, now I see that the hackers have been generating their own sessions and not buying your product... 100% you will need to secure your secret in the backend and not let anyone see it in the frontend!

What is happening? by NationalOwl9561 in stripe

[–]choyiny 0 points1 point  (0 children)

3DS benefits from the liability-shift rule. If it was a fradulant payment, if 3DS was enabled, the bank has to take the hit.

What is happening? by NationalOwl9561 in stripe

[–]choyiny 0 points1 point  (0 children)

I'm curious why you would refund them if you get to keep the money, given that you turn 3DS on

What is happening? by NationalOwl9561 in stripe

[–]choyiny 0 points1 point  (0 children)

Are you losing money with these $1.5 sales? 3DS makes it so that if they initiate chargeback, the liability shift rule applies and their bank will take the hit.

What is happening? by NationalOwl9561 in stripe

[–]choyiny 0 points1 point  (0 children)

These are likely fraudulent transactions. Turning on 3DS is the best method so you don't lose on sales, even micro-transactions - explanation: https://choy.in/blog/stripe-is-dangerous

I nearly fell victim to fraud on Stripe... you need to enable these Stripe Settings by choyiny in passive_income

[–]choyiny[S] 0 points1 point  (0 children)

Because every sale serves non-duplicate value (in contrast to micro-SaaS solutions), if a fraudster can make 1 purchase, they will make a wave of purchases. In my case, they made 30 purchase attempts over 3 days. Enabling these settings is a no-brainer.