Chris Lacey
Your site can look fine in a browser and still hand them nothing. I check what yours sends and show you how to check it yourself.
01 Findings
A blank page
One homepage looked fine in a browser. AI tools that don't run JavaScript got 0 characters of text, so its prices, clients, and case studies never reached them.
Blocked
Two sites' hosting turned away Claude's crawler, so Claude couldn't read them at all. Their own crawler rules said Claude was welcome. The check: 403 means turned away, 200 means let in.
A leftover page
One site gave search engines a list of its pages with just two entries. The second was the sample page WordPress makes on install.
02 Services
A
Three pages on what search engines and AI assistants can and can't read on your site, in priority order. Each finding comes with a check you can run yourself.
It also works as a re-check after your web vendor makes changes. I can't promise rankings or a spot in AI answers. I can show you what's in the way.
83-point checklist
B
Full-stack builds for products with a model in the middle: retrieval, agents, evaluation, and the interface people use.
My own is Fulcra, a live advising platform that answers by naming and citing frameworks from a curated set of 177.
Fulcra · 177 frameworks · live
03 Process
Lacey Software is me, Chris Lacey. I've spent over 6 years building React and TypeScript software for pharma, healthcare, and telecom clients.
Every finding in a review comes with something you can check yourself. If I can't back a finding up, I cut it before the report goes out.
On my own time I built Civic Mirror, which writes up local government meetings for residents, and Night Shift at Mother Bear's, a Halloween browser game for a local pizza place.