About

Measuring what machines can actually read

A growing share of the traffic arriving at any website is not a person with a browser. It is a retrieval system fetching a page to answer someone's question, and unlike a human reader, it either parses the page or it does not. MachineRead exists to tell site owners which side of that line they are on.

What the audit does

The Essentials audit runs 13 check groups across 56 checked points, covering off-site presence, AI access and scrapability, and search discovery. It reports a separate strict agent-readiness score because a good SEO result can hide a fatal fetch failure. Nine advanced rows are listed but locked at zero, so the report shows what is not being measured instead of quietly leaving it out.

What it refuses to claim

The audit does not measure search ranking, traffic, backlinks, conversion, or model citation share. It measures the public signals that constrain retrieval, not the outcomes downstream of retrieval. Keeping that boundary is what makes the rest of the report trustworthy. The methodology documents every check and its weight.

Who builds it

MachineRead is built and operated by George Jieh. It runs on a deliberately small stack: a FastAPI backend, a static frontend on Cloudflare Pages, and no paid API calls during a free audit. That constraint is a design parameter, and it is why Essentials can stay free to run.

Where it is going

The locked rows require paid crawling and verification, so the Starter and Pro tiers that unlock them will involve accounts and payment. Accounts will be OAuth only, so no passwords are ever stored, and payment will run through Stripe and Link. There is no tracking today and there will be none later, on any tier. See pricing for the current status.

Questions, bug reports, or partnership inquiries: [email protected].