See the Monitoring as Code quickstart guide if you want to start creating your monitoring as code with the CLI.
This guide will walk you through creating your first Browser Check with Checkly. Browser Checks are perfect for monitoring realistic user flows within your application or services. If you are looking for monitoring general availability, check out the Uptime Monitor Quickstart.
  • A Checkly account (sign up at checklyhq.com)
  • The URL of a website you want to monitor
1

Create a Browser Check

Light mode interface
  • Choose “Browser Check” for comprehensive website monitoring
  • Enter your webssite URL (e.g., https://your-website.com)
  • Click “Create Check”
2

Edit Your Test Script

The following test script will check if the homepage is available, performing correctly, and looks visually correct.
Light mode interface
3

Configure Check Settings

Configure your check settings by clicking the “Settings” button in the top right corner of the check editor
Light mode interface
For your first check, the default settings work well. You can always adjust them later.
4

Choose Scheduling Frequency and Locations

Light mode interface
5

Set Up Alerts

Configure who gets notified when issues are detected:
Light mode interface
6

Test and Save

Before activating your check:
  1. Click “Test Check” to run it once and verify it works
  2. Review the results to ensure your website loads correctly
  3. Check for any errors in the console or network tabs
  4. Click “Save and Activate” to start continuous monitoring
7

View Results

Once your check is active:
Light mode interface
  1. Visit your dashboard to see real-time results
  2. Check the results page for detailed performance metrics
  3. Review screenshots and timing information
  4. Set up additional checks for other critical pages

​
Next Steps

Now that you have your first check running:
  • Add API Checks: Monitor your backend services and APIs
  • Create Check Groups: Organize related checks together
  • Set up Status Pages: Share uptime information with users
  • Explore Integrations: Connect with Slack, PagerDuty, or other tools

​
Upgrading to Monitoring as Code

As your monitoring needs grow, consider upgrading to our CLI approach:
  • Version Control: Keep your monitoring configuration in Git
  • Team Collaboration: Review changes through pull requests
  • CI/CD Integration: Deploy monitoring alongside your applications
  • Advanced Scripting: Write custom Playwright tests for complex flows
Ready to make the switch? Check out the Monitoring as Code tab above!