You sent your own form to see how it feels, and the page said "Thanks," or reloaded with nothing changed, or went blank. For a moment you were not sure it went through. Your visitors feel the same thing, only they cannot ask you.
The question of what to include on a thank you page after form submission starts with that moment. The page has one job first: remove the doubt.
A few plain lines can do it. They say what arrived, what happens next, when to expect a reply, and who will write back. Everything else on the page, including tracking, comes second.
Key Takeaways
Say what was received, what happens next, when a reply comes, and who will reply. A bare "Thanks" answers none of the four.
Offer a single optional action that fits the form, such as a phone line, a booking link or a short prep checklist, and keep it visibly smaller than the confirmation.
WCAG 2.2 Success Criterion 4.1.3 asks for a confirmation shown on the same page to be announced by a screen reader without moving focus.
A thank-you URL works as a key event only when it cannot be reached except after a successful send.
What should a thank-you page say after someone sends a form?
Answer four questions right away, in words the visitor would use. The GOV.UK Design System asks confirmation pages to give "details of what happens next and when" and "contact details for the service", and it recommends a reference number where one exists. Its confirmation page pattern is the clearest short standard for this.
- What was received: "We received your project inquiry."
- What happens next: "A member of our team will review it and reply by email."
- When: "You can expect a reply within one business day."
- Who will reply: "You will hear from Jordan or another member of the team."
Put together, the four parts read like this:
> Your inquiry was sent successfully. We received your message and contact details. Jordan will review your request and reply by email within one business day. If your question is urgent, call [your phone number].
Promise a reply time only if your team meets it every time. A promised day that turns into three is worse than a modest promise kept. If you send a confirmation email, say where it went and what to do if it does not show up.
Add a reference number when the inquiry needs follow-up, such as a quote request or an order question. The Office for National Statistics design system also advises against letting an informal "Thanks!" stand as the only confirmation; its confirmation page guidance lists an email confirmation and a way to save answers among the extras a page can offer.
Which next step belongs under the confirmation?
Pick one action that matches what the visitor just did, and make it smaller than the confirmation above it. The right choice depends on the form. Someone who asked a quick question needs something different from someone who asked for a consultation.
| What the visitor just did | A fitting next step |
|---|---|
| Sent a question that may be urgent | A phone number, with a note on when the line is answered |
| Is ready to choose a time | A booking link |
| Asked for a consultation | A short checklist of what to bring |
| Requested a download | A link to the file they asked for |
| May wonder whether the email arrived | Where to look, including the spam folder |
| Wants to learn more while they wait | One relevant guide, pricing explanation or case study |
For a service inquiry, a layout like this keeps the order right: confirmation first, then the optional help.
> Want to prepare for the conversation? Bring your current website address, your main business goal, and any examples you like. [Book a time]. Prefer to wait? We will contact you within one business day.
Leave out several unrelated buttons, a second form, and any offer that asks the visitor to buy right then. Nothing requires a discount, a calendar, a video or a set number of calls to action, so choose the one step that lowers the visitor's uncertainty or helps them get ready. If you are still sorting out the form itself, the contact page checklist covers what belongs around it.
How do you make the confirmation reach a screen reader?
Make the message real text, not only a green color, a check icon or an animation. Then make sure assistive technology announces it. W3C's Web Content Accessibility Guidelines 2.2 (published October 5, 2023, updated December 12, 2024) include Success Criterion 4.1.3, Status Messages. Its Understanding document says status messages must be programmatically determinable so assistive technology can present them without receiving focus, and its example is a message that a form was successfully submitted.
In practice, when the confirmation appears on the same page as the form, the message sits in an element with `role="status"`. The text might read "Your message was sent successfully. We will reply within one business day." A screen reader user stays where they are and still hears it.
When the form sends people to a dedicated page, give that page a clear title and an `h1` such as "Your message was sent successfully." Move focus to the main heading only if your page behavior calls for it. Keyboard users must be able to reach the next-step link, and if you style the message as a colored panel with a link inside, test its contrast and keyboard behavior first. The full text of the WCAG 2.2 standard is the reference for your developer.
Should the confirmation replace the form or open its own page?
Either can work. No standard requires a redirect, and no standard rules one out. What matters is that the visitor sees the confirmation and that you can tell a real submission from a page visit.
An inline message keeps people where they were and needs the status role described above. A separate page gives you a clean address such as `/thank-you/`, which makes tracking simple, but it needs the protection covered in the next section. Switching from one to the other is usually a form setting or a template edit in your web design.
If your form only reloads the same page with no visible change, that is the case to fix first. Choose inline or redirect, and make the new state say the four things from the start of this post.
How do you track the page as a lead in GA4 and Google Ads?
A thank-you page can count as a lead, and it is worth doing, but only if the page loads after a successful submission and at no other time. If someone can open the address directly, reload it, bookmark it, or land on it after an error, a page view will overcount your leads. Google's help page on key events in Google Analytics describes the setup.
In Google Analytics, the steps run like this:
- Open Admin.
- Under Data display, select Events.
- Find the confirmation event, or create one based on the thank-you URL.
- Select Mark as key event.
Menu labels can change, so confirm them in your own account before you rely on this list.
To use the event in Google Ads, link your GA4 property to your Google Ads account. Then open Goals, then Conversions, then Summary, choose + New conversion action, select Import, pick Google Analytics 4 properties, choose Web, and select the event. Google says that linking accounts or marking an event as a key event can take 24 to 48 hours before import options appear, and the Google Ads help page on importing Google Analytics events covers the rest.
A confirmation page that exists only to be counted should usually carry a `noindex` directive, as Google Search Central explains in its guide to blocking Search indexing. The fuller setup is in the guide to tracking contact form leads in Google Analytics.
How can you test the whole path in ten minutes?
You do not need a developer to find out whether the page works. You need a private browser window, a test address your staff would recognize, and a notepad. Never use a real customer's personal details for the test.
Work through three checks in order: what the visitor sees, what arrives in your inboxes, and what your tracking records. Write down what you see, because the exact wording is the thing you will edit.
What does the visitor see?
Submit the form from the private window and note whether the button changes state when you press it. Then record whether an inline message or a new address appears, and copy the exact confirmation wording. Check that it says what was received, gives a reply time you can keep, and offers one useful next step.
Refresh the page and watch whether the form sends again or creates a duplicate entry. Then open the page on a phone and tap every link.
What lands in your inbox?
Look for the confirmation email if you promised one, and for the notification your team receives. A thank-you page on screen does not prove that the business email arrived, so check the inbox, CRM or notification channel itself. If the visitor sees success but nothing reaches you, the problem sits in delivery, and the steps in why a contact form stops sending emails apply.
Does tracking record it?
Open GA4 Reports > Realtime while you submit and look for the event. Google's help page on monitoring events in DebugView shows how to see each event as it fires, under Admin > Data display > DebugView. For a quick check that your tag is collecting data at all, use Google's guide to confirming that you're collecting data.
Do not run test after test against a live primary conversion without excluding or documenting your test traffic. Otherwise your lead count will include you.
When is a small fix enough, and when is a bigger project worth it?
The test often points to a small repair. Rewriting the message is a copy change. A reply promise that does not match your staff's habits is solved by changing the promise or the habit. The table sizes the usual jobs.
| What the test showed | What fixing it involves |
|---|---|
| Vague or missing confirmation | Rewrite the heading and body in the template; usually small |
| Page reloads with no visible change | Add an inline success state, or a redirect that fires only after a successful send; small to medium |
| Reply promise does not match practice | Replace it with the real standard and set a routing rule; small |
| Too many next actions | Keep the one that fits the form; small |
| Confirmation page shows up in search | Add `noindex` and confirm Google can still read the page; small |
| No GA4 event, or the wrong one | Check the tag, trigger, consent behavior and event name; small if the tag exists, larger with conflicting setups |
| Leads counted that never happened | Stop direct visits from counting, use a reliable success event, retest refresh; medium |
| Notification never reaches the business | Inspect the recipient, spam filtering, mail authentication and CRM link; a settings fix or a mail investigation |
| Screen reader gets no announcement | Add status semantics, headings and keyboard access; small for a simple form, larger for a custom one |
A larger project makes sense when the test shows a problem that crosses systems: notifications that arrive unreliably, tracking that conflicts, a broken CRM handoff, or a form that cannot tell a success from an error. Until then, fix the smallest thing the test found.
Is your thank-you page doing its job?
Pick an answer to begin.
1. A visitor submits your form and sees only "Thanks!" What is missing?
2. Your confirmation appears on the same page as the form. What helps a screen reader user hear it?
3. When can a thank-you page address count as a lead in GA4?
Frequently Asked Questions About Thank-You Pages
What should a thank-you page say after a form submission?
Confirm what was received, explain the next step, state a reply time you can meet, and give one contact method or one relevant optional link.
Should a thank-you page include a phone number?
Include one when urgent questions are likely or when your team answers calls. Say when the line is answered.
Should I add a booking link?
Add one when visitors are likely to be ready to schedule. Keep it optional and make sure it matches the form they just sent.
Does a thank-you page track a conversion automatically?
No. Tracking needs an event or tag that is set up correctly, and it needs a test. Mark the event as a key event in GA4, then import it into Google Ads if you run ads.
Should the thank-you page be indexed?
Usually add `noindex` when the page exists only to confirm a submission and has no search purpose of its own.
How should screen readers receive the confirmation?
Use real text in a status message that assistive technology can announce without moving focus, such as an element with `role="status"` on the same page.
What This Means for You
A good confirmation answers four questions: what arrived, what happens next, when a reply comes, and who will send it. One optional next step sits under it, a status message carries it to screen readers, and tracking counts a lead only after a real submission. Each part is small on its own.
Run the ten-minute test once and keep your notes. They show you whether you need new wording, a form setting, or a closer look at email delivery and tracking. Visitors who know the form worked are less likely to send it twice, and your team knows what it promised.
If the test shows more than a wording fix, Web Leveling can look at the whole path from form to inbox to GA4 with you, and our conversion rate optimization work fixes only the parts that fail. If the page needs only new words, you can do that yourself today. We work with small and medium businesses across the country and overseas. Send us what your test turned up, and we will tell you which fix it calls for.
Terms
Thank-you page words in this post
Tap a term to see what it means.
Confirmation page. The page or message a visitor sees after a form is sent, telling them it worked.
Status message. A short message that assistive technology announces without moving the user's focus, as WCAG 2.2 Success Criterion 4.1.3 describes.
Key event. An action GA4 is set to count as important, such as a completed lead form.
DebugView. A GA4 report that shows events as they fire, used to test tracking.
Reference number. A short code given to the visitor so a follow-up can be matched to their inquiry.
noindex. A directive that asks Google not to show a page in search results.
