01
Name the first promise
Write the one claim, offer, or outcome visible before the first call to action. Keep it beside your notes while you review the rest of the route.
Free self-guided field guide
Eight checks for one public launch path.
Review one public path yourself—no signup, login, form submission, or purchase required. Use the guide before a launch, campaign handoff, or client review to separate a reproducible observation from a design preference.
Public pages only. This is not a free audit, automated scan, certification, or promise that every issue will be found.
Name the routeOne public starting URL and one intended visitor action.
Use two viewportsOne ordinary desktop width and one narrow mobile width.
Write evidenceObserved behavior, reproduction steps, and owner questions stay separate.
The checklist
Follow the path a new visitor can actually see.
Do not enter fields or submit forms. Stop when the route needs authentication, a purchase, private data, or a production change.
02
Follow the primary click
Open the call to action a new visitor is most likely to use. Record each public page, redirect, decision, and dead end without entering or submitting information.
03
Match the destination
Check whether the public destination still supports the promise that prompted the click. Record what is visible; do not infer intent.
04
Check the return path
Confirm that navigation, labels, and ordinary back-links let a visitor understand where they are and recover from a wrong turn.
05
Read the trust pages
Review visible pricing, privacy, service-scope, and contact links for consistency with the public offer. This is not legal or compliance advice.
06
Repeat at a narrow width
Check the same route in a mobile-sized browser. Look for clipped headings, horizontal overflow, hidden calls to action, and controls that become hard to distinguish.
07
Separate fact from preference
Write what happened, where, and how to reproduce it. Put subjective ideas in a separate owner-question list rather than calling them defects.
08
Choose one next change
Prioritize the smallest change that addresses a reproduced route problem. Keep redesign, analytics, code work, and private-flow testing in a separate scope.
Finding note
Make each observation easy to reproduce.
- Route and viewport
- Public URL, desktop or mobile width, date, and local time.
- Expected visible behavior
- The action or destination a visitor could reasonably infer from the public copy.
- Observed behavior
- What appeared, in neutral language, with short reproduction steps.
- Next decision
- A bounded change to consider, or an owner question when the evidence is not conclusive.
Stop conditions
Public observation has a useful edge.
Stop before accessDo not log in, create an account, enter fields, submit a form, make a purchase, or access non-public information.
Stop before security workDo not probe, scan, bypass, exploit, or test authorization boundaries.
Stop before changing productionDo not edit a live site, contact users, or implement a recommendation without separate written authority.
Need a second set of eyes?
Request a written scope for the $350 audit.
Introductory fixed fee for the first three clients. One agreed public path, up to five public pages, desktop and mobile observation, and up to ten prioritized findings. Two-business-day delivery target after written scope confirmation and receipt of the agreed public URL and target action.
Request a written scope for the $350 auditPlease send only public URLs and visible-path context. Do not send credentials, customer data, payment details, or non-public information. An inquiry is not an order, reservation, subscription, or payment.
Service boundary
The paid audit is not a conversion, legal, privacy, accessibility, performance, SEO, security, or compliance certification. No revenue, ranking, conversion, defect-free, or launch outcome is promised.
Privacy boundary
This page has no account, payment form, analytics pixel, or web intake form. Its email link opens the visitor’s own mail client.