Audit a shop website twice with a local agent and Claude

Nazoor Ahmed had a local 27B agent and a Claude sub-agent audit the same shop site from one brief. Claude found 28 of 32 fixes in 40 minutes; the local agent took 14 hours but caught a launch blocker Claude missed.

Done withCustom agent· Nov 20, 2026

What they did

Before launching a 20-product shop site that their local agent had built, Nazoor Ahmed ran two independent UX and SEO audits from the same brief: every page at phone and desktop width in light and dark mode, every visitor flow, a dark-mode verdict, an SEO review, before-and-after screenshots for each top issue, and no changes to site files. One audit was their own agent engine running a local 27B model with browser tools, overnight. The other was Claude, which handed the brief to an expert sub-agent with its own browser. Claude then acted as referee, confirming each finding in code or the browser and merging both reports.

How it went

Claude's auditor took about 40 minutes and found 28 of the 32 merged fixes and 4 of 5 launch blockers, including a placeholder order phone number and a wrong price on larger sizes. The local agent took about 14 hours, 475 model calls and 430 tool actions, found 12 fixes, but caught a price filter that emptied the shop, which Claude missed. Its review loop stalled for 45 minutes on proving no file changed, and two of its screenshot pairs showed nothing.

Worth knowing

The local agent is thorough and literal: it tests what it is told and misses what a person would notice fast. Checks that only confirm a file exists do not prove a screenshot shows the fix. The audit ran on a copy of the site so the no-changes rule could be verified by comparing folders.

Try it

With Custom agent· 1 part to fill in

Audit [my website URL or local copy] before launch without changing any site file. Check every page at phone and desktop width, in light and dark mode, and try every visitor flow, including every option of every filter and every search box. Also review SEO on each page. For each top issue, capture a screenshot of the problem and one with the fix previewed in the browser. Confirm each finding in the code or browser before listing it. Produce a priority list and stop there for me to choose which fixes to make.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related