Understanding Search Parameters in the Member Search System

Link: https://support.brilliantdirectories.com/support/solutions/articles/12000106137

The member search functionality is powered by a series of specific GET parameters and field names. Knowing these parameters makes it easier to customize or replicate search forms so they work seamlessly with the built-in search logic. This article outlines the required parameters, field names, and CSS classes that drive keyword, category, and location searches, along with important notes about indexing and query construction.


Search Parameters Overview

These parameters define how keyword, category, and location data are passed into the member search system, ensuring that each search request returns accurate and relevant results.


Keyword Search

  • q – Main keyword search (searches member names, company names, and meta data)

Category/Service Search

  • sid – Top-level profession/category ID (converted to pid in the widget that builds the search query)

  • tid – Sub-category/service ID

  • ttid – Sub-sub-category ID


Location Search

The value submitted in the location_value field is used to fetch detailed location information from Google Maps via API. This information is then used to fill in the following GET parameters:

  • country_sn – Country short name/code

  • stateSearch – State search value

  • stateSearchLN – State long name

  • adm_lvl_1_sn – Administrative level 1 (state/province) short name

  • county_sn – County short name

  • city – City name

  • postal_code – ZIP/postal code

  • lat – Latitude

  • lng – Longitude

  • nelat, nelng, swlat, swlng – Bounding box coordinates

  • radius – Search radius for radius-based searches

Other Parameters

  • sort – Sort order (alphabet-asc, alphabet-desc, reviews, most_likes, etc.)

  • overall_rating – Filter by rating

  • subscription_id – Filter by membership level

  • listing – Member type (Company/Individual)

  • parentid – Parent account ID for sub-accounts

Required Field Names and Structure

Specific field names, CSS classes, and form configurations are needed to make sure the search form communicates correctly with the system and integrates with features such as autosuggest and Google Maps.


Required Field Names

  • q – Keyword search field (required for text search)

  • location_value – Location field (required for location-based search)

  • sid – Top Category dropdown (if using category-based search)

  • tid – Sub Category dropdown (if using category-based search)

  • ttid – Sub-Sub Category dropdown (if using category-based search)

CSS Classes

  • member_search – Applied to keyword search inputs to enable keyword autosuggest

  • googleSuggest googleLocation – Applied to location fields for Google Maps integration

  • btn_search – Applied to search submit buttons (though not strictly required)

Form Structure

  • Forms should use method="get" and submit to the search results page

  • The website-search class is commonly used for styling

  • Location fields should have autocomplete="off" for Google Places integration


Index Rebuild Considerations

A search index rebuild is not required for keyword or country filters to update properly. Reviewing the code of the search widgets being used and exploring the Search – Member – Search Query widget provides additional insight into how the search query is constructed and assists with any customization needs.


Final Notes

Understanding how these GET parameters, field names, and CSS classes interact makes it easier to create consistent and reliable search forms. No manual index rebuild is necessary for updates — instead, reviewing the search widgets and the query logic they contain is the recommended method to ensure forms continue to function as intended.