Your first check

Start with one address

Paste your project URL into the first look. I ask for the page response and domain signals there; it is not a browser visit. Create your account to keep the result and open the project. I then prepare suggested checks in the background. A suggestion is a starting point, not a saved result or an incident.

You can open the project while I prepare those suggestions. If setup is still working, come back to its progress from the project. If it says it stopped, use the retry offered there. You can also make a check yourself; an empty check list while setup runs does not mean the project has been checked.

Record a safe public path

In the project, choose to add a check and open the browser. For a shop, start with its public catalog: load the home page, follow a link to the catalog, then mark words you expect to see on that page while recording. Finish recording and give the check a name you will recognise. You do not need to create an order or an account on the shop to make this first check.

Replay it in a clean browser to see whether those steps work without your current session. A replay proves this draft can work; it is not a stored check run. If you save without a replay, I queue a first run right away; a check that passed its clean replay follows its daily or deploy schedule. The saved result appears in the project and run history once that run finishes, with evidence you can open. An incident is a separate state reached only after the same check fails twice in a row. See how alerts work.

When you need domain ownership

A read-only path through public pages can run without proving ownership. Checks that fill forms or read email wait until you verify the project's domain in Project controls. A path that continues to a second site outside that domain cannot run even after verification. You can keep the public catalog check while deciding whether to verify the protected path; the public path does not need your DNS or a file on your site.