Next step · What to do next

Get an alert when my site goes down

What you may see

I want to know before customers tell me

Why this step

Sites fail quietly at night; a simple check every few minutes tells you within minutes instead of days.

Before you start

Which pages must never be down (home, order, payment return)?

The prompt for this step

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

Any error or warning you see now

What you have now (tool, framework, where it is hosted)

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a senior engineer and careful product advisor who builds small business websites and apps, and explains every step to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

WHAT I WANT NEXT
Get an alert when my site goes down

ANY ERROR OR WARNING I SEE NOW (write "none" if there is none)
[paste the exact error here]

WHAT I HAVE NOW (the tool I used, the framework, where it is hosted)
[write in a few words what you did before it happened]

WHY THIS STEP
Sites fail quietly at night; a simple check every few minutes tells you within minutes instead of days.

DO THESE STEPS, IN THIS ORDER
1. Recommend a simple uptime monitor with a free or low-cost tier (tell me to check the current plan), and list the 3 to 5 addresses to watch.
2. Add a small health address that checks the database connection and returns a short answer without private data.
3. Set alerts to two channels (email and a phone message) and to two people, and describe what to do first when an alert arrives.
4. Also watch domain and certificate expiry dates.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- I receive a test alert on both channels, and the health address answers quickly.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not expose private information in the health answer.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

Recommend a simple uptime monitor with a free or low-cost tier (tell me to check the current plan), and list the 3 to 5 addresses to watch.
Add a small health address that checks the database connection and returns a short answer without private data.
Set alerts to two channels (email and a phone message) and to two people, and describe what to do first when an alert arrives.
Also watch domain and certificate expiry dates.

Do not do this

Do not monitor with a check that always says OK.
Do not expose private information in the health answer.

Try another entry