The ThreeSeven Standard

How fast your site loads and responds on a phone, on a real-world connection, not in a demo. Google calls these measurements Core Web Vitals, and they directly affect both your rankings and how many visitors stay long enough to become enquiries.

Most visitors abandon a page that takes more than three seconds to load. The usual culprits are oversized images and bloated page-builder code: invisible to the owner, obvious to every prospect on a phone.

Whether every visitor can actually use your site: read the text, navigate the pages, and complete your forms, including people with low vision, older visitors, and anyone who can’t use a mouse.

Common failures are low-contrast text, unlabeled form fields, and missing image descriptions. Each one turns away real customers, and accessibility requirements are increasingly written into law. The current benchmark is WCAG 2.2.

Zero detected errors is a measurement, not a certification. Automated scanners reliably catch contrast, missing labels, and broken heading structure, which is roughly a third of what actually matters. They can’t tell you whether an image description is meaningful or whether a form can be completed with a keyboard. So I scan, and then I go through the site by keyboard before launch. You should know which part of that number came from a machine.

Whether Google sees complete, correct information about every page: titles, descriptions, a submitted sitemap, and properly sized images. When these are missing, Google writes its own listing for you, often badly, and your click-through suffers.

I set up Google Search Console on your domain, submit your sitemap, and confirm your pages are actually being indexed. Every quarter I check coverage again for pages that dropped out or started throwing errors. It’s the difference between assuming Google can read your site and knowing it can. This is the unglamorous plumbing of being found. It’s also the layer most sites lose first as pages get added over the years without anyone checking.

Search Console is the one tool here that needs access to your Google account. I set it up when you join, and from then on this pillar is measured exactly as described above. A free report comes before that, so it checks your sitemap and the common causes of indexing problems instead.

Whether AI search tools, from ChatGPT to whatever comes next, can actually read your site: reach it, parse it, and identify who you are, what you do, and where you operate.

Three things stop them, and most site owners have never checked any of them. Your robots.txt may be blocking AI crawlers outright, often added by a plugin nobody remembers installing. Your content may only exist after JavaScript runs, which some tools never wait for. And your structured data may be missing, invalid, or describing something different from what is on the page, which is worse than having none.

This pillar does not promise an AI will recommend you. Nobody can promise that honestly, and the published research on whether structured data increases AI citations is genuinely mixed. What I verify is that nothing on your site is stopping an AI from reading it. That is the part within anyone’s control, so that is the part I hold.