How to improve search on a WordPress site

Write down the content visitors expect to find: posts, pages, products, documents, custom post types, categories, tags and important custom fields. Search for ten real phrases, including product names, partial phrases, misspellings and terms that should return no results.

WordPress core searches the post title, excerpt and content by default. It does not automatically turn every custom field, taxonomy or attachment into a useful searchable field.

Submit a test search and check the address bar. A standard WordPress search uses a GET form aimed at the site root, with the search input named s. If a page builder button sends the query to a custom URL or uses another field name, WordPress may not recognise it as a normal search.

Check the form in the theme’s search area and on mobile. Keep a visible label, use an input of type search, and make sure the results page shows the phrase that was searched.

Review every custom post type you want to appear. Its registration must allow front-end search by setting exclude_from_search to false. You can also add selected post types to the main search query with the pre_get_posts action, restricted to the front end and the main search query.

Put that change in a site-specific plugin or child theme, not in search.php. The query is prepared before the search template loads. A common Friday problem is a custom post type being marked as excluded, so the search page looks broken even though the content exists.

Use specific titles, useful excerpts and the words visitors actually use. Add synonyms to the copy where they make sense, and keep product names, reference numbers and important terms in searchable title or content fields rather than hiding them only in images.

Remove duplicate or obsolete pages from public search, fix empty excerpts, and give important content clear taxonomies. This manual work is often enough for a small brochure site or blog, and it avoids adding an index that needs maintenance.

For a developer-led site, WordPress provides pre_get_posts for changing the main search query, post_search_columns for choosing among title, excerpt and content, and posts_search for filtering the generated search SQL. Use these when you need to include a post type, limit the searched columns or apply a narrowly defined rule.

Core search does not provide a simple setting for weighted fields, typo tolerance, live suggestions, custom-field indexing or faceted filtering. Searching custom fields by adding database conditions can also become slow as the content library grows, so profile the query and test pagination before deploying it.

Choose WP Search with Algolia when the site has a large or content-heavy library, custom post types, WooCommerce products, or a need for live results and filters. Follow its setup wizard to connect Algolia, select the content types and taxonomies to index, run the initial index, and configure the search interface and ranking controls.

After indexing, test newly published, edited and deleted content. Rebuild or synchronise the index when results are missing, and check that the theme’s search form still submits s. An indexed search service is the fast route, but it adds an external service and another index to monitor.