The build-gate chapter, in full. It costs an email.
Six checks, the code that runs each one, and why it exists. One PDF, by email. Ten minutes to read, and a working release gate to keep.
Six checks, one gate, and the sum of a bad deploy.
Written to be run, not admired: each check arrives as the rule, the code that enforces it, and the reason it exists.
Banned words and phrases
The vocabulary that never belongs in client copy, matched on whole words across every page of the build.
Dead internal links
Every internal link resolved against the files that were actually built, fragments included.
Duplicate search queries
Each page declares the one query it owns; two pages on the same query fail the build.
Unsourced claims
Money amounts, percentages and large figures in visible text must be registered with a source.
Legal disclaimers
The privacy and terms pages must exist, and every page must link to both.
Third-party runtime requests
The built output, CSS included, scanned for any URL that leaves the origin. The count the chapter wants is zero.
A gate, not a warning
A violation does not warn. It fails the build, and nothing goes out until it is fixed.
The arithmetic of a bad deploy
What a dead link, an unsourced figure or a tracker costs once a client has seen it, set against one failed build.
Every one of these checks ran on this page before you saw it. Open the network panel and start with the last.
The sharpest chapter goes first. On purpose.
It is the chapter most likely to change how you ship, so it is the one to judge the playbook by. Read it and decide with something in your hands, rather than on the strength of a page like this one.
Read the sharpest chapter first. It costs an email.
We’ll send the build-gate chapter in full: the checks, the code, and the reasoning. Read it. If it doesn’t change how you think about shipping client sites, you’ve lost ten minutes and kept a working release gate.
That did not send. Check the address and try again.