Back

Search Results Visibility.
Choose what visitors can find on your site.

Search Results Visibility helps you select the content that can appear in WordPress internal searches. Manage allowed post types, exclude categories and hierarchical taxonomies, or select individual pages to hide.

This CORE module in WP Quick Tools brings these controls together in one panel. It helps make internal search more relevant, for example by leaving out utility pages or groups of content not intended to be browsed through search.

Exclusions do not delete content or protect it from direct access. They do not set noindex or automatically remove pages from external search engines.

What you can do with this module

Choose post types

Use Show in search for public types that WordPress makes searchable. Keep those useful to your audience and disable the others.

Control categories and taxonomies

You can exclude specific terms in the available hierarchical taxonomies. The exclusion also covers their descendants.

Exclude specific pages

Search for a page by title and add it to Excluded pages, without disabling search for all pages.

Account for a multilingual site

With the WPML APIs available, the module extends page and term exclusions to the translations it finds. Still check searches in the active languages.

Getting started, step by step

1. Enable the module

Open WP Quick Tools and enable Search Results Visibility.

2. Select allowed types

Check the available groups and set Show in search for those you want to include.

3. Review categories

In groups showing categories or hierarchical taxonomies, disable the terms to exclude. Consider their descendants too, as well as content assigned to multiple terms.

4. Choose pages to exclude

In the Pages to hide from search field, search for the title and select the result. Check that the page appears under Excluded pages.

5. Save the configuration

Save the Tools parameters. Check that you have not accidentally excluded every post type.

6. Run test searches

Search the frontend for words present in included and excluded content. Repeat the test in the active languages and with the search components actually used by the site.

Frequently asked questions

Does the module control Google and other external search engines?

No. The rules apply to WordPress internal search. They do not add noindex, change robots.txt, or constitute a removal request to external search engines.

No. It remains on the site and may be accessible by direct URL, menus, or other lists. The module filters search results, not the content itself.

Public types registered as searchable in WordPress. The list depends on the installed theme and plugins; some technical types are not presented as user-facing controls.

Yes. Search for it by title in the dedicated field, select it, and check that it appears under Excluded pages. Then save the configuration.

The individual selector in this version applies to pages. For posts, controls are available for post types and supported hierarchical taxonomies.

The panel offers public hierarchical taxonomies visible in the admin area. Standard WordPress tags are not hierarchical and are not included in these controls.

Yes. Taxonomy conditions include descendant terms. Check the entire branch before excluding a parent category.

If it belongs to an excluded term or its descendants, the exclusion condition can remove it from results even if it also belongs to an allowed category.

When the WPML APIs are available, the module finds translations of excluded pages and terms and adds their IDs to the exclusions. Check the result in the languages actually active.

Filters are provided for frontend WordPress search queries, including compatible AJAX queries, and content search through the standard REST endpoint. An external engine or custom query that does not use these paths requires a specific check.

Normal non-AJAX admin searches are excluded from the main filter. Internal queries recognized as WPQT configuration are also preserved. Check custom admin components that use different search paths.

After explicit configuration, no allowed types means no results in the filtered paths. Before the first save, the absence of a configuration instead keeps all normally searchable types.

Check that you saved the configuration and that the module is active. Then check whether the component uses standard WordPress search or an external index, and whether a cache retains earlier results. Exclusion does not prevent the same content from appearing in other lists on the site.