LaunchCheck

Do you check og:image beyond the homepage? We hit a case where the site-wide default image was fine on the homepage, but pages that defined their own Open Graph block quietly lost it, because the framework replaces that object instead of merging it. Sampling a few inner URLs from the sitemap and comparing their og:image with the homepage would have caught that for us.

The robots.txt tester is a nice touch — "blocked by robots.txt" is exactly the kind of thing you only notice weeks after launch. Do you also check whether the sitemap lists the same URLs as the canonical tags? On a site I run, a mismatch there kept a new page out of Google longer than it should have.

The 100-point score split into technical, search and conversion checks makes it easy to see what to fix first. Since it scans the public homepage, how does it handle pages from Lovable or Bolt that only render content after JavaScript runs? A small label on findings that are rendering-related would help builders know where to look.

A 100-point score split across technical, search, and conversion checks is a smart framing for AI-built sites that look fine locally but fail quietly in production. The copy-ready fixes are especially useful if you are iterating inside Cursor or Bolt and just want to paste a patch back in. Do the conversion checks look at things like CTA clarity and form friction on the homepage, or are they mostly technical signals dressed as conversion?

Copy-ready fixes are the right call, most checkers just give you a red score and leave you alone with it. Does LaunchCheck also look at multilingual sites? My own project runs in German, English, French and Italian, and getting hreflang and the language versions right was the part that took me the longest.

The split between technical, search and conversion checks is the right framing - most pre-launch audits stop at meta tags. Two things I'd find valuable from my own site work: a check for canonical/hreflang consistency on localized sites (a canonical pointing at the wrong locale quietly cost us weeks of indexing), and treating 308 redirects as first-class alongside 301 - several AI builders default to 308 for domain redirects and some SEO tools still misreport them.

Pairing a free robots.txt tester with the 100-point launch score is a practical way to catch indexing problems early. Does the scan also flag a missing or empty sitemap.xml, or noindex tags left over from the AI builder? Those two are common on freshly generated sites.

The copy-ready fixes are what make this useful for people on the marketing side who are not developers. Do the conversion checks also look at whether a visitor has a clear next step from the homepage, like a visible contact path, booking link or chat? A site can pass every SEO check and still leave visitors with no obvious way to reach the business.

Nice focus on AI-built sites. One check that would help Lovable and Bolt builds: many ship as client-side apps, so the raw homepage HTML is almost empty until JavaScript runs. Flagging when the title, meta description and main text only appear after JS loads, and suggesting prerendering, would catch a really common indexing gap.

The 14 days of rescans could be especially useful during the last round of fixes. Do rescans show a before/after diff with the date each finding was resolved or reintroduced? That would make it easier to distinguish real progress from a score change caused by one new homepage edit.

This looks really solid. I'm curious about the technical stack behind it—did you build this natively or use a web wrapper? Also, how does it handle performance on older machines? Nice work!

Scanning only the public homepage keeps the free check quick, but a lot of Lovable and Bolt sites put most of their content on inner routes. Does the $19 Launch Pack extend the scan to the pages listed in the sitemap, or does it stay on the homepage and rescan it over the 14 days?

Copy-ready fixes are the right focus — a score alone does not help someone who is not a developer. Since you scan only the public homepage, how do you handle a site where the real conversion problem is on a pricing or signup page that is not the homepage? Is there a way to point the check at a second URL?

The robots.txt tester would be even more useful if it showed AI crawlers next to Googlebot (GPTBot, ClaudeBot, PerplexityBot). Some AI-builder templates block a few of them by accident, and AI answers are now a real traffic source. Do you also check Open Graph tags? A missing og:image is the first thing people notice when they share a new launch on LinkedIn or X.