Disable WordPress Search When You Don't Need It
- WordPress includes a public search system by default, but not every website needs one.
- A small company website may contain only a handful of pages. A landing-page website may have nothing useful to search. Another site may rely entirely on a specialized search platform rather than WordPress's built-in results.
- Even when there is no visible search box, standard WordPress search URLs can still be requested directly.
<For example: example.com/?s=keyword>- Disable Site Search closes that default search functionality at the WordPress level rather than simply hiding a search form.
- When WordPress identifies the main frontend request as a standard search, WP PowerSuite converts it into a 404 with empty search results and no-cache headers.
- This provides a cleaner solution for websites where public WordPress search serves no useful purpose.
Disable the Core REST Search Endpoint
- WordPress also exposes search functionality through its REST API.
- When Disable Site Search is active, the core: /wp/v2/search route is removed.
- General REST collection searches that are not scoped to an allowed post type are also rejected.
- This keeps the module's behavior consistent across the traditional frontend search and WordPress's core REST search functionality rather than disabling only the visible search-results page.
- It does not replace WP PowerSuite's Disable REST API (Public) module, which serves a much broader purpose.
Keep Product and Post-Type-Specific Search
- Disabling general website search should not necessarily mean disabling every type of search.
- This is especially important for WooCommerce stores.
- A store may not want standard WordPress blog search while still relying heavily on product searches to help customers find items.
- WP PowerSuite therefore allows searches explicitly scoped to supported non-post post types to continue.
- For example, a WooCommerce request using product search can remain available while a regular WordPress ?s= search is disabled.
- Developers can also extend the allowed post types using the provided filter when a custom content type needs to retain its own search functionality.
