Hide Posts

Yes — by design. Hiding controls where a post is listed (homepage, archives, search, feeds, sitemaps, etc.), not who can open it. Anyone with the direct link can still read it, which is exactly what you want for syndication-only or direct-link content. If you need to restrict access itself, use WordPress’ built-in Private or Password-protected post status instead.

No. Hiding a post from the XML sitemap only removes it from the sitemap — search engines that already know the URL can still index it. To keep a post out of search results, set it to “noindex” with your SEO plugin (e.g. Yoast’s “Allow search engines to show this content?” setting). The two work well together: hide it from your site’s listings here, noindex it there.

The plugin clears its own caches the moment you save, so first check external layers: a page cache, object cache, or CDN can keep serving the old page — purge those. If the post appears via a theme or page-builder widget that runs its own custom database query, that query bypasses WordPress’ standard hooks and the plugin cannot filter it.

That’s intentional — you need to see and manage hidden posts. The “Hidden On” column shows exactly where each post is hidden. Hiding only affects visitor-facing output.

Yes. Go to Settings → Hide Posts and enable the post types you want. Posts are enabled by default, and WooCommerce products get their own store-specific options.

The “Hide from Yoast internal link suggestions” option applies to Yoast’s internal linking suggestions, which are a Yoast SEO Premium feature. The Yoast sitemap and breadcrumb options work with free Yoast SEO.

Deactivating simply stops the hiding — all posts reappear everywhere, nothing is lost. Deleting the plugin also removes its settings and visibility data, so hidden posts become fully visible again.

Thanks, donations help us to continue improving our plugins. Read More About Donations.

This is possible. This functionality is not free. You can contact me at martin@martincv.com for more information and send the name of the plugin you want to migrate from.