How Bernard checks your site — and what he does about it
Most website tools hand you a hundred warnings and wish you luck. Bernard works the other way round: he watches your site, tells you the handful of things that actually matter, fixes them when you say so — and then proves the fix worked.
What gets checked
Every time you publish, Bernard re-reads your live site and runs four checks:
- Broken links — a link on your site pointing at a page that doesn't exist. Visitors hit a dead end; Google notices too.
- Page details — every page should have its own title and description, because that's what Google shows in search results. Missing or duplicated ones make pages easy to skip.
- Structured data — the behind-the-scenes description that tells search engines what your business offers. If it's broken or incomplete, Google can't read it.
- Speed and usability — Google's own independent test (the same one behind your Lighthouse score) grades how fast and usable your pages are on a phone.
What you'll see
Problems appear on your site's page under Things you can improve, grouped in plain English — "People are being sent to a missing page", "Missing page details" — with the heaviest first. Each one explains why a real visitor would care, keeps the technical detail one click away, and carries two buttons:
- Fix this — Bernard prepares the change on a draft. You see a preview; nothing goes live until you approve it.
- Dismiss — not everything is worth doing. Dismissed items stay quietly out of the way.
Bernard checks his own work
After a fix goes live, the same check runs again. A genuine win shows as ✓ Fixed, with the proof. If the checker still flags the problem, Bernard says so honestly — "Published — though Google's checker still flags this one" — and offers another pass. There are no quiet ticks.
The story, kept
Open What's happened under any item and you'll see its whole story: when Bernard spotted it, when you asked for it to be sorted, when the change went live, and what the re-check found. A few weeks after a fix, Bernard adds the final chapter from real Google data — how often the page was shown, and how many people came.
That last part is the point. Anyone can generate a to-do list; Bernard keeps the receipts.
The prompt
“Check my site for problems, list the most important ones in plain words, and wait for me to choose what to fix.”
The [bracketed] parts are yours to fill in. First time? Connect bernard to your AI over MCP — a one-time setup in bernard → your site → Use your own AI — then paste the prompt above.
Questions people ask
- What exactly does Bernard check?
- Four things. Links that point at missing pages, so visitors never hit a dead end. Page details — the titles and descriptions Google shows in search results. Structured data — the behind-the-scenes description that tells search engines what your business offers. And Google's own speed and usability test, which grades how fast and usable your pages are on a phone.
- When do the checks run?
- Every time you publish, Bernard re-reads the live site and re-runs the checks — so the list is always about the site as it is now, not as it was. Google's speed test is also re-measured after publishes, and once a week Bernard gathers results for fixes that have had time to bed in.
- Will I get buried in warnings?
- No. Bernard only lists problems worth acting on, grouped in plain English — things like "People are being sent to a missing page" — with the heaviest first. Anything he can't explain in a sentence, with evidence, stays off your list.
- What happens when I press Fix this?
- Bernard prepares the change on a draft and shows you a preview. Nothing goes live until you approve it. If you'd rather not deal with something, Dismiss tucks it away and it won't nag you again.
- How do I know a fix actually worked?
- Bernard checks his own work. After a fix goes live, the same check runs again: a genuine win shows as Fixed with the proof, and if the problem is still there, Bernard says so honestly and offers another pass — no quiet ticks.
- What is "What's happened" under each item?
- Every item keeps its own story: when Bernard spotted it, when you asked for it to be sorted, when the change was prepared, when it went live, and what the re-check found. A few weeks after a fix, Bernard adds what it earned — how often Google showed the page and how many people came.