An audit measures what is measurable. It cannot tell you whether a checkout confuses people, how a layout behaves on a real phone, or what a screen reader actually announces. These do.
Every test returns a recorded walkthrough with a screenshot and the console output of each step, plus the tester's written findings. Orderable from your dashboard — or by an AI agent through the MCP server, which is the point: an agent that cannot judge something can now buy the judgement.
Fulfilled by a named practitioner rather than by whoever is free — these are sold on the reading, not on the time.
An SEO practitioner reads your Dr Urls report and returns the five fixes that matter, ranked by the impact they will actually have on this site — not by the scanner's severity label.
You receive: Five ranked fixes, each with the reason it is ranked there, the pages affected, and what to expect after fixing it. Plus what to deliberately ignore, and why.
Gauthier Bros
An SEO practitioner reads your Dr Urls report and returns the five fixes that matter, ranked by the impact they will actually have on this site — not by the scanner's severity label.
You receive: Five ranked fixes, each with the reason it is ranked there, the pages affected, and what to expect after fixing it. Plus what to deliberately ignore, and why.
Bruno Bros
An SEO practitioner reads your Dr Urls report and returns the five fixes that matter, ranked by the impact they will actually have on this site — not by the scanner's severity label.
You receive: Five ranked fixes, each with the reason it is ranked there, the pages affected, and what to expect after fixing it. Plus what to deliberately ignore, and why.
Matt MBA
You have a plan. A practitioner tells you what is wrong with it, what is busywork, and what is missing — before you spend a quarter on it.
You receive: A written review of each item: keep, drop, or change, with the reason. Plus anything absent from the plan that should be at the top of it.
Gauthier Bros
You have a plan. A practitioner tells you what is wrong with it, what is busywork, and what is missing — before you spend a quarter on it.
You receive: A written review of each item: keep, drop, or change, with the reason. Plus anything absent from the plan that should be at the top of it.
Bruno Bros
Three competitors audited against your site: what they do better, and which of it you could copy inside a week.
You receive: A side-by-side table of the four sites on the measures that matter for your category, then a short list of what is worth copying, ordered by effort.
Gauthier Bros
Three competitors audited against your site: what they do better, and which of it you could copy inside a week.
You receive: A side-by-side table of the four sites on the measures that matter for your category, then a short list of what is worth copying, ordered by effort.
Bruno Bros
Three competitors audited against your site: what they do better, and which of it you could copy inside a week.
You receive: A side-by-side table of the four sites on the measures that matter for your category, then a short list of what is worth copying, ordered by effort.
Matt MBA
Traffic fell and you do not know why. A practitioner reads Search Console alongside a fresh audit and returns the most likely cause with a way to confirm it.
You receive: The leading hypothesis, the evidence for it, at least one alternative that was considered and ruled out, and the specific check that will confirm or kill it.
Gauthier Bros
Traffic fell and you do not know why. A practitioner reads Search Console alongside a fresh audit and returns the most likely cause with a way to confirm it.
You receive: The leading hypothesis, the evidence for it, at least one alternative that was considered and ruled out, and the specific check that will confirm or kill it.
Bruno Bros
Run by any active tester with the right device.
A tester sees your page for five seconds, then writes down what the product does, who it is for, and what it costs — before looking again.
You receive: Their unprompted answers to those three questions, plus what they remembered seeing. The gap between that and your intent is the finding.
A tester loads your key pages on a throttled connection and reports what is unusable while it waits — blank screens, layout shift, silent failures.
You receive: Load timings per page, screenshots at 1s/3s/10s, and a written note on what a visitor on a poor connection would think had happened.
A tester opens your page on a real handset, works through it as a first-time visitor, and reports where they hesitated, mis-tapped or gave up.
You receive: A recorded walkthrough with a screenshot per step, the console output of each screen, and a written list of every point of friction with the step it happened on.
If you test on devices or in setups we do not cover — a screen reader you use daily, a language you speak natively, a phone nobody else has — get in touch. You publish your own offers at your own prices, and the Dr Urls extension does the recording for you.
Apply as a testerA native speaker reads your localised pages and reports translations that are wrong, unnatural, or formatted for the wrong locale.
You receive: A line-by-line list of every problem with the page and element, a suggested correction for each, and a note on dates, currencies and number formats.
You describe a bug you cannot reproduce; a tester on the matching device tries to trigger it and reports exactly what they did.
You receive: A yes/no on reproduction, the exact steps attempted, a recording of the attempt, and the device, browser and OS versions used.
A tester deliberately tries to break your forms — wrong formats, empty required fields, pasted values, back-button mid-flow — and reports what happens.
You receive: Every input tried and the resulting behaviour, screenshots of each error state, and a list of the cases where the message did not say how to fix the problem.
A tester creates a fresh account and tries to reach the product's first moment of value, reporting where a new user would stall.
You receive: Recorded run from landing page to first value, timestamps per step, and a written account of what was unclear — including anything they expected and did not find.
The same flow run on Safari, Chrome and Firefox on real machines, reporting anything that differs.
You receive: One recorded run per browser with matching screenshots, plus a written diff of every visual or behavioural difference found.
A tester completes a purchase from landing page to confirmation email, on their own device, and reports everything that broke or confused them.
You receive: The full recorded run, screenshots of each step including the confirmation, the confirmation email as received, and a written verdict on whether a normal buyer would have finished.
Someone who uses a screen reader every day navigates your key flow and reports what is unreachable, unlabelled or announced wrongly.
You receive: A written report per step: what the screen reader announced, what it should have announced, and which element is responsible. Audio recording where it helps.