What a Signup Walkthrough Catches That a Page Audit Misses

A page audit looks at your signup screen and tells you whether the form is clear: field labels, button copy, what the password rules say. Useful, and it stops at the submit button. The breaks that cost you the most signups happen after that click, in the parts a static audit never sees: the confirmation email that lands in spam, the verification link that 404s, the empty dashboard that greets a brand new user with nothing to do.

Here is a real walkthrough of a fictional product, Ledgerly, to show the gap. Same signup, two methods. One reads the page. One walks the flow.

What the page audit reported

Point an audit at ledgerly.app/signup and it judges the page in front of it. The findings were fair:

  • The email field has no label, just placeholder text that disappears when you start typing.
  • "Create account" is clear, but the password requirements only appear in red after you submit a bad one.
  • The link to the terms of service opens in the same tab, so a careful reader loses their progress.

Three real issues. A designer can fix all three without ever creating an account. That is the ceiling of a page audit: it is honest about the screen and silent about everything the screen leads to.

Walking the actual signup, step by step

A flow walkthrough runs the named flow end to end. The reviewer (or an agent driving a browser) signs up with a fresh test inbox, clicks the button, and keeps going. Here is what the Ledgerly signup produced once someone pressed submit.

Step 1: Submit. The button showed a spinner for roughly eight seconds with no text change. A first-time user assumes it is broken and clicks again, which fired a second signup attempt. The page audit never saw this because the delay only exists in the live backend.

Step 2: The confirmation screen. "Check your email to verify." No mention of which email, no option to resend, no visible way back to the form if the address was wrong.

Step 3: The verification email. It arrived, subject line "noreply@ledgerly: action required". The from name was the raw address. The verify button linked to ledgerly.app/verify?token=..., which opened and showed "Token expired" because the email took three minutes to arrive and the token lived for two. That is the single most expensive break in the flow, and no amount of reading the signup page would have found it.

Step 4: The dashboard. After a manual re-verify, the new account landed on an empty dashboard with the heading "Your reports" and zero guidance. No sample data, no first action, no "connect your bank to begin." A new user has nothing to click.

Four findings, ranked by cost. The expired token kills signups outright. The double-submit creates duplicate accounts and support tickets. The empty dashboard quietly loses people who did make it in. None of them live on the signup page.

Why the emails matter as much as the screens

Signup is not one screen. It is a form, a confirmation state, at least one email, a link in that email, and whatever greets the user on the other side. The emails are where real signups die, and they are exactly what a page audit cannot reach. A token that expires faster than mail delivers, a verify link pointing at staging, a confirmation that never sends: these only surface when someone walks the whole path and reads the email the system actually sent.

This is the difference worth keeping straight. An onboarding feedback pass judges how welcoming the first-run experience feels. A flow walkthrough checks whether each step mechanically works and hands back the evidence. If you want your signup emails walked specifically, that is a reason to walk the emails, not just the pages.

How the review comes back

Each step becomes an item with its own screenshot: the spinner, the confirmation screen, the raw email, the expired-token page, the empty dashboard. Pins mark the exact spot that broke, and the verdict sits at the top with findings ordered by what they cost you. A developer reads it as a task list, not a vague "signup feels off."

You can run this two ways. Add Cobalt to the assistant you already use and ask in plain words, something like "Run a flow walkthrough of the signup on ledgerly.app." The agent needs a browser to drive the real flow, signs up with a temporary test inbox, and stops once for your go before it starts. See how to connect your coding agent over MCP if you have not set that up yet.

Or walk it yourself. Cobalt Capture runs in a browser tab with no install and no extension: capture each screen, pin the break, dictate or type the note, and publish a shareable review link the receiver can act on. It is free to try with no password or card. After 7 days a review goes read-only for you while the shared link keeps working; Pro is $5 a month to keep editing and exporting with no cutoff.

Point your next walkthrough at the flow that loses the most people. That is almost never the signup page itself.

Send us feedback

Stuck, or want to do something it won't let you? Tell us what you're trying to do and we'll reply by email as soon as we can. This isn't a live chat.

Powered by AcornReply