Web Design

Thank You Page Design: What to Put on the Page and What to Build Behind It

Most advice on thank you pages is about the second ask: a discount, a download, a follow button. That comes after the part that matters more, telling someone their form or order worked and what happens next. This guide puts the confirmation first, then one next step, then the build rules nobody lists: keeping the page out of search, counting each conversion once and announcing the message to every visitor. Sources were read on 13 November 2026.

Thank You Page Design: What to Put on the Page and What to Build Behind It

Key takeaways

  • Confirm first, sell second. Unbounce says a thank you page should give peace of mind: the visitor should be assured they have or will receive what they signed up for. Everything else comes after that.
  • Say what happens next and when. "We will reply within one working day" beats "Thanks for your message". Name who replies and from which address.
  • Offer one next step, not five. A single useful link or action keeps the page calm. More than that turns relief into a menu.
  • Keep the page out of search results. Google says a no-index rule, set by a meta tag or an HTTP header, drops a page from results, and that it only works if the page is not blocked in robots.txt.
  • Count each conversion once. Google Analytics says the transaction ID on its purchase event helps you avoid duplicate events, which is what a reload of an order page causes.
  • Announce the message to everyone. WCAG 2.2 success criterion 4.1.3 says status messages should be exposed so assistive technology can present them without moving focus.

The short answer

A good thank you page tells the visitor what just happened, what they will get and when, who to contact if it does not arrive, and then gives one useful next step. Behind the page it is kept out of search, counted once for analytics and readable by a screen reader. Whether it is a separate page or a message on the same page matters less than getting those parts right.

Who is writing: we are Amariq, a web design studio. The rules quoted come from Unbounce, Google Search Central, Google Analytics and the W3C, read on 13 November 2026.

What the current results cover, and what is missing

For "thank you page design", Google (US, English) showed on 13 November 2026 galleries (Dribbble, Mobbin, Webflow's showcase, SaaSFrame, Behance), template pages (OptimizePress, Envato, AidaForm, SeedProd), and example lists from FluentCRM (30 July 2026), Unbounce (updated 1 February 2024), HawkSEM (updated 8 January 2025) and others. Unbounce's guide, which we read in full, is the most useful. It argues the page is not the end of the transaction, and suggests telling people what to do next, inviting them to follow or subscribe, offering an event invite or a promo code, and putting a download link on the page rather than relying on email alone.

What the lists mostly leave out is the build side: where the page should not appear, how to stop double counting, what a visitor sees if they land on it directly, and how it is announced to people who cannot see it. They also lean towards the extra ask. For a small business taking quote requests, the extra ask should be the smallest part of the page.

The confirmation: five things to say

  1. What happened. "Your enquiry has been sent" or "Your order is confirmed". Plain words, near the top.
  2. A reference or copy of what they sent, where it helps: an order number, the date and time they asked for, or the project type they chose.
  3. What happens next, and when. Who will reply, from what address, and in how long. If a phone call is next, say which number it will come from.
  4. What to do if nothing arrives. A phone number or email address for urgent cases, and a note to check the spam folder if you are sending a download or receipt.
  5. A way to correct a mistake. A reply address works for most forms. For an order, link to the order page.

Here is sample wording for a quote request. It is an example, not a template to paste:

Thanks, your quote request is in. We will reply from the address on your confirmation email within one working day with questions or a price. If it is urgent, call the number below. If you do not see our email, check your spam folder.

One next step, matched to the form

FormSensible next stepSkip
Contact or quote requestRead one relevant case study or prepare a short briefNewsletter pop-up
Booking or callAdd to calendar, what to prepare, how to rescheduleA discount code
Newsletter signupLink to the best three posts, with the confirmation email noteAsking for a second form
DownloadA download link on the page, as Unbounce suggests, plus the email copyHiding the file behind another step
PurchaseOrder number, delivery information, how to reach youUpsell before they have read the receipt
DonationReceipt timing, what the gift doesA second ask on the same screen

Unbounce's examples show bigger asks: an invitation to an executive briefing, a loyalty programme sign-up, and a follow-up question that routes people to more content. Those come from companies with an established funnel and traffic to test against. For a small site, one clear link is plenty. For the form itself, see contact page design and for the donation case nonprofit website design.

Build rules behind the page

Nobody should find a thank you page from Google. Google's documentation says the rule is set with a robots meta tag or an X-Robots-Tag header, and that when Googlebot crawls the page and sees it, Google drops the page from results. It also says the rule only works if the page is not blocked by robots.txt, because a crawler that cannot fetch the page never sees the rule. So do not block thank you pages in robots.txt as a shortcut. See our robots.txt guide. Google also says it can take months for Googlebot to revisit a page, and that the URL Inspection tool shows the HTML it received.

Do not list it in your sitemap

A page you do not want in search should not be in the file that lists pages for search. Check your sitemap after you add the page.

Count each conversion once

If your analytics counts a visit to the page as a conversion, a reload or a returning visit counts again. Google Analytics' reference for the purchase event says the transaction_id parameter is required and helps you avoid duplicate events for a purchase. Use the same idea for any conversion that has an ID, such as an order number, and test it by reloading the page and checking you get one count.

Decide what a direct visit sees

Someone will open the address without submitting anything, from a bookmark or an old email. Show a short, polite page with a link to the form instead of a "your order is confirmed" message that is not true.

Make the message readable by everyone

WCAG 2.2 success criterion 4.1.3 (Status Messages, level AA) says status messages should be programmatically determinable through role or properties so assistive technology can present them without receiving focus. If your confirmation appears on the same page after a submit, announce it that way. If you send people to a new page, put the message as the first thing in the page and set the page title to say what happened. See our accessibility checklist.

Plan for failure

If the form fails to send, the visitor must see an error, with their entries kept, not a thank you. Test a failed send, as well as a good one.

Separate page or message on the same page?

Separate pageMessage on the same page
Good forTracking by address, longer next steps, tools that count page viewsShort forms, keeping people in context
Watch forNo-index, sitemap, direct visits, double countingAnnouncing the change to assistive technology, keeping the message visible
A sensible defaultOrders, bookings, downloadsShort contact forms

Neither is wrong. Pick the one your analytics and platform handle cleanly, then test both the success and failure paths. For Webflow forms specifically, see Webflow forms. For a tour request, as on a daycare website, say when you will call to confirm the time.

A thank you page checklist

  1. Says what happened in the first line.
  2. Says what happens next and when.
  3. Gives a way to reach you if it does not arrive.
  4. Offers one useful next step.
  5. Is kept out of search and out of the sitemap.
  6. Is not blocked in robots.txt.
  7. Counts a conversion once, even on reload.
  8. Shows a sensible message to a direct visit.
  9. Announces the message to screen readers.
  10. Shows an error, not a thank you, when the send fails.

Add it to your website audit checklist and to the redesign checklist so it survives the next rebuild.

How Amariq can help

We plan the confirmation step with each form, test the success and failure paths before launch and set the page up so it is counted once and kept out of search. Quotes come from the scope, never the clock, with payment of 40% to start, 30% at design approval and 30% before launch. Once the final payment is made the design, copy and code belong to you, and the domain, hosting and analytics accounts sit in your name. See our web design service.

Frequently asked questions

What should a thank you page say?

What happened, what the visitor gets and when, who to contact if it does not arrive, and one next step. Put the confirmation first.

Should a thank you page be a separate page?

Either works. A separate page helps with tracking by address and longer next steps. A message on the same page suits short forms, as long as it is announced to screen readers.

Should I add an offer to the thank you page?

A small, relevant next step is fine. A big upsell before the visitor has read their confirmation tends to feel pushy. Unbounce suggests promo codes and sign-ups, but start with the confirmation.

Should thank you pages be indexed by Google?

No. Use a robots meta tag or header that blocks indexing, and do not block the page in robots.txt, or Google cannot see the rule.

How do I stop a thank you page counting conversions twice?

Send a unique ID with the conversion where you can, as Google Analytics' purchase event does with transaction_id, and test by reloading the page.

What is a thank you page for an email signup?

A short confirmation that tells people to check their inbox, with a note about the spam folder and one link to your best content.

How long should a thank you page be?

Short. A few lines of confirmation and one next step is enough for most business sites.

Do I need a thank you page for a contact form?

You need a confirmation. It can be a separate page or a message on the same page. It must say the message was sent and when to expect a reply.

Rahat Khondokar, founder of Amariq

Rahat Khondokar

Founder & CEO, Amariq

Rahat designs and builds websites for marketing teams and ecommerce brands, and writes here about the structure, copy and conversion work behind them. More about Amariq. Find him on YouTube, Dribbble and LinkedIn.

Keep reading

Related articles.

All articles

FAQ Page Design: Real Questions, Plain Answers, Accordions Only When They Help
Web Design·15 November 2026

FAQ Page Design: Layout, Wording and Schema

FAQ page design that works: where questions come from, when to use accordions, accessible markup, and FAQ schema after 2026. Checked 15 Nov 2026.

Website Layout Examples: Which Layout Fits Which Business, and Why
Web Design·16 November 2026

Website Layout Examples by Business Type (2026)

Website layout examples by business type and page: which layout fits a service firm, shop, restaurant or portfolio, with eye-tracking data. Checked 16 Nov 2026.