Waitlist landing page: what to put on it so launch day has an audience
A waitlist page needs a one-line promise, who it's for, what joining gets them and a form that works, plus the tags that let it rank and share early.
LLaunchScaler·Published ·8 min read
A waitlist landing page needs five things: a one-sentence promise of what the product does, who it is for, what people get by joining, a single email field, and a confirmation that tells them what happens next. It also has to be indexable and shareable from the first day, with a real title, a meta description and an Open Graph image, because people who hear about you will search your name and paste your link.
The rest of this guide covers each section, the confirmation email, the technical basics, and the launch-day email you should write before you need it.
What should a waitlist landing page include?
Keep it to one screen of content that answers what the product is, who it is for and why someone should give you an email address now. Everything else, from the feature grid to the team section, can wait for the launch page. A visitor should be able to decide in about the time it takes to read two sentences.
Section
What to write
Example
Headline
What it does, in plain words
"Turn support tickets into a searchable help center"
Subhead
Who it is for and the result
"For SaaS teams with under 20 people who answer the same question every day"
What joining gets you
A concrete reason to join now
"Early access in November, and your help center imported free"
Questions, answered
What people ask about this
01
What should a waitlist landing page include?
A one-sentence promise of what the product does, who it is for, what people get by joining, a single email field, and a confirmation that says what happens next and when. Add a title, a meta description and an Open Graph image so the page can be found and shared.
"One email when we launch, one a month before that"
Who is building it
Your name and a link to where you post
"Built by Ana, posting progress on X"
Showing the real product also answers the question launch platforms ask later: does this exist yet? Show HN, for one, turns away landing pages for things people can't try.
How do you write the one-sentence promise?
Name the job the product does and the person it does it for, with no adjective a competitor could also claim. "The all-in-one platform for modern teams" fits thousands of products. "Send invoices from Stripe payments without leaving Slack" fits one, and a reader knows at once whether it's for them.
Three rewrites show the pattern:
Before: "AI-powered productivity, reimagined." After: "Summarize every Zoom call into action items in your Linear backlog."
Before: "The future of team feedback." After: "Anonymous weekly check-ins for remote teams, answered in two minutes."
Before: "Supercharge your SEO." After: "Find the pages on your site Google stopped indexing, and why."
Test it by reading the headline to someone outside your field and asking them to repeat it back. If they can't say what the product does, rewrite it. The same sentence will become your launch tagline, so the work pays twice.
What should people get for joining the waitlist?
Give them a specific reason to join now rather than later. Early access, a launch-day discount, a free setup or a say in the roadmap all work, as long as you state it plainly and deliver it. "Get notified" is not a reason; they could simply come back.
Say how many emails they'll get and when. A line like "one email when we launch, and a short update each month until then" lowers the cost of signing up, and a reader who expected your email has no reason to report it.
If you promise early access, decide now how you'll grant it: a date, a batch size, or an invite link in the launch email. A promise you can't keep on launch day turns your warmest audience into your first complaints.
Should a waitlist use double opt-in?
Yes, in most cases. Mailchimp describes double opt-in as "an extra confirmation step that checks each email address," where "the confirmation email contains a unique URL that your potential subscriber must click before we can add them to your audience." The list you email on launch day then holds only addresses that work and people who chose to be there.
That matters most on launch day, when you send one email to everyone at once. Google's sender guidelines for Gmail require every sender to set up SPF or DKIM and to keep the spam rate reported in Postmaster Tools below 0.3%. Senders of more than 5,000 messages a day to Gmail must also set up DMARC, and their marketing messages must support one-click unsubscribe. Addresses with typos bounce, and people who don't remember signing up report you, both on the one day you most need the inbox.
Write the confirmation email to set expectations, not to sell:
Subject: "Confirm your spot on the [product] waitlist."
One line on what they signed up for.
The confirm button.
When they'll hear from you next, and how often.
One optional ask: "Reply and tell me what you'd use it for." The replies become your first customer interviews.
Set up SPF, DKIM and DMARC on the sending domain before the first confirmation goes out. The guide to SPF, DKIM and DMARC records has the exact DNS entries.
How do you make a waitlist page indexable before launch?
Remove any noindex, give the page a descriptive <title> and meta description, and put Open Graph tags in the server HTML. Google says that when it finds noindex, it "will drop that page entirely from Google Search results," and a template or a staging setup can leave one behind without anyone noticing.
The page will mostly rank for your product name, which is exactly what people type after seeing you mentioned. Google's title guidance asks for a title on every page that is "descriptive and concise," and warns against vague ones like "Home." Its snippet guidance says there is "no limit on how long a meta description can be," but snippets are truncated to fit the device, so put the promise first.
Use this set of tags on the page:
<title>Acme: turn support tickets into a searchable help center</title>
<meta name="description" content="Acme imports your support tickets and builds a help center from the answers. Join the waitlist for early access in November.">
<link rel="canonical" href="https://acme.example/">
<meta property="og:title" content="Acme: turn support tickets into a help center">
<meta property="og:type" content="website">
<meta property="og:url" content="https://acme.example/">
<meta property="og:image" content="https://acme.example/og.png">
The Open Graph protocol requires og:title, og:type, og:image and og:url on every page. For the image, Meta recommends at least 1200 x 630 pixels and an aspect ratio close to 1.91:1, and it rejects files over 8 MB. Check the header too: run curl -sI https://yourdomain.com/ and confirm no X-Robots-Tag: noindex line appears. If shares show the wrong card, the guide to an OG image that isn't showing covers the fixes.
Give the page a few paragraphs of real text below the form: the problem, how the product solves it and who it is for. A page that is a headline and a form gives search engines and AI crawlers almost nothing to describe.
How do you check that the waitlist form actually submits?
Submit it yourself on the live domain, from a phone and a laptop, and confirm the address reaches your email tool and the confirmation email arrives. Forms break silently: an embed blocked by a content-security policy, an API key that only works on localhost, or a button whose handler was removed in a redesign.
Run these tests after every deploy that touches the page:
Submit a real address you haven't used before. Confirm it appears in your email tool, marked as pending if you use double opt-in.
Open the confirmation email on Gmail and Outlook, click the link, and confirm the contact changes to subscribed.
Submit an invalid address such as name@ and check that the form says what's wrong before submitting, instead of failing silently.
Submit the same address twice and check you don't create a duplicate or show an error page.
Try it with a common ad blocker switched on, in case it blocks your form provider's script.
Check the success state. The visitor should see what happens next, not a blank form.
The dead CTA button test covers how to catch a button that looks fine and does nothing.
What should the launch-day email to your waitlist say?
Write it now, before launch week, and keep it to one link and one ask. The people on your list chose to hear from you, so the email only has to tell them it's live, give them what you promised, and ask for one thing. A long email on launch morning gets skimmed.
A structure that works:
Subject: "[Product] is live, and your early access is ready."
One sentence on what launched.
What they were promised, delivered: the invite link, the discount code or the import offer.
One link to the product, tagged with utm_source=waitlist&utm_medium=email&utm_campaign=launch. Google Analytics recommends always setting those three parameters.
One ask. If you're on a launch platform that day, ask people to visit and comment. Several platforms, Product Hunt and Hacker News among them, forbid asking for upvotes.
Your name and a reply address that a person reads.
Send a test to yourself on two providers, check the links, and schedule it for the morning of your main launch. The SaaS launch strategy guide shows where this email sits in the wider launch week, and building in public before launch covers how to grow the list that receives it.
Check the page before you send people to it
Before you post the waitlist link anywhere, run the free scan on LaunchScaler with the page's URL and no account. It runs 156 checks across 6 of its 7 categories at no cost, including a missing or boilerplate title, a missing meta description, a noindex on a page you want ranked, thin content, a form with no working submit path, a form endpoint that errors on valid input, and a call to action that is a dead control. Fix what it flags, then submit the form once more yourself on the live domain.
Usually yes. Double opt-in sends a confirmation email with a link the person must click before they are added, so the list holds only real, reachable addresses when you send the launch email.
03
Can a waitlist page rank on Google before launch?
Yes, if it is indexable: no noindex, a descriptive title and meta description, and enough text to say what the product is. It will mostly rank for your product name, which is what people search after hearing about you.
04
What should the confirmation email say?
Thank the person, restate what they signed up for, say when they will hear from you next and how often, and give one small thing to do meanwhile, such as replying with their use case.
05
When should I send the launch-day email to my waitlist?
On the morning of your main launch, with one link and one ask. Write it before launch week and send a test to yourself on Gmail and Outlook first.
A listing that gets clicks has a one-liner for the job, a description of problem, method and audience, highlights with numbers, and a price stated plainly.
Launch traffic drops because every launch board resets daily. What keeps a product found after that: indexed pages elsewhere, reviews and your own content.
