Quick start: monitoring your first website

1. 1

   Create an account

   Sign up at mykavo.app with an email address and password, or with Google. A personal workspace is created for you automatically - the workspace owns your websites, your plan and your notification settings.

2. 2

   Add a website

   Enter the full URL including https://. MyKavo validates that the address resolves and is reachable, and rejects addresses that point at private or internal networks. The free plan allows one website; Pro allows eight.

3. 3

   Let MyKavo discover your pages

   MyKavo reads robots.txt, follows any sitemap declarations it finds, parses sitemap index files, and falls back to crawling internal links from the homepage. Discovery is bounded - it will not crawl your site indefinitely.

4. 4

   Choose the pages to monitor

   Select the pages that carry revenue or risk: homepage, pricing, checkout, key landing pages, the contact form. Monitoring everything is rarely useful; monitoring the pages you would be woken up for is. Free allows five monitored pages, Pro allows fifteen per website.

5. 5

   Run the baseline scan

   The first scan captures each page's screenshot, normalized DOM, visible text, SEO metadata, headings, internal links, third-party scripts and performance figures. It deliberately creates no change events - there is nothing to compare against yet.

6. 6

   Approve the baseline

   Review what was captured and approve it. That approved state becomes the reference every future scan is compared against, which is what separates MyKavo from tools that compare each check against the previous one.

7. 7

   Turn on alerts and let it run

   Email alerts are off until you enable them in Notifications - MyKavo will monitor and record changes either way, but it will not email you until you ask it to. Scans then run weekly on Free and daily on Pro, and you can run one manually at any time.

What happens after the first scan

Each scheduled scan captures the same set of measurements and compares them with the approved baseline. Anything that differs becomes a change event with a severity, a category, the previous value, the current value, and - for visual differences - a before screenshot, an after screenshot and a pixel diff.

You then do one of two things with each change. If it was expected, approve it: the new state becomes the baseline and it stops alerting. If it was not, fix the site and rescan. That loop is the entire product.

Frequently asked questions

More in getting started

• Choosing which pages to monitor
• Reading a change and deciding what to do
• All documentation