pafcore.site

Watch (Pro)

Watch is for pages you own. You prove the domain, save pages, schedule checks, and get alerts when the score moves the wrong way.

Open it at pafcore.site/pro. Sign in with the same email link as the rest of PafCore.

What you get

Plan What Watch does
Free (signed in) Create projects and pages (up to 20 pages). Prove domains. Prepare for schedules.
Pro $19/mo Schedules under fair use, alerts, history from watched runs, 60 credits each month for lab checks.

Fair use (Pro)

Watch scheduled runs do not spend credits. Caps keep the queue fair:

Cap Limit
Saved pages 20 across projects
Active schedules 10
Hourly schedules 3 (other schedules use daily)

Lab actions (Would this change help?, find file, smaller image, paste ready code) still spend from the 60 monthly credits, or from a credit pack.

You can open Watch before buying Pro. Signed out visitors see Free vs Pro. Signed in Free users can set up projects and domain proof. Schedules and alerts unlock after Pro.

Get Pro from the Watch sidebar when you are on the free plan.

Flow

  1. Create a project in the left rail. History, alerts, and schedules always follow the project you have selected.
  2. Add pages you care about. Not only the home page. Pricing, checkout, a blog post, or any public https://… address works. Cap is 20 pages across all projects.
  3. Prove the domain (Domains in the rail, or Prove on a page). One proof covers that host. Required before schedules.
  4. Start a schedule on the Schedules tab (Pro). You pick one saved page from the selected project.
  5. Add alerts on the Alerts tab (email and/or https webhook). Rules apply to every watched page in that project.
  6. Read history on the History tab after watched scans run. Filter by page when a project has more than one.

Domain proof

Before a hostname can be scheduled, you must prove you control it. Either method works.

In Watch, open Domains and follow the four steps on the page.

DNS TXT

  • Host field at most registrars (Namecheap, Cloudflare): _pafcore only
  • Full name that must resolve: _pafcore.yourdomain.com
  • Value: pafcore-site-verification=<token>

File

  • URL: https://yourdomain.com/.well-known/pafcore-site-verification.txt
  • Body: the token only

Press Check after you publish the record or file. DNS can take a few minutes.

Remove a domain

Use Remove on a domain row. Pages in your projects stay. Any schedules on that host are deleted, because watches cannot run without proof. You can prove the domain again later and create new schedules.

Schedules

Use the Schedules tab in Watch. Pick a page, how often (daily or hourly), and phone or desktop.

Needs:

  • Pro plan
  • Domain proven for that page’s host
  • Cron enabled on the server (hourly tick)

You can also create schedules with the API. The website is the normal path.

Real visitors

Under the lab chart, Watch shows what Google recorded from real Chrome visitors to that site: largest content paint, tap response, and layout shift.

Each one is graded Good, Needs work, or Poor on Google's own thresholds, so it agrees with what you see in Search Console.

If Google has no data for your site, the panel stays hidden and the note says so. That is normal for a site without much traffic. Your lab numbers still work.

Lab and real visitors are two different things, and the sentence under the panel says how far apart they are on your page.

Alerts

Threshold (score or lab metric below a limit) or regression (score dropped by N points). Delivery is email, an https webhook, or both.

Each rule in the list says what it watches in plain words, and whether the last alert reached you.

Check an alert works

Press Send test on any rule. It sends a real message down the same path a real alert takes, so a typo in a webhook URL or a mail that lands in spam shows up now instead of during a real drop.

The message says it is a test and names what that rule watches. Nothing about your site changes, and a test never quiets a real alert.

If a channel fails, the line under the rule says which one and why, for example Webhook failed: webhook answered 404. Fix it and send another test.

Tests are limited to a few an hour per account.

If a webhook fails

PafCore tries a webhook twice when the far end times out, rate limits, or returns a server error. It does not retry a 404 or a 401, because sending the same request again would change nothing.

Webhook URLs must be https and must resolve to a public address. Redirects are never followed.

Share reports

Public report links still open the full homepage report (/?scan=…) with share and download. Plain / Technical stakeholder view: /share?scan=….

Next