About
I build the tools agencies use to manage the web, and write about how that’s changing.
What I’ve built
Dyno Mapper is my longer-running platform: a visual sitemap, content inventory, and accessibility auditing tool I started in 2014. It now powers a public API with 75 endpoints across 9 modules and serves agencies, universities, and enterprise teams running everything from small client sites to multi-thousand-page enterprise platforms.
IATO is the newer one. It’s an AI-powered SEO and web crawling platform built around a simple thesis: the next generation of SEO tooling shouldn’t be human-callable software with an AI bolt-on. It should be agent-callable infrastructure that humans and AI tools can both work through. IATO ships visual sitemaps, automated audits, MCP-native tooling, and a free WordPress plugin that lets any AI assistant read and update WordPress and Elementor sites safely.
Across both products, I’ve worked with 2,500+ clients spanning SaaS, B2B, government, and higher education. That’s given me a useful view of what actually breaks at scale, and what doesn’t.
SEO, AI agents, and what it takes to govern the web at scale. That’s most of what I write about. If any of that sounds interesting, the writing is here, and there’s a free monthly-ish newsletter if you’d rather it come to you.
Background
15 years building for the web
I’ve been building site crawling and SEO tooling since before “agentic” was a word people used in product copy. Long enough to have watched the same problems return in new forms a few times, and long enough to have opinions about which of those problems are actually solved by AI and which aren’t.
What I think about
Four threads I keep pulling on
Agentic SEO
What changes when the next visitor to your site is a research agent, not a human? What does it mean for a site to be agent-readable, and how do agencies need to think about this before it’s the default?
Trust as infrastructure
Autonomous tools that touch real client sites need a real trust layer: audit trails, dry-runs, rollback, scoped permissions. Most “AI agents for X” tools skip this and pay for it later.
Tooling for agencies
How agencies running 30 or 300 client sites can use AI without losing the editorial control that’s the whole reason their clients hired them.
Web governance at scale
What does it actually take to keep a 10,000-page site organized, accessible, and searchable? Notes from 12 years of crawling enterprise, government, and university sites, and what changes when AI agents are the next set of users to worry about.