How to verify AI-generated code before you merge
A review loop for checking an AI-generated patch against the original failure, hostile inputs, trust boundaries, regression tests, and deployed behavior.
SiteCMD Blog
Product updates and practical guidance for building faster, safer, more reliable websites.
Why Google isn't indexing your page
A developer's checklist for tracing an indexing problem through HTTP status, robots rules, canonicals, rendering, internal links, sitemaps, and Search Console.
All articles
13 articles
8 manual accessibility tests for every website
Test keyboard use, focus, zoom, forms, dialogs, motion, content, and screen readers with eight browser checks automated audits cannot finish.
Lighthouse vs. Core Web Vitals: why they disagree
Lighthouse is controlled lab data. CrUX reports field data from real visits. Learn why the numbers diverge and how to use both without chasing the wrong score.
Debug a Core Web Vitals regression in 30 minutes
A 30-minute workflow for separating field and lab data, finding the affected metric, tracing recent changes, and choosing a measurable fix.
Set up pre-commit hooks that actually catch bugs
A fast Lefthook setup for staged-file linting, project type checks, related tests, formatting, lockfile drift, and an intentional escape hatch.
AI-generated code audit: 7 mistakes before shipping
Audit AI-generated code for exposed secrets, swallowed errors, authorization gaps, unsafe SQL, reckless retries, and stale React effects.
Pre-launch website checklist: 12 production checks
Twelve pre-launch checks for builds, critical flows, SEO, accessibility, security, performance, monitoring, rollback, and post-deploy proof.
How to choose a tech stack for a side project
Choose a side-project stack by starting with familiarity, deployment shape, data ownership, operating cost, and a believable exit path.
How to actually test your Content Security Policy
Test whether your Content Security Policy blocks unsafe scripts, handles third parties, and reports violations without breaking the site.
How to decide which dependency updates to merge
Decide whether to merge a dependency update using security urgency, blast radius, lockfile changes, release timing, and evidence from your application.
Why most cookie banners fail before you click
A cookie banner cannot create consent after tracking has started. Audit storage and network requests, gate optional tools, and test both choices.
Why I run checks locally before CI
Fast checks belong at the developer's keyboard. CI should repeat the important ones from a clean environment and own the shared release boundary.
Get new articles by email
Occasional product updates and practical advice. No content calendar filler.
Email updates
Occasional updates. Unsubscribe any time.
✓
Check your email
We sent a confirmation link to that address. You are on the list once you press the button in that email.