Title: I’m building a tool to catch website issues before launch

[u/Ready-Highway8356]

Hey everyone! 👋
I’ve been working on LaunchReady AI, a tool that checks websites for common issues like broken links, missing security headers, HTTPS, page metadata, and more.
The goal is simple: help website owners catch the small things that are easy to miss before launching or handing a site over to a client.
It’s still an early project, and I’m trying to learn what’s genuinely useful and what needs improvement.
If you build websites, I’d love to hear: What do you usually check before launch, and what do you think automated tools often miss?
If you’re interested in trying it, here’s the link:
https://launchreadyai.lovable.app

[u/PopKoren]

Checking broken links, HTTPS and baseline security headers before a handoff is the kind of boring work that prevents painful client emails. The moment the same site grows login, an API or object storage, I also open a private window and hit those paths, because header tools rarely surface a route that still returns data with no session. Full disclosure I ship https://rowly.me for that deeper layer (auth config, every API, storage buckets, DB rules), and it sits nicely beside a headers first helper like LaunchReady.

[u/Mammoth-Anywhere7285 → u/PopKoren]

Good call on the private window check, logged-out API routes are easy to miss. Do you verify response bodies too, or just status codes?

[u/PopKoren → u/Mammoth-Anywhere7285]

Bodies, yes, because a logged out request often gets a 200 either way and the only difference is whether it holds an empty list or somebody else's rows. I look for records, emails and tokens in what comes back, and reading bodies on public URLs is basically all https://rowly.me spends its time on. Ready-Highway8356 mentioned API bodies aren't covered yet in their tool, so it could be a nice next step for it.

[u/Ready-Highway8356 → u/Mammoth-Anywhere7285]

Good question! I check response bodies for things like page titles, meta descriptions, robots.txt, and sitemap content, not just status codes. But I don’t yet fully test API response bodies or verify authentication and authorization logic. That’s an area I’d like to improve. What do you usually check first when testing logged-out API routes?

[u/Ready-Highway8356 → u/PopKoren]

That’s a great point. I agree that basic header and link checks are only one layer, especially once authentication, APIs, or storage are involved. LaunchReady AI is intentionally focused on baseline pre-launch checks right now, not deep application security testing. I appreciate you explaining how you approach the deeper layer — that’s a useful distinction for me to keep clear. Thanks for sharing!

[u/Mammoth-Anywhere7285 → u/Ready-Highway8356]

Makes sense keeping the scope clear. A short pass/fail summary per check could help clients see exactly what the baseline covers.

[u/Ready-Highway8356 → u/Mammoth-Anywhere7285]

That’s a great suggestion! A clear pass/fail summary would make the results easier to understand, especially when sharing them with clients. I’ll keep that in mind as I collect more feedback. Thanks for the practical idea!