Site Check

Every morning, whether your pages still load properly.

What you get

One page, waiting for you at 7. Every page you listed gets one line: whether it loaded, how long it took, and — in plain words — what went wrong if something did. Broken pages sit at the top. The ones that are fine sit at the bottom, where you can safely ignore them.

It opens each page in a real Chrome on your own computer, the same way a visitor would, and watches what happens. Along the way it picks up console errors — that's the phrase for something on the page quietly failing to run. You'd notice it as a button that does nothing, a form that never sends, a picture that never appears. You get told which of those broke, in those words. Not the error text.

Your pages, not your whole site. It checks the handful you listed and stops. It does not crawl around, follow links, or go looking for pages you didn't mention.

You choose the pages

Open pages.md in this cabinet. Each page goes on its own line, like this: - Home page — https://yourshop.com/ — a dash, the name you call the page, a long dash, then the address. The name is yours; it's what shows up in the table.

It ships with two example lines on a placeholder address. Delete them and write your own five or six: the page people land on, the page they buy from, the page they use to reach you. Until you do, the routine tells you the list is still empty rather than checking made-up pages.

What it will not do

It only looks. It never fills in a form, never clicks a button that buys, sends, deletes or submits, never signs in anywhere, and never types a password — not even to see what's behind one. A page that asks you to sign in comes back as "Unclear", and the row says so.

It also changes nothing on your website. It's a visitor, not a repair service: it tells you what's wrong, and fixing it stays with you.

How to look at it

Open the Site Check app in this cabinet. It comes pre-filled with a made-up example so you can see the shape of it straight away — the page says clearly that those pages are fake. Your first real check takes its place.

Before it can check your pages

Connect Chrome DevTools in Cabinet's integrations screen: click Connect, and that's it. There's no account, no key to paste, no sign-in, nothing to set up first — it's the easiest connection in the whole set, because the Chrome it uses is the one already on your computer.

You'll see a Chrome window open on its own each morning, load your pages one after another, and close again. That's the check happening. Leave it alone and it finishes by itself.

What's inside

• Page Checker — the one agent. Opens your pages, writes the list.
• Morning Site Check — the one routine. Runs at 07:00 every day.
• pages.md — your list of pages. The only file you have to edit.
• Site Check — the one page. Opens on today, with a dropdown for earlier days.