Three ways to work with Faculty

When someone asks ChatGPT, Claude, or Perplexity to recommend a business like yours, do you come up? For most sites the answer is no — not because the work is bad, but because the site isn’t legible to the tools doing the answering.

I find exactly why you’re invisible — the structured-data gaps, the content these tools can’t parse, the questions you should be the answer to and aren’t — and give you a specific, written plan to fix it: the exact changes, with examples, ready to implement. Not a promised ranking; anyone who promises that is guessing. What you’re buying is the diagnosis of what’s actually wrong and a clear path to correcting it. This very page is an example of the work — clean, machine-readable, built to be found.

Code gets written fast now — and a lot of it ships before anyone asks how it handles input, sessions, or authentication. I read your application the way an attacker would: I find what puts you at risk, prioritize it plainly, and the high-risk issues get fixed.

My curiosity led me to web security at its most formative moment — the years when many of the standards the field still relies on were set, a number of them mine. I introduced the CSRF token, and wrote one of the early books on securing web applications. This isn’t a scan run through a tool and handed back; it’s a senior read of your real application, by someone a lot of the field learned this from.