Simple Restrict
View on WordPress.orgScores higher than 43% of indexed plugins
About
Restrict pages based on permissions assigned to pages and granted in user profiles.
Security History
What It Does
Simple Restrict lets site administrators lock down individual WordPress pages by assigning custom permissions directly to each page and then granting those same permissions to specific user profiles. When a visitor lacks the required permission, the restricted page is hidden from them entirely, making it a lightweight option for gating private content without configuring complex roles.
Who It's For
This plugin suits small to mid-sized WordPress sites that need page-level access control for a handful of users, such as private client portals, small membership sites, or intranets where only a few pages need to be restricted. It works best for administrators who are comfortable editing user profiles and want a no-frills solution without subscriptions or e-commerce features.
Who Should Skip It
If you run a large membership platform, sell subscriptions, or need drip content, paywalls, or granular role management, you should look elsewhere, as Simple Restrict does not handle payments, content schedules, or bulk user imports. Sites needing WooCommerce integration or front-end registration flows will also outgrow this plugin quickly.
The Bottom Line
Simple Restrict delivers exactly what its name promises: a stripped-down, page-by-page permission system with a strong rating, recent updates, and broad WordPress compatibility. Its tiny install base, absence of support activity, and lack of PHP version metadata suggest it is a personal or small-team project rather than a community-driven tool. For a simple internal use case with under a hundred protected pages, it is a solid, low-risk choice, but anyone running a growing membership business should plan to migrate eventually.
Related Plugins
Pick this instead if your goal is to protect contact information from scrapers rather than restrict entire pages.
Choose this if you build pages with Elementor and need to conditionally hide widgets or sections based on user roles or login status.
Opt for this when you want to obscure WordPress itself from attackers rather than restrict content visibility to specific users.
Pick this if you only need to keep subscribers out of the wp-admin area and do not need page-level restrictions.
Choose this when you want to lock down an entire site or development environment to logged-in users or specific IP addresses.