Skip Navigation

[Resolved] Do I need Relevanssi for custom fields to appear in search?

This thread is resolved. Here is a description of the problem and solution.

Problem: I would like to know if Relevanssi is required to be able to search custom field values using the standard text search.

Solution: By default, WordPress does not index custom field values for text searches. Some third-party system is required. Relevanssi is one third-party system that works well with Toolset.

Relevant Documentation: https://toolset.com/documentation/user-guides/searching-texts-custom-fields-views-relevanssi/

100% of people find this useful.

This support ticket is created 5 years, 5 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

This topic contains 2 replies, has 2 voices.

Last updated by michaelW-23 5 years, 5 months ago.

Assisted by: Christian Cox.

Author
Posts
#1248453
custom-field-search.png

Tell us what you are trying to do?
I want my custom field to be Included in text searches throughout the site. Is the standard WordPress search function able to read these fields or do I need to install Relevanssi?

#1248545

Hi, yes you need Relevanssi since WordPress search does not index custom fields by default. More information about that here: https://toolset.com/documentation/user-guides/searching-texts-custom-fields-views-relevanssi/

#1255195

My issue is resolved now. Thank you!