What you get when a page stops working

• Subject: for example “[Heedza] Checkout broken on your-app.lovable.app”.
• What happened: one sentence, for example “The payment page opened, but the ‘Subscribe’ button was missing.”
• The app and its address.
• A button that opens the check in your dashboard.
• The fix to paste into your AI tool, ready to copy.
• A picture of the page that failed, attached to the email.
• On Pro and Business, with GitHub connected: for some problems, a Fix it for me button at the top, with Or fix it yourself and the prompt below it. See how Fix it for me works.

You get one alert per failure. While the same check is still failing, Heedza doesn’t send it again.

• Email alerts: every plan
• Slack, Telegram and webhook alerts: paid plans

When you add an app, you pick the tool you made it with. The fix is written for the tool you pick: Lovable, ChatGPT (including Codex), Claude, Cursor, Bolt, Replit, v0, GitHub Copilot, Gemini, Windsurf or Base44 (11 tools), or any other AI tool. For Lovable, Bolt, Replit, v0 and Base44, it also includes steps for that tool’s settings.

Each fix says which page failed, what was missing, and asks the tool to make a small change without redesigning the page. Fixes for payment pages tell the tool not to enter a card or make a charge.

You paste the prompt into your tool, check the change, and publish. Or, on Pro and Business, for some problems you press Fix it for me and approve the fix Heedza opens on GitHub. Heedza doesn’t change your app unless you approve a fix.

You are editing this Lovable project. Change only what is required to fix the failure below. Do not redesign the page.

Heedza found that the payment page on https://your-app.lovable.app is broken.

What happened: The payment page opened, but the “Subscribe” button was missing.

What to do:
- Restore the checkout page so a visitor can see the payment form. Keep the pay button from charging anything during a test.
- Keep the existing URL if you can, so the saved check still finds it.
- The check stops before payment. Do not submit a card, do not click Pay, and do not create a charge while you verify the fix.

After the change, load the page in a browser and confirm the failure above is gone.

Every time we check your site, we look at it from the outside, like a visitor, and tell you in plain words when something is exposed or changes. Every alert comes with the exact fix to paste into your AI tool.

• A new outside script on your homepage. The alert has two buttons: It was me (the address joins your known list and we stop asking about it) and Get a fix prompt (a ready-made prompt for your AI tool, to find and remove it).
• An exposed file, an unexpected redirect, or a dropped security setting. Each alert has a fix prompt, written for the AI tool you chose.
• Google’s list flags your site as potentially unsafe. Shown only to you, in your dashboard and alert. It says what Google says, links to Google’s advisory and has a fix prompt. We do not find this ourselves.

On Pro and Business, with GitHub connected, some alerts have a Fix it for me button. Nothing starts until you press it. Heedza then opens the fix on GitHub, and nothing changes until you approve it. It works only for some problems: a page Heedza checks that stopped working, a file that should not be public, and a security setting your site stopped sending. For other problems, and on other plans, the fix prompt is a prompt you paste into your AI tool. Your AI tool makes the change, and you should check it before you publish. How Fix it for me works.