Search plugin data paths

Where WordPress search plugins send the queries your visitors type

Site search captures intent. Visitors type health conditions, legal problems, and product needs into the search box. Some plugins keep that query on your WordPress host. Others can send search terms to an outside search provider as visitors type, before they submit a search. This table summarizes the documented setups below. Your settings can change when queries leave.

Based on plugin documentation, not tests of your site. Your settings can change what loads. This is not legal advice or a compliance rating.

Scan your site for third-party requests

How we group search plugins

We compare the search setups named below. Local search keeps queries and the index on your host. Cloud search relays visitor queries to an outside vendor. Cloud search can send queries as visitors type or after they submit a search, depending on the setup. We have not tested when requests start relative to cookie consent or assessed how long search logs are kept.

Site search plugins

No paid placement. On your server first, then outside search vendors, then plugins not yet reviewed. Names are alphabetical within each group.

PluginDocumented behaviorReceiving domainsWhen queries leaveVisitor page scopeHow long data is keptBefore consentLinksSource
FiboSearch (local AJAX index)

WordPress.org listing: FiboSearch (Ajax Search for WooCommerce) provides live AJAX suggestions from an index on your WordPress site. Live suggestions still stay on your host in the documented default path; they are not an outside SaaS relay.

On your serverNone in the documented default path.Stays on your serverVisitor pagesNot assessedNot tested
  • None
Native WordPress search (WP_Query)

Core WordPress search runs WP_Query on your WordPress host. The documented default path does not send visitor search terms to an outside search vendor.

On your serverNone in the documented default path.Stays on your serverVisitor pagesNot assessedNot tested
  • None
Relevanssi (local index)

WordPress.org listing: Relevanssi replaces the default search with a relevance-ranked index kept in your WordPress database. The documented default path does not require an outside search vendor.

On your serverNone in the documented default path.Stays on your serverVisitor pagesNot assessedNot tested
  • None
SearchWP (local index)

SearchWP indexes content in your WordPress database and answers visitor searches on your host. The documented product path does not require routing queries through an outside search SaaS. Third-party add-ons you connect yourself are outside this row.

On your serverNone in the documented default path.Stays on your serverVisitor pagesNot assessedNot tested
  • None
AddSearch (search-as-you-type)

AddSearch WordPress docs: the plugin replaces site search with AddSearch. The default option is a search-as-you-type widget; a separate results page is optional. Search API calls use api.addsearch.com (or regional api-eu / api-us hosts), so visitor query terms reach AddSearch.

Outside search vendorapi.addsearch.com, api-eu.addsearch.com, api-us.addsearch.comAs you type (settings vary)Visitor pagesNot assessedNot tested
  • None
Algolia DocSearch (docs embed)

Algolia DocSearch embeds a documentation search UI that queries an Algolia index as visitors type. Browser search requests reach Algolia hosts. This is an embed pattern, not a wordpress.org plugin slug.

Outside search vendor*-dsn.algolia.net, algolia.netAs you type (settings vary)Visitor pagesNot assessedNot tested
  • None
Jetpack Search (Instant / Overlay)

Jetpack Search privacy docs: visitor search requests are submitted to WordPress.com servers. Overlay (Instant Search) shows results in real time as visitors type. Theme or embedded experiences still process queries on WordPress.com when Jetpack Search is on. Jetpack features you leave off are outside this row.

Outside search vendorpublic-api.wordpress.com, wordpress.comAs you type (settings vary)Visitor pagesNot assessedNot tested
  • None
WP Search with Algolia (InstantSearch / Autocomplete)

WP Search with Algolia indexes site content into Algolia and powers Autocomplete and InstantSearch in the browser. Those UIs can send search queries to Algolia application hosts (commonly {APP_ID}-dsn.algolia.net) as visitors type; Algolia docs also describe delaying requests until typing pauses. A native WordPress search-template setup without InstantSearch may wait for submit; this row covers InstantSearch / Autocomplete.

Outside search vendor*-dsn.algolia.net, algolia.netAs you type (settings vary)Visitor pagesNot assessedNot tested
  • None
Better Search

We have not reviewed this plugin's search data path yet.

Not reviewedDocumentation not reviewed yet.Not reviewedNot reviewedNot assessedNot tested
  • None
Ivory Search

We have not reviewed this plugin's search data path yet.

Not reviewedDocumentation not reviewed yet.Not reviewedNot reviewedNot assessedNot tested
  • None

What this table does and does not prove

This table describes the named search setups. It does not show what loads on your site. Local indexes and cloud search can both apply. Instant search can send queries before a visitor submits a search. We have not tested consent timing, and we have not assessed how long search logs are kept. The site scan linked below checks for third-party requests; it does not read your search index files.

Documentation snapshot: Sep 29, 2026. Sources are linked in each reviewed row.

Scan your site for third-party requests

/wp-search-plugin-privacy