Page and Post Restriction
View on WordPress.orgScores higher than 33% of indexed plugins
About
Restrict content access for WordPress (WP) | Restrict pages/posts in WP based on user roles and login status to protect content
Security History
What It Does
Page and Post Restriction lets WordPress administrators lock specific pages or posts behind login walls or role-based permissions. Site owners can configure rules on a per-page basis to control who sees what content based on whether a visitor is logged in and which WordPress user role they hold.
Who It's For
This plugin fits small WordPress sites that need a lightweight, no-frills way to hide select pages or posts from the public or from certain user roles, without setting up a full membership system. It works well for intranet-style sites, internal company documentation, or simple client portals built on WordPress.
Who Should Skip It
If you need recurring payments, subscription tiers, drip content, or detailed user account management, skip this plugin and choose a dedicated membership solution. Sites running modern PHP-only stacks below 7.4 should also look elsewhere, since the plugin's minimum PHP 5.6 requirement signals outdated code that may not be security-hardened.
The Bottom Line
Page and Post Restriction does one thing, restrict page and post access by role or login status, and does it with a clean, recently maintained codebase that scores 74.88 overall. The catch is a tiny install base, no forum support history, and a PHP 5.6 minimum that raises questions about long-term security posture. It is a reasonable pick for a simple internal site, but anyone needing subscriptions, drip content, or reliable community support will be better served by the alternatives listed above.
Related Plugins
Pick this when you need a full registration and membership workflow with 50,000 installs and a much larger user community behind it.
Choose this if your restriction needs are tied to paid subscriptions or recurring billing, where Page and Post Restriction offers nothing.
Go with this 300,000-install heavyweight when you want to lock entire sites, categories, or partial content blocks with a single password instead of role-based rules.
Select this 40,000-install alternative when you need richer conditional logic, such as restricting blocks within a page based on roles, capabilities, or custom conditions.
Pick this if your site is built with Elementor and you want to hide widgets or sections based on user roles directly from the page builder.