SEO for Thank-You and Confirmation Pages
This is the one page-type guide where the goal isn't to get the page found. It's to keep it out of search while making it the backbone of your conversion tracking.
Founder, Vazagency · Runs reputation recovery and SEO campaigns for businesses across 35+ industries.
Every other guide in this series is about making a page rank better. This one is different, and that difference trips people up constantly: a thank-you or confirmation page — the page someone lands on right after submitting a contact form, requesting a quote, or completing a booking — generally should not appear in search results at all. But it's also frequently the single most important page on the entire site for measuring whether marketing is working. Those two facts aren't in tension. They're two different jobs, and getting both right just means using the right tool for each.
Job one: keep it out of search results (noindex)
A thank-you page has no standalone value to someone arriving from a search result. It says "thanks, we got your message" — useful context immediately after submitting a form, meaningless and confusing to a stranger who lands on it cold from Google. Worse, if it does get indexed and starts appearing in results, people can click through to it directly without ever filling out the form it's meant to confirm.
That last scenario is the real problem, and it's more common than it sounds — thank-you page URLs get shared, bookmarked, cached, or occasionally just crawled and indexed by default because nobody told search engines not to. Once that happens, the page starts pulling in direct search visits from people who never actually converted, which quietly corrupts the very data the page is meant to help you collect.
- Add a
noindexmeta robots tag (or the equivalent header for non-HTML resources) to the thank-you page's<head>. - Don't rely on robots.txt alone to accomplish this — robots.txt and noindex do different jobs, and robots.txt disallow can actually prevent search engines from seeing the noindex tag at all.
- Leave the page fully reachable to real visitors — noindex only affects search result listings, not whether the page loads normally for someone who lands on it through the actual form flow.
- Exclude the URL from the XML sitemap, since including a noindexed page in the sitemap sends a mixed signal.
Worth knowing
Job two: make it the trigger for your conversion tracking
Here's the part that gets confused most often: noindexing a page and using it for conversion tracking are not related settings, and they don't interfere with each other. Noindex is a signal to search engines about search result listings. Conversion tracking is a completely separate mechanism — typically a tracking tag, pixel, or event that fires when the thank-you page loads, telling your analytics platform "a form submission just happened." A page can be noindexed and still fire a conversion event every single time someone lands on it. In fact, that's exactly the setup almost every service business should be running.
Why the thank-you page is the right conversion trigger
Using the page load itself as the trigger, rather than a click on the "submit" button, is more reliable in practice — it only fires after the form has actually been processed and the visitor has actually been redirected, which filters out failed submissions, JavaScript errors, and abandoned attempts. If your analytics or ad platform is set up to count a click on "Submit" as a conversion, you're likely counting some submissions that never actually completed successfully. A distinct, dedicated thank-you URL fixes that. For the setup itself, see how to set up conversion tracking.
A common mistake: one generic thank-you page for every form
If a site has multiple conversion points — a contact form, a quote request, a newsletter signup, a booking form — and they all redirect to the same generic thank-you page, conversion tracking loses the ability to tell those actions apart. A single vague "conversion" event tells you something happened, not what. Wherever practical, use a distinct thank-you URL per form (/quote-thank-you, /contact-thank-you, /booking-confirmed) so each conversion type can be tracked, reported, and valued separately — which matters a lot if a quote request and a newsletter signup shouldn't count the same in your reporting.
What the page should actually contain
Since it won't be found through search, the content requirements are lighter than any other page type in this series — but it shouldn't be a dead end either.
- A clear confirmation that the submission was received, and what happens next (e.g., "we'll call you within one business day").
- A phone number, for anyone who wants to speak to someone immediately rather than wait for a callback.
- A soft next step — a link back to the homepage, a relevant guide, or recent project photos — rather than leaving the visitor stranded on a page with nowhere to go.
- No navigation-heavy distractions competing with the confirmation message itself; this isn't the place for a full site menu, similar to the logic behind stripping navigation from a dedicated landing page.
The short version
Noindex the page so it never shows up in search and never pulls in visitors who haven't actually converted. Use its page load as the trigger for conversion tracking so your data reflects real, successfully completed submissions. Those two decisions aren't in conflict — they're the correct configuration for a page whose entire purpose is confirming an action, not attracting one.
Frequently asked questions
If thank-you pages should be noindexed, why do they matter for SEO at all?
Does noindexing the thank-you page hurt the site's overall SEO?
Can I still use the thank-you page for conversion tracking if it's noindexed?
What's the difference between noindex and just password-protecting or hiding the page?
Should the thank-you page redirect automatically, or should the visitor click through?
More guides
Want this handled for you?
We build the SEO foundation and handle the ongoing work — no long-term contract, no guaranteed-rankings sales pitch.