Post actualizado el día octubre 17, 2026 by DeiviSanzPlay
You don’t need to delete a page to keep it out of sight. In fact, deleting is the worst move if you might need that content later. WordPress gives you four real ways to hide a page: make it private, password-protect it, unpublish it as a draft, or noindex it from search engines. Each one behaves differently, and picking the wrong one is how people accidentally break their own site.
Let’s cut the fluff. Hiding a page in WordPress is a two-minute job once you know which switch does what. The confusion comes from tutorials that treat all four options as interchangeable. They’re not.
Private vs. Password-Protected: Which One Actually Hides the Page?
If you want the page gone from the public eye entirely, set its visibility to Private. Only users with Editor or Administrator roles on your site can see it. Even logged-in subscribers get a 404. That’s the cleanest way to hide a page in WordPress without deleting it.
Password protection is different. The page URL stays live, the title may still show up in menus and sitemaps, and anyone with the password can read it. Use it for client previews or gated downloads, not for content you genuinely want hidden.
Rule of thumb: if you don’t want a single stranger to know the page exists, go Private. If you just want to control who reads it, use a password.
How to Hide a Page in WordPress Without Deleting It (Step by Step)
Open the page editor, look at the right-hand sidebar under Document settings, and find the Visibility line. Click Public and you’ll see three options: Public, Private, and Password protected.
- Private: pick this, hit OK, then Update. The page is hidden from every visitor who isn’t an admin or editor.
- Password protected: type a password, update, and share it only with the people you trust.
- Draft: if you’re not ready to publish at all, switch the status from Published to Draft. The page disappears from the front end but stays in your dashboard.
- Noindex: if you want the page live but invisible to Google, install an SEO plugin like Yoast or Rank Math and toggle Noindex under the Advanced tab.
That last one matters more than people realise. Making a WordPress page private keeps it out of your site, but a draft or password-protected page can still leak into search results if it was indexed before you changed the settings. Noindex is the only option that actively tells Google to drop it.
Hiding a Page from the Menu Without Touching Its Status
Sometimes you want the page live and shareable by link, but you don’t want it cluttering your navigation. That’s a menu problem, not a visibility problem.
Go to Appearance → Menus, find the page in your menu structure, and remove it. The page itself stays published. Anyone with the URL can still read it. You’ve just hidden a page from WordPress navigation, which is exactly what you want for thank-you pages, landing pages for ads, or internal resources.
If your theme uses a block-based menu, the same logic applies inside the Navigation block. Delete the link, keep the page.
Blocking Specific Users Instead of Hiding the Whole Page
Here’s where most guides stop short. You can block access to a page on WordPress for certain users while letting others through. That requires a membership or role plugin — Members, User Role Editor, or Restrict Content are the usual picks.
With those, you can set rules like: logged-in users only, subscribers with a specific role only, or everyone except a custom role you define. This is the approach I’d defend for membership sites, course platforms, and any WordPress install where ‘public’ and ‘private’ are too blunt.
Don’t overengineer it, though. If you only have three pages to hide, a plugin is dead weight. Use the built-in visibility settings and move on.
What Actually Happens Behind the Scenes
When you set a page to Private, WordPress changes the post status in the database from publish to private. The permalink still resolves for admins, but the query that fetches public content skips it entirely. That’s why it never appears in archives, feeds, or sitemaps.
Password protection works differently: the status stays publish, but a hashed password is stored in post meta. The content is wrapped behind a form. Search engines can index the title and excerpt, which is why password-protected pages sometimes show up in Google with a snippet. Annoying, and a good reason to pair it with noindex.
Understanding this saves you from the classic mistake of ‘hiding’ a page and then finding it ranking on page two of Google three weeks later.
Common Mistakes When Hiding WordPress Pages
- Forgetting to clear the cache. If you use WP Rocket, LiteSpeed, or Cloudflare, the old public version can linger for hours. Purge after changing visibility.
- Assuming drafts are invisible. They are on the front end, but preview links can be shared and indexed if you’re careless.
- Using password protection for SEO-sensitive pages. Google can still see they exist. Noindex them separately.
- Hiding a page that other pages link to. You’ll create broken internal links and hurt your crawl budget.
That last point is the one people ignore. Run a quick check in a tool like Screaming Frog after you hide anything. If a hidden page was linked from your homepage, remove the link too.
So, Which Method Should You Use?
If the goal is to hide a page in WordPress from the public completely, set it to Private. No debate. If you need to share it selectively, password-protect it and noindex it. If it’s just about the menu, remove it from the menu and leave the page alone.
Resist the urge to install a plugin for something WordPress already does natively. The built-in visibility settings cover 90% of real-world cases, and every extra plugin is another thing that can break on update day.
Now go hide that page. It takes less time than reading this article.
