A subscription form earns its place only when the reader understands what will arrive next. “Get every new Linux debugging guide by email” is a promise; “Follow us” is furniture. WordPress now gives site owners a native Subscribe block, so the hard part is no longer generating a button—it is placing and testing the invitation without turning the page into a wall of pop-ups.
“Follow” and “Subscribe” now describe the same reader goal
Older WordPress documentation used a Follow Button generator that returned JavaScript to paste into a site. Current WordPress.com and Jetpack interfaces call the reader-facing control Subscribe and manage it through blocks and Newsletter settings. Readers can receive posts by email and, when using WordPress.com, manage delivery preferences through Reader.
Choose the path that matches your site
WordPress.com-hosted site: newsletter and subscription features are built into the platform; add the Subscribe block or enable a placement from Jetpack → Newsletter.
Self-hosted WordPress with Jetpack: install/connect Jetpack, enable Newsletter subscriptions, and use the Jetpack Subscribe block.
Self-hosted site without Jetpack: the WordPress.com subscription workflow is not automatically available. Use a reputable newsletter provider/plugin and follow its consent and deliverability documentation instead.
Classic Editor site: the Subscribe block expects the block editor. Jetpack documents switching to the block editor or allowing users to choose between editors.
Add the Subscribe block to one page or post
Sign in to WP Admin and open the page or post in the block editor.
Select the + block inserter and search for Subscribe.
Insert the Subscribe block where the reader has enough context to decide—commonly after the introduction, after a useful tutorial, or in a focused newsletter landing page.
Replace generic heading text with the content and cadence readers should expect.
Set the email-field placeholder, button label, success message, colors, typography, border, and spacing in the block controls.
Choose the standard email form or the button-only style. The button-only style opens a subscription modal.
Preview desktop and mobile layouts, then save or publish.
Test as a logged-out visitor with an email address you can access.
A better invitation than “Follow this blog”
Name the subject: Android platform debugging, Linux commands, or weekly engineering notes.
State frequency honestly: every post, weekly digest, or occasional release notes.
Keep the button literal—Subscribe or Get engineering updates is clearer than a clever label.
Put privacy context close to the form when required by your jurisdiction and policy.
Avoid pre-checked marketing consent or language that hides what the email address will be used for.
Place a Subscribe block after every post
For a publication, repeating one calm invitation at the end of each article is usually more useful than manually editing hundreds of posts. In current Jetpack Newsletter settings, enable the option to add the Subscribe block at the end of each post. With a block theme on WordPress 6.5 or later, the Preview and edit link opens the Single Post template so you can adjust its appearance.
Go to Jetpack → Newsletter and open Settings.
Find the Subscriptions section under Homepage and posts.
Enable Subscribe block at the end of each post.
Use Preview and edit when available to style the block in the Single Post template.
Save the settings and inspect several real posts, including a short post, a long post, and a mobile viewport.
This automatic placement applies to posts, not ordinary pages or custom post types. Add a block directly to those layouts when they need a subscription form.
Add a floating button, pop-up, overlay, or navigation entry
WordPress.com and current Jetpack Newsletter settings can also expose a homepage overlay, an in-post subscription pop-up, a floating corner button, and navigation blocks. These are distribution choices, not requirements. Start with one persistent placement and one contextual placement; measure before adding more.
Floating button: continuously available but can cover mobile controls or accessibility widgets.
Post pop-up: visible, yet more interruptive; it is suppressed for some contexts such as already-subscribed readers and recently dismissed prompts.
Homepage overlay: useful for a newsletter-first publication, aggressive for visitors arriving to complete a task.
Navigation Subscribe block: predictable and unobtrusive; current support is tied to block themes.
Comment subscription options: useful for active discussions, but distinguish updates to the entire site from replies on one comment thread.
Customize the form without weakening clarity
Use sufficient color contrast for field borders, placeholder text, labels, focus indicators, and the button.
Keep the email field and action touch-friendly on narrow screens; use the new-line option if the inline layout becomes cramped.
Write a success message that tells the reader to check their inbox for confirmation when confirmation is required.
Use the button-only style only when hiding the email field does not make the action ambiguous.
Show subscriber counts only when they build useful trust and the number is represented honestly; social totals can be rounded or use different definitions.
If newsletter categories are enabled, let readers understand and manage the subjects they receive.
Test the subscription as a real visitor
Open the published page in a private browser so an existing WordPress.com session does not change the form.
Submit a fresh email address and capture the visible success state.
Check inbox, spam, and quarantine folders for the confirmation message.
Use the confirmation link. A visitor without a WordPress.com account may have one created as part of the managed subscription flow.
Publish or send a controlled test post and confirm sender identity, subject, layout, links, unsubscribe control, and delivery timing.
Verify the subscriber appears in Jetpack → Subscribers, then test removal or unsubscribe with the same address.
Repeat on a phone and with keyboard-only navigation.
Seeing a success message is not end-to-end verification. The durable state is a confirmed subscriber who receives the intended publication and can leave it without asking an administrator.
Manage subscribers without treating them as WordPress users
Use Jetpack → Subscribers to search, filter, inspect, remove, and export subscribers. A newsletter subscriber is not automatically a local WordPress user with dashboard access. Keep that distinction clear when auditing accounts or explaining access to editors.
Review confirmed versus unconfirmed subscription state before diagnosing delivery.
Export only for a legitimate operational purpose and protect the file as personal data.
Do not upload purchased lists or silently repurpose addresses collected for another reason.
Honor removals and unsubscribes across any separate email platform you also operate.
Limit dashboard access to people who genuinely administer the publication.
Troubleshoot common failures
The Subscribe block is missing: confirm Jetpack is active/connected on a self-hosted site, Newsletter subscriptions are enabled, and the block editor is available.
No confirmation email arrives: verify the address, wait briefly, check spam/quarantine, and retry once rather than repeatedly generating mail.
The form looks different while testing: sign out or use a private window; WordPress.com-aware controls can recognize the logged-in account.
The automatic block appears on posts but not pages: that placement is designed for posts. Insert a Subscribe block in the page or template.
The pop-up does not appear: the visitor may already subscribe, may have dismissed it recently, or the content type/context may suppress it.
Subscribers do not receive a post: check confirmation status, newsletter/category selection, publication visibility, send settings, and whether the address unsubscribed.
The layout breaks on mobile: reduce side-by-side constraints, place the button on a new line, and inspect theme/plugin CSS conflicts.
Privacy and performance checks before launch
Update the site privacy notice to describe subscription processing, providers, retention, and reader choices.
Confirm the form communicates the expected emails before submission.
Avoid custom analytics on typed email values or confirmation URLs.
Test whether overlays or floating controls shift content, obscure controls, or trap keyboard focus.
Measure page performance after enabling extra newsletter UI; every additional prompt still participates in the real page experience.
Document who can export the subscriber list and how exported files are deleted.
Related WordPress maintenance guides
If your publication syndicates complete posts, review how to add featured images to WordPress RSS feeds.
Before reorganizing newsletter landing pages, use the WordPress duplicate-post workflow carefully.
Keep search crawlers away from private staging copies with the WordPress noindex guide.
Primary references
Jetpack’s current Subscribe block documentation covers activation, insertion, styling, button-only mode, categories, automatic post placement, subscriber management, and privacy data.
The official WordPress.com newsletter settings guide documents overlays, post pop-ups, automatic blocks, floating buttons, navigation controls, comments, and confirmation behavior.
The subscriber management guide explains the current Subscribers dashboard and export/management tools.
Readers can use WordPress.com Reader to manage frequency as described in Jetpack’s subscribe-to-a-site guide.
Comments and corrections