Build log · 13 March 2026
Why we started Dr Urls
Written up in November 2026 from our engineering log · 2 min read
Dr Urls started with a frustration most people who run a website share: audit tools are very good at telling you that something is wrong, and very bad at telling you what to do on Monday morning.
A score is not a task
A typical report ends with a number and a long list. The number is hard to act on, and the list mixes a missing meta description on one page with a broken template on four hundred. Somebody still has to turn it into work.
The first commit set the direction: crawl the site, check every page across SEO, performance, security and accessibility, and present every problem with the exact fix — ranked so the first thing on the list is the thing worth doing first.
Written for people and for agents
From the start the output had two readers. A person needs to understand why something matters. A coding agent needs a precise, structured task it can apply. Most of what came later — the MCP server, the VS Code extension, the task files — grew out of taking that second reader seriously.