A WordPress.com subscriber may receive one daily or weekly digest because their account is set to collect new-post emails. That setting does not prove that every missing post email was caused by a digest. A post may also have had email sending turned off, been published before the reader subscribed, or fallen into spam.
WordPress.com sends a notification email when a new post is published, provided email sending is on for that post. Pages and custom post types do not generate these subscriber emails. WordPress.com’s newsletter email guide also says that each post is emailed only once.
A digest is a delivery choice
A logged-in WordPress.com reader can choose how subscription emails arrive. The available default delivery choices are instant delivery for each newly published post, a daily digest, a weekly digest, or no email. A reader who selects daily or weekly delivery receives a digest rather than a separate message for every post.
This choice belongs to the reader’s WordPress.com notification settings. The publishing controls described for a post let the site owner decide whether that post is emailed and who may read it. They do not provide a per-subscriber switch for changing one reader from a digest to instant emails.
| Reader’s email delivery choice | What the reader receives |
|---|---|
| Instantly | A new-post email when a subscribed site publishes a post |
| Daily digest | A digest of posts from subscribed sites |
| Weekly digest | A weekly digest of posts from subscribed sites |
| Never send email | No subscription emails |
WordPress.com also lets a reader pause all subscription emails. That is separate from choosing a digest. If all emails are paused, changing the delivery frequency alone will not restore messages.
Where a subscriber can check the setting
The reader needs to sign in to the WordPress.com account used for the subscription. From any WordPress.com screen, they can hover over their name in the top-right corner, open My WordPress.com account, and choose Notifications. In the Emails section, WordPress.com lists the delivery controls for sites followed in the Reader.
The relevant setting is Default email delivery. The reader can choose instant emails, a daily digest, a weekly digest, or no email. Weekly delivery also lets the reader choose a day; daily delivery lets them choose a time of day. WordPress.com does not state one universal time when every digest arrives, so a publisher should not promise a fixed delivery hour.
After changing the setting, the reader must save it at the bottom of the notification settings page. The same page includes Pause all emails, which should remain unchecked when the reader wants subscription messages.
A digest does not explain every missing post email
Start with the delivery preference when a reader consistently receives roundups but never individual post messages. That pattern matches daily or weekly delivery. It does not settle cases where a specific post is absent.
Check whether the subscriber was already subscribed when the post went live. WordPress.com lists subscription timing as one reason a subscriber may not receive a post email. Joining after publication does not create a retroactive post notification.
Then check the address connected to the WordPress.com account. A reader may be looking in a different inbox, forwarding may point elsewhere, or the account may use an address they no longer monitor. WordPress.com also advises checking the spam folder and confirms that email filtering can explain an apparently missing message.
The publisher should check the post itself. In the newsletter panel, WordPress.com shows whether email is enabled. If it is off, the panel says that the post will not be emailed. The publisher can turn on email sending before publishing. The panel can also preview the message and send a test email before publication.
A scheduled post follows the same rule: its notification email is sent soon after the post becomes live. Scheduling a post does not send the email at the time the draft is created.
Post type, republication, and site status matter
WordPress.com limits subscriber emails to posts. Publishing a page or a custom post type will not produce the same subscriber email. That distinction catches a surprisingly ordinary mistake: the content is visible on the site, yet it was never eligible for a post notification.
Republishing an already published post does not send it again. WordPress.com states that each post is emailed once. An edit to an old post may therefore appear on the site without creating another inbox message.
A private site also does not send email notifications of its posts to subscribers, according to WordPress.com’s newsletter documentation. A site owner troubleshooting a broad delivery failure should include site privacy in the review.
WordPress.com describes one further case involving a Jetpack connection error. If several posts were delayed while the connection was unavailable, WordPress.com sends notices for the first three delayed posts after the connection returns and holds back the rest. That rule prevents a large backlog from producing a flood of subscriber emails.
What the publisher can check
The publisher’s task is to confirm that the site sent, or was configured to send, the post email. They cannot inspect or override an individual reader’s inbox rules or chosen digest frequency.
Before publishing, open the newsletter panel in the editor. Confirm that email sending is on, review the audience, and use the preview or test-email option if needed. The post title becomes the email subject line, so a clear title also makes it easier for a reader to search their mailbox.
For a post that went live with email sending turned off, WordPress.com documents a recovery path: switch the post back to draft, enable Send this post to subscribers, and publish it again. This applies to a post whose email never went out. It does not turn an already delivered post into a second routine notification.
What the subscriber can check
The reader should first look at the address registered with their WordPress.com account, then search that inbox and its spam folder. Next, they should open Notifications and review Emails. Check that all emails are not paused, then select instant delivery if separate post emails are wanted.
If the reader prefers fewer messages, daily or weekly delivery is the right setting. A digest is an intentional frequency choice, not a delivery error by itself.
If the post is still missing after those checks, compare the publication time with the subscription time and ask the publisher to verify the post’s newsletter panel. That separates an inbox or preference issue from a post that WordPress.com never sent.
Useful questions before changing anything
Did the reader receive a daily or weekly roundup from the same site?
Was the reader subscribed before the post was published?
Was the content published as a post with email sending enabled?
Is the reader checking the email address attached to their WordPress.com account, including its spam folder?
