Skip to content

Knowledgebase

Understanding private posts and who can read them

wordpress

A private WordPress post is restricted through WordPress permissions rather than a shared visitor password. In a standard installation, administrators and editors can read private content, while other access depends on the user's capabilities and any customisation applied to the site.

Who can read a private WordPress post?

Private status is not a promise that only the author can read the item. Other authorised editorial users may also have access. If you need material visible to one customer or one project team, define an appropriate access-control workflow rather than relying on the word Private alone.

Also distinguish private post content from its uploaded files and external integrations. A linked Media Library file can remain publicly reachable by direct URL unless a separate mechanism protects it.

01 Set and test private visibility

  1. Edit the intended post or page and open the visibility settings.
  2. Choose Private, review the confirmation and save the item.
  3. Open the public URL while signed out and confirm that an ordinary visitor cannot read the protected content.
  4. Test with representative user roles that should and should not have access. Use separate accounts rather than changing an administrator's role merely for a quick test.

02 Review templates and integrations

Check custom search, listings, API integrations and third-party plugins if the site uses them to expose content. A plugin can implement its own permission handling or display derived information elsewhere. Verify the actual result rather than assuming every extension follows the default interface exactly.

Keep sensitive details out of titles or other fields until you have confirmed how the whole site displays them. If content was previously public, changing its status does not recall copies already distributed outside the website.

03 Choose a better fit when necessary

For editorial work awaiting approval, Draft or Pending Review may express the workflow more clearly. For a temporary review link, use a supported preview-sharing method with an understood access boundary. For customer documents, use authenticated protected delivery.

If the wrong person can read private content, record the role and affected URL, review their capabilities and investigate relevant plugins. Do not solve the issue by sharing or changing the site's main administrator credentials.

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support