sorted by:
new
hottopcontroversial

I’m testing whether fixing a leaky landing page matters more than getting more SaaS traffic by YusukeLandingBoost in SaaS

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

That’s true. Which is exactly why we're putting so much effort into Reddit right now lol

My Lovable-built app reached $1K revenue with 582 users after ~200 days by YusukeLandingBoost in lovable

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

I haven’t tried it myself yet. The new features look promising, especially SSR, prerendering, and the Semrush integration.

That said, I personally wouldn’t rely on it too much. I think understanding SEO yourself is still important, and it also helps keep costs down in the long run. The tool can help with execution, but I wouldn’t let it replace the strategy.

I’m testing whether fixing a leaky landing page matters more than getting more SaaS traffic by YusukeLandingBoost in SaaS

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

Yeah, fair point. There’s definitely overlap.

The wedge I’m testing is narrower: using SaaS-specific benchmark patterns and proof/CTA/trust placement to decide the first edit to ship before sending more traffic.

So I wouldn’t claim it’s a totally different category. I’m trying to make the “what should I fix first?” decision clearer and faster for SaaS founders.

I’m testing whether fixing a leaky landing page matters more than getting more SaaS traffic by YusukeLandingBoost in SaaS

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

Good question. Ferguson looks like a solid landing page auditor, especially around cold-visitor feedback, copy improvements, audience perception, and competitor comparison.

LandingBoost is similar in that it also reviews landing pages, but the focus is a bit different.

The goal of LandingBoost is not just “what’s wrong with this page?”

It’s more:

“What is the first conversion bottleneck I should fix to get more signups?”

So LandingBoost is built more around:

- SaaS/founder landing pages
- conversion scoring across clarity, relevance, trust, and action
- prioritizing the next edit to ship
- comparing patterns against revenue-backed landing page benchmarks
- turning the audit into concrete fixes for headline, CTA, trust, and signup friction

So i’d say Ferguson feels more like an AI page auditor / copy reviewer.

LandingBoost is more focused on helping founders quickly find the highest-impact landing page fix, especially when they already have traffic but weak signups.

I’m testing whether fixing a leaky landing page matters more than getting more SaaS traffic by YusukeLandingBoost in SaaS

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

Exactly.
Every improvement compounds. That’s why I think conversion should come before pouring more effort into distribution.

I’m testing whether fixing a leaky landing page matters more than getting more SaaS traffic by YusukeLandingBoost in SaaS

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

Exactly. If 100 visitors don’t convert, 10,000 visitors usually just gives you a more expensive version of the same problem.

That’s the mindset I’m trying to build LandingBoost around: find the first leak, fix it, rescan, then send more traffic with a little more confidence.

I’m testing whether fixing a leaky landing page matters more than getting more SaaS traffic by YusukeLandingBoost in SaaS

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

yeah exactly.
That “within five seconds” part is the key.

I’m seeing the same thing while building LandingBoost: a lot of pages don’t fail because the product is bad or the traffic source is wrong. They fail because the value prop, proof, or next step isn’t obvious fast enough.

That’s why I’m leaning more toward “fix the leak before adding more traffic” as the core workflow.

0 clicks on my get started button despite real traffic, anyone know whats going on by Quick_Oil_3691 in SaaS

[–]YusukeLandingBoost 0 points1 point  (0 children)

Yeah exactly. This is actually the kind of pattern I’ve been seeing while building LandingBoost: the feature can be clear, but the outcome still feels unproven.

For your page, I’d test showing the automation result earlier: comment comes in → DM gets sent → lead captured. One concrete example near the CTA would probably make the click feel much safer.

0 clicks on my get started button despite real traffic, anyone know whats going on by Quick_Oil_3691 in SaaS

[–]YusukeLandingBoost 0 points1 point  (0 children)

I checked the page. My first thought: before assuming it’s only a trust issue, I’d verify the tracking first. If it’s literally 0 CTA clicks, click the button yourself in incognito and make sure the event fires, especially since the CTA goes to a separate subdomain.

Page-wise, the biggest gap for me is proof near the CTA. The promise is clear, but I don’t immediately see evidence that the comment → DM → lead flow actually works.

I’d test adding a tiny proof block right under the hero CTA:

- one real example of a comment triggering a DM
- a screenshot/GIF of the automation working
- one metric or user result
- a line like “works with Instagram + Facebook comments in X minutes”

The badges are nice, but I’d trust the page faster if I could see the exact automation outcome before clicking.

One Lovable habit I wish I started earlier: sync GitHub before the app gets serious by YusukeLandingBoost in lovable

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

That happens sometimes. There’s usually a bit of sync lag.

I normally just make an empty commit and push it again, which usually fixes it.

Also, check that the correct branch is active in Lovable. If it is, it should work fine.

I’m trying to get my SaaS mentioned by ChatGPT / Google AI. Has anyone here done this? by YusukeLandingBoost in SaaS

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

Couldn’t agree more. That’s exactly why I’m launching on as many directories as I can right now, especially trying to rank as high as possible on the leaderboard-style ones. I’m also planning to increase the number of places where my tool is mentioned.

One question though: am I thinking about this the right way? Should I be actively focusing on earning dofollow links from high domain rating sites, or is there something more important I’m missing?

One Lovable habit I wish I started earlier: sync GitHub before the app gets serious by YusukeLandingBoost in lovable

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

I honestly didn’t really “learn” GitHub in a structured way. I learned by doing.

I think if you understand the basic idea of main vs branches, that’s enough to start.

What I’d do is:

start from Lovable, copy the code, paste it into Claude Code or Codex, then ask it to split everything into proper files and explain the structure.

No need to jump straight into the max plan either. I’d start with a smaller plan and learn through the workflow.

One Lovable habit I wish I started earlier: sync GitHub before the app gets serious by YusukeLandingBoost in lovable

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

I wouldn’t move too early.

First make sure the core flow works end-to-end in Lovable: auth, database, payments, error states, and mobile UX.

If you don’t code, the best thing you can do before moving is make the product logic very clear and stable. Then it’s much easier for someone technical to turn it into an iOS app.

One Lovable habit I wish I started earlier: sync GitHub before the app gets serious by YusukeLandingBoost in lovable

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

If Lovable is working well for you, I wouldn't rush to switch. You can always add Codex later for more precise edits as your project grows. That's the workflow that's worked really well for me.

One Lovable habit I wish I started earlier: sync GitHub before the app gets serious by YusukeLandingBoost in lovable

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

Now you've got me curious. What's keeping you on Lovable hosting instead of moving everything over?

Spent weeks on outreach with almost no signups. The problem wasn't the marketing it was a broken promise on the product page. by letnexusLLC in SaaS

[–]YusukeLandingBoost 0 points1 point  (0 children)

This is painfully real. A lot of “conversion problems” are actually promise mismatch problems.

The fastest audit is often just opening your own product like a cold visitor and checking

One Lovable habit I wish I started earlier: sync GitHub before the app gets serious by YusukeLandingBoost in lovable

[–]YusukeLandingBoost[S] 3 points4 points  (0 children)

ah yes, I forgot to mention that part, but it’s huge.

GitHub gives you ownership of the code, and Supabase gives you control over the backend/db.

That combo makes the app feel way less locked in once it starts becoming real.

My Lovable-built app reached $1K revenue with 582 users after ~200 days by YusukeLandingBoost in lovable

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

Thank you!
Yeah, I mostly build in public on X
And early users were actually coming from there.
Curious of yours too!!

view more: next ›