A swipe file earns a permanent spot in someone's bookmarks when every example has a real result attached and a note on why it worked, not just a list of things that sound clever.
A checklist converts when it's built from a process you actually run, broken into clear stages, not a generic list of tips. Start from a real template and gate it after the first stage.
Neither wins outright. A time-based delay works well when a few extra seconds signals real engagement; click-to-unlock works well when you want the visitor to control the pace instead of being interrupted.
Write the post as blocks, set the gate position to two or three paragraphs in, and the rest unlocks after an email. It's inline gating applied to an article instead of a checklist or template.
Inline gating shows some real content before the form; a squeeze page shows the form immediately. The setting is the same gate position number, just at zero or higher.
A squeeze page (gate everything upfront) usually converts a higher share of the people who reach it. A content upgrade (real preview, then gate) usually brings in more total leads from content-driven traffic, because it earns trust first.
Stan Store is built to sell things, digital products, courses, coaching calls. If all you need is one free resource that captures an email, a dedicated gating tool fits the job better than a storefront.
Notion and Google Docs sharing links don't support an email gate on their own. The easy fix is publishing the content as a gated page instead, or gating the page that reveals the doc's link.
The simplest way to require an email for a PDF is to stop hosting it on a public link. Upload it to a gated page instead: visitors see a preview, and the file unlocks after they give their email.
The usual lead magnet stack is a doc, a form tool, a Zap, and a spreadsheet, glued together and one broken link from failing silently. Here's what replaces the whole thing.
You don't need WordPress or a plugin to gate content. A standalone gated page with a built-in email form does the same job with no installs, no conflicts, and no PHP.