Is Your Thank You Page The Most Wasted Page On Your Site?

What should actually be on my thank you page?

Three things: confirmation that it worked, what happens next with a time attached, and exactly one useful next action. Most thank you pages have the first and skip the other two, which is why they feel like a dead end rather than the start of something.

This is the page someone lands on immediately after doing the thing you spent all your effort getting them to do. They are more engaged with your business at that moment than they will be again for weeks. And in my experience it is the least designed page on almost every site I audit.

If you want the mechanics of routing a submission to a page in the first place, I covered that in sending form submissions to a confirmation page. This article is about what goes on the page once they get there.

Why is this page usually empty?

Because nobody owns it. The page gets created during a build as a placeholder with the word Thanks on it, the form works, the ticket gets closed, and no designer or copywriter ever returns to it. It is not neglected on purpose. It is neglected because it is invisible in every review.

It is also invisible in most reporting. Nobody browses to a thank you page, so it never shows up in a list of your popular pages sorted by entrances, and it looks like low-traffic dead weight if you glance at sessions.

The second reason is a mental model problem. Teams treat the form submission as the finish line, so anything after it feels like extra. But the submission is the start of a relationship, and the page is the first thing you say once someone has agreed to talk to you.

Who is reading this page, and what state are they in?

Someone who has just given you something and is mildly anxious about it. They want to know the form went through, whether they need to do anything, and when they will hear from you. Until those three questions are answered they are not receptive to anything else you have to say.

They are also, briefly, in a mood to keep going. They have already crossed the hardest threshold your site has. A person who has just booked a call is far more likely to read a case study than the same person was five minutes earlier.

So the page has two jobs in sequence, and the order is not negotiable. Reassure first, then offer. Leading with an offer while the reader is still wondering whether their message arrived reads as opportunism, and it is the most common mistake on these pages.

What belongs above the fold?

Confirmation, specifics, and a timeframe. Say clearly that it worked, name what was submitted so there is no ambiguity, and tell them when a human will respond. A sentence like we will reply within one working day does more for trust than any amount of visual polish on this page.

Give them the details they might need later. Which email address you will write from, so it can be whitelisted and found in spam. What to do if they do not hear back. A reference to what they asked about, if you can render it, so the page feels like a receipt rather than a template.

Then set expectations you can keep. A promise of one hour on a page that runs at two days is worse than promising two days, because you have converted a neutral wait into a broken commitment. Under-promise here and let the reply be the pleasant surprise.

What is the one next action worth offering?

Whatever shortens the wait or improves the conversation you are about to have. My default is something that helps them prepare: the case study closest to their situation, a short page on how you work, or an honest note about pricing. All of those make the next conversation better rather than merely filling time.

Pick one. The temptation is to offer a newsletter, a webinar, three blog posts and a social follow, and the result is that nobody does any of them. This is the clearest example I know of the argument I made in how many calls to action a page should have, because here the cost of a second option is unusually high.

Choose the action by what you want to be true at the start of the next conversation. If your calls go badly because people arrive without context, give them context. If they go badly because of budget mismatch, put your pricing approach here. The thank you page is a cheap place to fix a problem that costs you real hours.

And be honest about the case where the right answer is nothing. If someone has just booked a call, adding a link may genuinely be worse than leaving the page calm. A quiet page that keeps its promise is not a failure.

What should you never put here?

Anything that undoes the trust you just earned. A popup, a survey before the confirmation, an immediate upsell, or a second form. The reader has given you something and the correct response is not to ask for more in the same breath.

Avoid vague copy too. Thanks, we will be in touch is technically confirmation and practically useless, because it answers none of the three questions the reader arrived with. If your page says only that, it is a placeholder that shipped.

And do not send people back to the homepage as the only route onward. A homepage link is a default, not a decision, and it treats someone who just converted as a stranger who needs to start over.

How do you measure whether it works?

Set the submission up as a tracked event and then measure what people do after they land, which is a different question from whether the form fired. Google Analytics changed its vocabulary here, so it is worth using the current terms.

Google's documentation states that events measuring actions important to the success of your business are now called key events, and that a conversion now refers to an important action you want to use to measure ad campaign performance and optimise bidding. That split matters when you are talking to a team that still says conversion for both things.

Google explains the reason for the change too. It says that previously, important events marked as conversions in Analytics were measured differently from Google Ads conversions, which led to discrepancies between the two. So if your Analytics and Ads numbers have never agreed, that is the documented history.

Practically, Google notes that any event you collect can become a key event, that many reports such as Landing pages and User acquisition include a Key events column, and that you can build explorations using metrics like Key events and Session key event rate. Mark your submission, then look at what the next action gets clicked. For the tagging itself I walked through the setup in tracking Webflow form conversions in GA4.

Does this need to be a separate page at all?

Not always, and the choice is worth making deliberately. An inline success message keeps someone in context and is the right answer for a newsletter signup where there is nothing further to say. A separate page is right when you have something to tell them, or when you need a real URL to measure against.

The URL is the underrated part. A real page gives you something to point a tracked event at, something to exclude from your sitemap, and something to show a client when they ask what happens after the form. An inline message gives you none of that.

My rule is that a separate page earns its place when the next action is genuinely useful. Otherwise use an inline message and do it well, because a redirect to a page that says only Thanks is a worse experience than not redirecting at all.

What should you do next?

Open your own thank you page right now and read it as a stranger. Does it confirm what happened, say when you will reply, and offer one thing worth doing? If it fails any of those three, you have twenty minutes of work in front of you and it is probably the highest return twenty minutes on your whole site.

Then check it is being measured, and check the promised timeframe is one you actually keep. A page that promises a same-day reply from a business that answers on Thursdays is doing damage rather than nothing.

If you want a second opinion on what belongs on yours, or your forms work but nothing useful happens afterwards, reach out. This is a small job with an unreasonably good return, and I enjoy doing it.