Uptimeify

Create a website

Step-by-step: create a website and start monitoring.

Create a website

In Uptimeify, a website is the central entry point for monitoring: it ties together checks, incidents, reports, and notifications.

Where is this in the UI?

In the dashboard you can usually find it under Websites.

  • Open Websites
  • Click New website / Create website

Step 1: Basic information

Name

Choose a name that is easy to recognize for your team (e.g. “Marketing Website”, “Shop API”, “Customer Portal”).

URL (important)

The URL must include the protocol (e.g. https://example.com). A plain hostname like example.com (without https://) is not valid here.

Tips:

  • Prefer the canonical target URL (usually https://…).
  • If you want to verify HTTP→HTTPS behavior, also use the HTTPS Redirect monitor type.

Status

Depending on your setup, you can keep a website active or temporarily disable it (e.g. during migrations). A disabled website is not monitored as usual.

Step 2: Monitoring configuration

Depending on your plan, different options may be available. Typically you pick a monitoring type (e.g. “Uptime”) and configure the most important parameters.

Monitoring type

  • Uptime / HTTP(S): Standard for websites/APIs (status, response time, redirects, SSL, etc.)
  • Heartbeat: For cronjobs/backups (you get a ping URL that your job calls periodically)
  • Playwright: For end-to-end flows in a real browser (login, click paths, complex apps)

Interval & timeout

  • Check interval: How often to run checks (e.g. every 60s)
  • Timeout: How long to wait for a response (e.g. 30s)

Step 3: Add checks (optional, but recommended)

Depending on the monitoring type, you can enable additional checks, for example:

  • SSL: Validity and expiration date
  • Response Time: Performance thresholds
  • Keyword / Content Validation: Verify content is present
  • Page Size: Alert on unexpected size changes

Common pitfalls

URL vs. hostname (DNS/ICMP)

Websites require a URL with protocol (https://…). Some monitor types work with a hostname without protocol.

  • DNS Monitor: hostname without protocol (e.g. example.com) → see DNS Monitor
  • ICMP Monitor: hostname without protocol (e.g. server.example.com) → see ICMP Monitor

Authentication / bot protection

If your site uses Basic Auth, token auth, or bot protection, a simple HTTP check may fail.

  • Configure auth headers / basic auth where available.
  • For complex login flows, Playwright is often the more robust choice.

Next step