The Post-Click Experience: Don't Break the Promise

A click is a small act of trust. The visitor read some words on a button, formed an expectation of what would happen next, and committed. It’s a tiny transaction, over in a fraction of a second, but it has the structure of every larger transaction: a promise, an act of faith, and then a moment of truth when the visitor finds out whether the promise was kept.

Most conversion advice is about the promise. Make the button say the right thing, put it in the right place, make it the right color. Fine. But I’ve come to believe the moment of truth matters more, and it’s the part almost nobody designs. What happens after the click is usually assembled from whatever pages already existed, by whoever wired the link, and nobody ever walks the path end to end pretending not to know where it leads.

The failures are mundane, which is why they survive. A button says “See pricing” and lands on a contact form; the visitor asked a question and got a counter-question. A button says “Start free trial” and lands on a page whose headline is the company’s mission statement; the visitor was mid-motion and the page changed the subject. An ad promises a specific feature and the landing page is the generic homepage, where the visitor is expected to re-find, on their own, the thing they already clicked on. None of these are broken in the technical sense. Every link resolves, every page loads. But each one breaks a promise, and the visitor feels it even if they couldn’t name it. What they feel is a small lurch, the sensation of a stair that isn’t where your foot expected it. Two or three of those and they’re gone, and your analytics will record it as a mysterious drop-off between two perfectly good pages.

The principle that fixes this is old and simple: the first thing the visitor sees after clicking should confirm the words they clicked. Advertisers call this message match, but it’s really just conversational manners. If someone asks “how much does it cost?” you answer with a number, not with “let me tell you about our founding story.” The button text is the visitor’s side of a conversation. The next page is yours. Read them as a dialogue and the breaks become audible. “Get the report.” “Welcome to our platform!” That’s not an answer; that’s a subject change. “Book a demo.” “First, create an account.” That’s not an answer either; that’s a toll booth that appeared after the visitor was already committed to the road.

The subtlest version of the broken promise is escalation. The button promised something small and the page demands something large. “Learn more” that leads straight into a form asking for a phone number has escalated from browsing to being sold to, and the visitor never agreed to that. Momentum is real, and it’s directional: a visitor moving through small kept promises will keep going, sometimes surprisingly far. A visitor who hits one escalation stops and re-evaluates everything, including the promises already kept. The rule of thumb I use is that the page after a click may ask for at most one step more commitment than the click implied. Anything steeper reads as bait.

What makes all this hard to catch is that no single page is at fault. Audit each page in isolation and each one looks fine; the homepage is a good homepage, the form is a reasonable form. The defect lives in the seam between them, in the relationship between the promise on page one and the delivery on page two. Teams don’t review seams. Ownership is by page, so the seams belong to no one. This is one of the reasons I built GazeSite to look at pages the way an arriving stranger does rather than the way an owner does: the owner’s knowledge of where every link goes makes the broken promises literally invisible to them. You cannot feel the missing stair if you already know it’s missing.

The most instructive place to watch for this is the paths that begin off-site, because there the promise was made somewhere you don’t control the context. A search result promised whatever your page title says. A shared link promised whatever the sender said about it. Payment flows are the extreme case: the visitor leaves your site, hands over money on a checkout page you don’t fully control, and returns carrying the biggest promise of the whole funnel. If the page they return to is confused about who they are or what just happened, you’ve broken the promise at the exact moment the visitor paid to have it kept. I’ve made a version of this mistake myself, with a checkout that returned buyers to a page that treated them as strangers, and what struck me afterward was how invisible it had been from the inside. Every component worked. Only the seam was broken, and only a paying customer could reach the seam.

The audit for all of this costs nothing but humility. Take every button and link on your site and write down, in plain words, what it promises. Then click it and write down what the next page actually delivers in its first screen, before any scrolling. Where the two sentences don’t match, you’ve found a leak, and the fix is usually an afternoon of rewriting a headline or rerouting a link, not a redesign. It’s unglamorous work. But conversion is mostly the accumulation of kept promises, and a site that keeps every small promise earns the right to ask for the big one.

The click is where the visitor extends trust. The next page is where you decide what to do with it.