Is This Website Built With Lovable? How to Tell
Prompt-to-app builder that generates React front ends with Supabase back ends.
Paste the URL into the analyzer and the Overview card shows a “Built with Lovable” badge when the page matches, alongside the full tech stack, SEO audit and performance scores.
What Lovable is
Lovable turns a chat prompt into a working web app: a React and Vite front end styled with Tailwind, usually paired with a Supabase database and auth. Projects publish to a *.lovable.app subdomain by default, and many founders ship their MVP or landing page straight from it before moving to a custom domain.
Signals the analyzer checks for Lovable
The detector searches the page HTML for any of these strings. One match reports the builder with high confidence.
lovable.applovable.devgenerator" content="lovable
How to check it yourself
- Open the page, press Ctrl+U (Cmd+Option+U on a Mac) to view the source, then use Ctrl+F to search it. Search for "lovable.app" or "lovable.dev". Generated projects often keep a default Open Graph image hosted on lovable.dev even after a custom domain is attached.
- Look at the <meta name="generator"> tag near the top of the head. Lovable projects that have not edited index.html declare Lovable there.
- Check the published URL. A site served from a *.lovable.app address was deployed from Lovable.
- In DevTools, open the Network tab and reload. A single large JavaScript bundle under /assets/ with hashed names and a Supabase API host (supabase.co) in the requests is the usual Lovable stack.
What Lovable sites usually show in an audit
- The page is rendered entirely in the browser. Crawlers that do not run JavaScript see an empty root element, so titles, descriptions and headings should be verified in a prerendered or server-rendered form if search traffic matters.
- Default metadata is common: a title such as the project name, a placeholder description and the Lovable Open Graph image. Those appear in the analyzer's SEO section as missing or generic tags.
- Supabase keys are embedded in the client bundle by design. That is normal for the anon key, but any service key in the bundle is a security finding.
- Image weight and unused JavaScript are the usual performance flags, since generated components ship with every dependency the prompt pulled in.
These are tendencies from audits, not rules. Run the analyzer on the site in question, then use the fix guides for anything it flags, or compare it with a competitor.