Dead clicks, rage clicks, SEO crawler drift, mobile breakage, real-user LCP. Built specifically for the failure modes of AI-generated sites. Install in one prompt.
Every signal mapped to a documented Lovable failure mode. Sources cited from independent research, CVEs, and community threads.
Lovable defaults to client-side React. When Googlebot hits your site, it sees an empty HTML shell — your content lives in JavaScript that Google may or may not render. Onely's controlled study found Google takes 9× longer to crawl JS than HTML. Harvv detects when crawler traffic lands but bounces because the rendered DOM is empty.
When you re-prompt Lovable to add or change something, the AI often rewrites adjacent React components and severs state bindings. Buttons stop firing handlers. Forms lose their submit logic. Users keep clicking — Harvv catches it as dead clicks and rage clicks within the first hour of a regression.
Lovable optimizes for the desktop preview canvas. Touch targets under 44×44 px, iOS Safari fixed-position jumping, viewport overflow — all common in Lovable-generated mobile experiences. Harvv ships dedicated mobile-UI signals (edge proximity, container starvation, tap-target sizing, readability) that flag these before you lose mobile conversions.
An independent audit of 50 Lovable apps found 89 percent had Supabase Row-Level Security disabled or misconfigured on at least one table. The Wiz Research vibe-coding study found 1 in 5 organizations affected. Harvv does not patch security, but our SEO + crawler audit surfaces when bot traffic is hitting exposed admin paths so you can lock them down.
We scanned 100+ Lovable.app sites with our pixel and synthesized the findings against verified CVE data, Wiz Research, and primary-source community accounts. Read the complete teardown.
Read the research →Lovable's dashboard tracks build status, credit usage, and deploy events — not user behavior on the live site. Once your project is on a custom domain or even a lovable.app subdomain with real visitors, you need a pixel that captures dead clicks, rage clicks, scroll depth, and SEO crawler drift. Harvv is the production-traffic layer Lovable does not provide.
Yes. We give you a single prompt to paste into your Lovable chat. The Lovable AI agent reads it, edits your index.html, and adds the Harvv pixel. Takes about 30 seconds. See /install/lovable for the full flow.
The four documented Lovable failure modes: (1) SEO invisibility from client-side rendering — we detect when Googlebot is served an empty React shell; (2) Mobile breakage — touch targets under 44 px, iOS Safari viewport jumps; (3) Reactivity drift — buttons that silently stop working after an AI regenerates a component; (4) Conversion friction — forms with field-level abandonment, missing trust signals, slow LCP.
Yes. The pixel sits in your frontend and tracks user behavior independently of your backend. Whether your data is in Supabase, Lovable Cloud, or your own Postgres, the pixel only sees the user interactions in the browser. We do not touch your backend.
GA tells you traffic came and bounced. Hotjar gives you session recordings (heavyweight, expensive, requires manual review). Harvv automatically detects the patterns — dead clicks, rage clicks, SEO drift, mobile breakage — and tells you what is wrong, with a fix. Built specifically for AI-generated sites where the failure modes are predictable.
Free tier: 1 site, 50,000 events per month. Pro: $29/month for 3 sites + 500,000 events/site/month. Both tiers get every detector (dead clicks, rage clicks, mobile breakage, SEO drift, LCP, INP, form abandonment). No credit card required for free tier.
One prompt. Paste into your Lovable chat. Pixel live in under a minute. Free forever for solo builders.