Skip to content

Why WordPress.com Password-Protected Posts Email Subscribers but Stay Out of RSS

Sealed envelopes beside a closed brass padlock on a wooden table.

A WordPress.com post can be password-protected, send a new-post email to subscribers, and remain absent from the site’s RSS feed at the same time. Those settings cover different things.

Password protection controls who can open the post itself. RSS controls whether the post appears in the site feed. The newsletter setting controls whether WordPress.com emails subscribers about publication. WordPress.com documents these outcomes separately: password-protected posts stay out of RSS, while subscribers receive a notification and need the password to view the content. WordPress.com, “Control who can see a page or post”

That combination can surprise a site owner who expects “password-protected” to mean “silent.” It does not. If the post must stay off subscribers’ inboxes, turn off its email notification before publishing.

Password protection controls access to the post

A password-protected post asks visitors for the password before it shows its content. WordPress.com saves the password in a browser cookie after a visitor enters it. Someone using a shared computer can clear browser cookies if they do not want that password retained there. WordPress.com, “Control who can see a page or post”

The protection applies to the page or post content. A subscriber may learn that a new password-protected post exists through an email notification, yet they cannot read the protected content without the password.

A visitor who reaches the post without successfully entering its password does not see the protected content. WordPress.com says that visitor is sent to a 404 error page. On public sites, WordPress.com also counts views of password-protected posts and pages in site statistics, except views by site owners and members. WordPress.com, “Control who can see a page or post”

Password protection fits a narrow use case: you want to publish a post at a public URL while restricting the post body to people who know a shared password. It does not create a private workspace for a named group of readers.

Why the post can email subscribers but stay out of RSS

WordPress.com treats the email notification and RSS feed as separate publication channels.

A password-protected post is excluded from the site’s RSS feed. That rule applies even when the post has been published. WordPress.com also states that subscribers receive a notification about a new password-protected post. WordPress.com, “Control who can see a page or post”

The email does not make the password unnecessary. It announces a newly published post, while access to the protected content still requires the password.

Publishing state Subscriber email Site RSS feed Who can read the post
Public post WordPress.com says public posts are emailed to subscribers The password-protection exclusion does not apply Everyone
Password-protected post Subscribers receive a new-post notification Excluded Visitors with the password
Private post Not emailed to subscribers Not visible Administrators and Editors

The table reflects WordPress.com’s visibility guidance. A private post has stronger audience limits than a password-protected post: only Administrators and Editors on the site can view it. WordPress.com says private posts are also absent from the Reader, feeds, and search results, and subscribers do not receive an email about them. WordPress.com, “Control who can see a page or post”

Password-protected versus private: choose the outcome you need

Use password protection when readers should be able to access a published post by entering one shared password. Expect the post to stay out of RSS, but do not assume publication will be invisible to subscribers.

Use a private post when only site Administrators and Editors should see it. WordPress.com lists private posts as unavailable in feeds, search results, and subscriber email notifications. WordPress.com, “Control who can see a page or post”

These options answer different questions:

  • Password protection answers: “Who has the password?”
  • Private visibility answers: “Which site roles can view this?”
  • The newsletter toggle answers: “Should subscribers receive an email for this post?”

Keeping those questions separate avoids an easy publishing mistake. A post can have a password and still be set to notify subscribers.

Turn off the email before you publish

WordPress.com provides a per-post setting for posts that should publish without a subscriber email. In the editor, click the Newsletter icon in the upper-right corner. In the Email section, turn off “Send this post to subscribers.” WordPress.com says the sidebar then shows “Newsletter emails are turned off.” WordPress.com, “Disable newsletter emails”

Do this before publishing. The timing matters. WordPress.com states that the toggle no longer appears after the post is published. A password-protected post that has already been published cannot use that per-post toggle retroactively.

For a password-protected post that should not notify subscribers, use this order:

  1. Create or edit the post.
  2. Set its visibility to Password protected and enter the chosen password.
  3. Open the Newsletter settings in the editor.
  4. Turn off “Send this post to subscribers.”
  5. Confirm that newsletter emails are turned off in the sidebar.
  6. Publish only after those settings match the intended audience.

That check takes little time and prevents a mismatch between access control and notification behavior.

A site owner can also change the default for future posts. WordPress.com says sites on Business and Commerce plans can go to Jetpack → Newsletter → Settings and turn off “Email new posts to subscribers by default.” The change saves automatically. WordPress.com directs owners of free, Personal, and Premium sites to upgrade for that feature. WordPress.com, “Disable newsletter emails”

The site-wide default and the per-post toggle solve different needs. Use the default when most new posts should not generate notification emails. Use the per-post toggle when one post needs an exception. For a specific post, WordPress.com directs users to the per-post setting.

Treat uploaded media as separate from the post password

Password protection does not secure every file inserted into the post. WordPress.com warns that an image or other media file added to a password-protected page or post can still be indexed by search engines. The file can also be directly accessed by visitors without a password. WordPress.com, “Control who can see a page or post”

That limitation matters for screenshots, PDFs, images, audio, and any other upload that should not be reachable outside the protected post.

A simple fictional example shows the risk. Suppose a consultant creates a password-protected post for a client and inserts a project screenshot. The post body requires the password. The screenshot file itself may still be directly accessible, according to WordPress.com’s media warning. Password protection alone is therefore a poor choice for media that must remain inaccessible to people without the password.

Check the files before publishing. If an uploaded asset contains information that must not be public by direct URL or search indexing, do not rely on the post password as the only safeguard.

A short check before publication

Read the post’s visibility and email settings as two separate controls. Verify that the post is marked Password protected, if that is the planned access method. Verify that “Send this post to subscribers” is off when no notification should go out. Review every uploaded media item with the understanding that the password does not necessarily protect its direct file URL.

For a private draft intended only for site staff, private visibility is the closer match. For a published post shared through one password, password protection can work, provided the subscriber-email setting and uploaded media have been checked first.

Do subscribers need to know that a protected post exists, or should publication remain limited to site staff? Does any uploaded image, PDF, or audio file contain material that should never be reachable through a direct link?