Landing pages & email
Test the lead magnet journey before you share it.
Two downloads and no replies, and no way to tell whether the resource, the page or the audience was the problem. You cannot test your way to a good idea, but you can remove the failures a reader would meet before anyone else does.
The page went live, a few people downloaded the file, and nobody replied. You cannot tell whether the resource was thin, the page asked for too much or you promoted it to the wrong people, so every fix is a guess. Before promoting again, walk the journey a reader actually walks: the promise on the page, the file behind it, the request, the screen that follows, the delivery email, the links and the unsubscribe. Record what you expected and what happened, repair the largest gap, retest, then decide whether to release or hold.
It is functional testing. It will not tell you whether the idea is good, and it promises nothing about inbox placement or sales. It finds ordinary failures: a page promising a table the file does not contain, a link to last week's version, a next screen that says the file is ready when nothing opens.
What a launch test can and cannot tell you
Sort your questions first, so the test is not asked to answer one it cannot.
| Question | What the test gives you |
|---|---|
| Does the file keep the page's promise? | A yes or no. Read the page, then look for each named item in the file. |
| Was the request recorded once? | A yes or no. Submit, press the button again, compare. |
| Does the next screen give the right instruction? | A yes or no, and whether it matches the route the form describes. |
| Does the delivery email reach the current file? | A yes or no, opened signed out on a device that has never seen your email. |
| Will the email land in the inbox? | Nothing. Placement depends on mailbox providers and sending reputation, so check arrival, not placement. |
| Is it compliant and accessible? | Nothing. These are functional checks, not a legal, privacy or accessibility audit; ask a qualified adviser for that. |
A scope list for functional testing. No campaign, download figure or result is measured here.
A pass removes the mechanics you would otherwise worry about. It says nothing about whether readers want the file.
Walk the journey in the order a reader meets it
Six stages, one pass condition each. Work in order, because a failure early in the list hides the ones behind it.
| Stage | What you do | What counts as a pass |
|---|---|---|
| 1. The page promise | Read the headline, contents list and button, first on a phone. Then open the file. | Every item named on the page exists in the file under the same name. |
| 2. The request | Submit the form with an address you control, then press the button twice more. | One record arrives, with the page it came from, and no duplicate. |
| 3. The next screen | Read the screen immediately after you submit. | It matches the route the form promised, confirmation first or immediate, and says where to start. |
| 4. The delivery email | Open the email signed out, on a phone and on a desktop. | It arrives, the subject matches what the form said, and the link opens the current version. |
| 5. The email choices | Compare the sentence under the form with the messages that actually arrive. | The sentence is accurate, and every email has an unsubscribe link that works without a login. |
| 6. The links | Click every link on the page and in the email: help, privacy, the file, your site. | Each one resolves to the page you meant, not a draft or a placeholder. |
The checks described here. The free Launch Check Workbook expands them into seven and adds a symptom-to-repair table.
Slow down at delivery and at the next screen
Open the email while signed out. Your own browser is the worst place to test delivery: you are signed in, the cookie is warm, and the file is probably already on your desktop. Use a private window, or a browser where you are not signed in, and follow the link in the email rather than opening the file from your computer. Then check three things.
- The link opens the file, not a sign-up step you forgot was in front of it.
- The file is the current version. A footer date, version line or page count is the quickest way to tell.
- The email also arrives at a second address on a different mailbox provider.
Replace-file mistakes are easy to miss. If you revised the workbook after writing the delivery email, the link may still point at the older file while the page describes the newer one.
Keep the note even when a check passes. "Signed out, private window, phone: version 2 dated 12 October" is a sentence you can show a client. "Looks fine" is not.
One instruction, in three places. Confirmation first or immediate delivery are both legitimate, but the form, the next screen and the email have to tell the same story. If the form says the file arrives once you reply, the next screen must not say the download is ready. Press the button twice, or refresh the confirmation screen, and see whether one record or two reach your list; if duplicates appear, ask whoever manages the form how double submissions are handled.
Email choices that hold. Whatever you write under the form is a promise about what will arrive. The first email should arrive with the subject the form described. It should say who sent it and where to reply, and a reply should reach a mailbox someone reads. Every email should carry an unsubscribe link that works without logging in. If a short series follows the file, say so under the form before anyone signs up.
Read your own plan pages rather than assume. Leadpages pricing, retrieved 25 October 2026, publishes form and integration detail of the kind worth checking; Kit pricing, retrieved 25 October 2026, lists automated email sequences as a feature. Your tool may call the same thing an automation or a workflow, and may include it only on a higher tier. Neither link is a recommendation.
Record expected versus observed, then repair in order
Three columns are enough: what you expected, what happened, and the repair. Here is a finished record for a fictional operations consultant with a supplier-onboarding checklist.
| Check | Expected | Observed | Repair |
|---|---|---|---|
| Page promise | The contents list names six checks and all six are in the file. | The page promised a risk summary; the file had no such table. | Removed the line from the page. |
| Next screen | Check your inbox and reply to confirm. | The screen said the download was ready, but nothing opened. | Rewrote the screen to match the confirmation route. |
| Delivery email | The link opens version 2, dated 12 October. | Signed out, the link opened version 1. | Replaced the file behind the link, then retested signed out. |
| Unsubscribe | A working link in every email. | The link opened a page with no action on it. | Fixed the link before launch. |
Fictional consultant and observations, written to show the form of a record. Nothing here reports a test carried out by this site.
Fix a promise the file does not keep.
Delete the promise or add the item. A reader told one thing and sent another has a reason to distrust the paid work too.
Fix anything that stops the file arriving.
The request, the next screen and the email link. Until these work, every other improvement is invisible.
Fix anything that traps the reader.
A dead unsubscribe link, a help link that goes nowhere, a reply address nobody reads.
Then the wording and the polish.
Typos, the file name, the page description. Worth doing, but last, because it changes nothing about whether the journey works.
Retest only what you changed, plus one clean pass from the top with a fresh address, and date the record. If a fix breaks something else, you will want to know which change did it.
Make a release-or-hold decision
Two outcomes, decided once and written down. A third, publish and hope, is how a stale file reaches every reader who asks for it.
Release
All six stages passed on a stated date, on the devices you recorded, and the record names whoever will re-run the checks when the file changes.
Hold
One named reason and one date to retest. A hold is not a failure; it is a decision you can explain to a client in one sentence.
Release does not mean finished for ever. Re-run the delivery check whenever you replace the file, change the form or edit the sequence.
The worry underneath: that it will just collect dust
A launch test cannot make a generic workbook specific. If the file is a template with the logo swapped, the journey will pass and the reader will still leave. Two questions cover what the mechanics cannot.
- Does the page promise a step only your practice would include? If the headline could sit on any consultant's page, the reader has no reason to finish yours. Name the step most people skip in the work you do.
- Does the file say where the material came from? Client notes, your own framework, a process you follow with permission. A source line and a plain sentence about what the resource is not do more for credibility than any design choice.
If an AI tool helped draft the page or the file, check the sentences most likely to overreach before publishing. Reviewing AI-written claims covers that pass, and the free Source & Claim Review Checklist turns it into ten checks with three claim records. The freebie-seeker worry has a similar answer: a narrow task filters by itself. A checklist for collecting supplier approvals is useful to the consultant adding a third supplier and dull to everyone else, which is the point.
What you need, and where the structured version fits
No new software. Two email addresses on different providers, a phone, a browser where you are signed out, and somewhere to keep the record. If you already have a page, a form and an email tool, that is the whole kit.
The free Lead Magnet Launch Check Workbook is the printable version of this article for a finished resource whose page and emails exist: seven checks, a journey map, four test passes with two test inboxes, three templates, a symptom-to-repair table, a worked example and the release-or-hold decision. Its first action is the signed-out check above. It is a functional workbook, not a legal, compliance or accessibility audit, and it predicts nothing about inbox placement or sales. The pages are writing lines rather than fillable fields, so print it or annotate it.
Free: enter your email and reply VERIFY to the short email we send you. We email you the workbook and the one-page check sheet, then four short follow-up emails over two weeks on using it (the last one names our own $79 Workflow Pack). Every email has an unsubscribe link.
If the test shows the page copy is the weak part, the free Promotion Copy Template gives you the resource-page fields, a social post and the delivery email, with a completed example to copy the pattern from. The page itself is broken down in what a lead magnet landing page should include, and the messages after the download in planning five helpful emails. Used together, they let you see whether the page, the file or the audience is the stage to fix first.
Quick questions
Do I need two email addresses?
One shows whether the request arrives. Two, on different mailbox providers, show whether the delivery email behaves the same everywhere. The Launch Check Workbook is built around two test inboxes for that reason.
What if the resource is already live?
Run the same checks now. The record tells you which failure to fix first, and you can change the page, the file and the delivery email before you promote again. Start with the signed-out delivery check today.
Does a passed test mean the lead magnet will work?
No. It means the mechanics work: the request is recorded, the file arrives, the instruction matches the route, the links resolve. Whether readers want the resource depends on the problem it names and the audience you promote it to.
Sources & editorial notes
- Landing page platforms publish form and integration behaviour on their plan pages. Leadpages pricing, retrieved 25 October 2026, is cited as an example of the detail to look for. No price is quoted, no product is recommended and no affiliate relationship is active.
- Email tools list features by plan. Kit pricing, retrieved 25 October 2026, lists automated email sequences, cited as an example of what to check in your own tool before promising a sequence to readers.
- Workbook contents and the free-file route are described from the Launch Check Workbook page as of 25 October 2026.
- The operations consultant and every quoted record are illustrative. No tool was tested and no campaign, download figure or result is reported on this page.
Examples are illustrative. See our Editorial Policy, Review Methodology and Affiliate Disclosure.
Run the checks in order.
The free Lead Magnet Launch Check Workbook turns this into seven checks, four test passes with two test inboxes, a symptom-to-repair table and a release-or-hold decision.
Free: we send you a short email first. Reply VERIFY to it and we email you the workbook, then four short follow-up emails over two weeks (the last one names our own $79 Workflow Pack). Every email has an unsubscribe link.