Most readers didn't open the sign-in page because the home page convinced them. They opened it because four smaller pages, in a specific order, quietly earned enough trust to make a free account feel worth the friction. We pulled two months of scroll-depth and path data from our newest cohort and the sequence below is the one that kept showing up — including the page we'd long assumed was a dead end.
Page one is /about. We expected bounces. We got the opposite. Readers who landed here scrolled past the founder photo, lingered on the mission paragraph, and clicked through to either pricing or a feature page roughly 38% of the time. The page isn't persuasive because of what it says. It's persuasive because it answers the "who is this, really" question before any feature has to do that work.
Page two is almost always a feature page, not a pricing page. That's the first surprise. Readers want to know what the product does before they want to know what it costs. The feature page that wins is the one with a short demo loop or a concrete example — the longer the page, the shallower the scroll midpoint and the lower the click-through to sign-in.
Page three is where the path forks. About two thirds of readers hit a pricing or comparison page next. The other third skip straight to a use-case or story page. Both groups convert, but the comparison-page readers sign up faster on average, while the story-page readers churn less in week one. The implication isn't "pick one." It's "offer both, and let the reader self-select."
Page four is the quiet closer. For most readers, it's a FAQ, a documentation entry, or a security/trust page — not a hard CTA. The pages that move the needle here are the ones that answer a small, specific worry: "can I export my data," "is my history saved," "what happens if I cancel." Once that worry is named and resolved, the next click is the sign-in button.
The lesson isn't the order. It's the texture. Every page in the sequence does one job, and only one job. None of them try to be the sign-in page. By the time the reader actually clicks sign in, they've already decided — and your job on that page is just to not get in the way.
If you want to map this path on your own site, start with one question: which page, on your domain, is doing two jobs at once? Fix that one first, and the rest of the funnel usually loosens on its own.