Everything you need to know about faster WooCommerce search.
Clear answers about Fast Index, search accuracy, caching, images, universal integration, Quick Add, Guided Answer Search and production troubleshooting.
FlatSearch.Pro began as a deeply optimized Flatsome search solution and now also provides its own theme-independent WooCommerce search surface.
Search infrastructure built around ecommerce intent.
FlatSearch.Pro combines retrieval, relevance, presentation and shopping actions instead of treating search as a simple WordPress text box.
Retrieve faster
Fast Index, browser reuse, shared cache and optional Cloudflare edge delivery reduce repeated search work.
Match smarter
Better Word Matching, Typo Fix, multi-word matching and Price Search Words help shoppers find the intended products.
Convert sooner
Product images, prices, stock context, Quick Add and Guided Answer products can shorten the path from search to cart.
What has FlatSearch.Pro achieved in production testing?
These figures are measurements from our production test environment and should be treated as engineering evidence rather than guaranteed latency for every store.
Basic Questions
What FlatSearch.Pro is, what it requires and where it fits into WooCommerce.
What is FlatSearch.Pro?
FlatSearch.Pro is a WooCommerce commerce-search solution designed to improve product retrieval, relevance, search UX and shopping actions.
It includes Fast Index search, search-accuracy modules, product images, caching, search analytics and optional commerce features such as Quick Add and Guided Answer Search.
Is FlatSearch.Pro only for Flatsome?
No.
Flatsome remains the most deeply optimized and production-tested theme integration, but FlatSearch.Pro now also provides its own theme-independent search form and search-icon surface for WooCommerce.
Does FlatSearch.Pro replace WooCommerce?
No. WooCommerce remains the commerce platform and source of product, price, image and stock data.
FlatSearch.Pro improves how that catalogue is searched and presented.
Do I need coding knowledge?
Normal configuration is managed through plugin settings and module controls.
Custom themes, custom product types or complex optimization stacks may require ordinary WordPress integration testing.
Can features be turned on and off independently?
Yes. FlatSearch.Pro is modular.
Speed, accuracy, design and commerce modules are designed to coexist without requiring every feature to be enabled.
Does FlatSearch.Pro require Cloudflare?
No.
Cloudflare is an optional acceleration layer. Fast Index and core WooCommerce search can operate without Cloudflare.
Does it require Redis or Object Cache Pro?
No.
Persistent object caching can reduce repeated server work, but it is not required for search correctness.
Speed & Fast Index FAQ
How the current search engine reduces repeated database, PHP, browser and network work.
What is Fast Index Engine?
Fast Index Engine prepares commerce-search data before a shopper searches.
Instead of relying on a broad WordPress/WooCommerce catalogue scan for each uncached request, FlatSearch.Pro can search the prepared index.
What search endpoint does the current architecture use?
The current canonical browser search transport uses the FlatSearch.Pro search endpoint, for example:
/fsp-search.js?q=chivas&n=20
The exact URL can also include version/cache identity parameters.
Does FlatSearch.Pro send a request for every letter I type?
The current architecture is designed not to.
FlatSearch.Pro can display useful local/browser information while typing and coalesce transient prefixes before giving the settled query canonical network ownership.
What does “single search owner” mean?
It means multiple search modules should not independently send competing network requests for the same query.
One authoritative transport owns the settled search request.
Why doesn’t FlatSearch.Pro abort old requests anymore?
The current no-abort coordination allows an already-started canonical request to finish instead of deliberately producing a cancelled browser network row.
Sequence and stale-result guards prevent an old result from replacing a newer query on screen.
What is Browser Quick Search?
It reuses suitable result information in the visitor’s browser so repeated interactions may appear with little or no new search work.
What is Repeated Search Cache?
It allows commonly repeated normalized queries to reuse valid search answers rather than recomputing the same result every time.
What is Memory Cache Boost?
It uses available persistent server caching such as Redis/object cache to reduce repeated server-side work.
What is Search Cache Warm-Up?
Warm-up prepares selected common search terms in the background before a shopper needs them.
It should be used selectively rather than trying to warm every possible query.
What is Product Result Preload?
It can prepare likely product navigation after the shopper interacts with search.
The safe approach is to avoid unnecessarily waking an entire product page’s image and frontend asset tree.
Should I enable every speed feature?
Not automatically.
Start with Fast Index and verify search accuracy. Add browser/shared/edge acceleration according to the infrastructure your store actually uses.
Search Accuracy FAQ
How FlatSearch.Pro interprets real customer search language.
What is Better Word Matching?
Better Word Matching improves relevance when a product title contains several meaningful terms.
It helps product families and multi-word searches behave more naturally.
What is Typo Fix?
Typo Fix helps shoppers reach the intended product when they make common spelling mistakes.
Example: civas can still lead to Chivas products.
What is Multi-Word Matching?
It coordinates queries containing several words so useful terms can contribute together to relevance.
Example: macallan sherry
What is Search From First Letter?
It allows useful discovery from very short prefixes.
The current frontend can provide immediate perceived feedback while avoiding unnecessary canonical network requests for every intermediate character.
What are Price Search Words?
Price Search Words interpret common shopping-budget phrases.
- whisky under 300
- wine above 100
- between 100 and 250
What is Page & Blog Search?
It allows relevant published pages and posts to participate in live search where enabled.
Product discovery remains the main commerce objective when strong product matches exist.
Do accuracy modules still work when Fast Index is enabled?
That is the intended architecture.
Fast Index should accelerate retrieval without redefining the search meaning created by the relevant accuracy modules.
Search UX & Images FAQ
How product results remain visually fast as well as technically fast.
What is Search Box Design?
It controls FlatSearch.Pro’s supported result presentation including product rows, prices, search suggestions, View More behavior and supported mobile search presentation.
What is Better Search Images?
It helps choose image URLs appropriate for a compact search dropdown instead of unnecessarily requesting full-size product images.
What is Small Image Guard?
It protects search presentation when an image URL is missing, unsuitable or unnecessarily large.
What is viewport-aware image admission?
The current search frontend prioritizes the thumbnails actually visible inside the dropdown viewport.
Off-screen search-result images stay deferred until the shopper scrolls them into view.
Is this the same as normal top-to-bottom lazy loading?
No.
The goal is to admit the current visible thumbnail batch together so the search dropdown feels complete quickly, rather than visibly cascading one image at a time from top to bottom.
Why not preload every product image?
Because a 20-result dropdown does not mean the visitor can see all 20 products at once.
Loading hidden thumbnails wastes network capacity and can make first-use search feel slower.
Should I use Cloudflare Image Resizing?
Only when your infrastructure intentionally supports it.
Avoid repeatedly transforming an image that is already appropriately sized for the dropdown.
What is Background Dimmer?
It visually reduces page distraction behind supported search interfaces so attention remains on search results.
What are Popular & Recent Searches?
They provide useful discovery terms and recent-search context around the live search experience.
Commerce & Conversion FAQ
Features that help shoppers move from discovery to cart.
What is Quick Add?
Quick Add lets eligible WooCommerce products expose an Add to Cart action directly from search.
This can shorten the path between high-intent product discovery and cart.
Does Quick Add load on every page even when disabled?
The current lightweight architecture separates the heavier Quick Add presentation assets so they can remain out of the normal frontend transfer path when the feature is disabled.
Does Quick Add support every custom WooCommerce product type?
Standard eligible products can use Quick Add.
Booking, subscription, bundle, auction or heavily customized product types may require their normal product-specific configuration flow and should be tested separately.
What is Guided Answer Search?
Guided Answer Search displays store-controlled explanatory cards associated with selected WooCommerce products.
It can guide the shopper and connect the answer directly to products.
Is Guided Answer Search a live AI agent?
No.
Guided Answer content is created and controlled by the store rather than being generated unpredictably during every search.
Can shoppers select multiple products from a Guided Answer?
The supported Guided Answer workflow can present selectable related products and allow selected items to move toward cart.
What is Search Page Sorting?
Search Page Sorting controls supported product ordering on the full WooCommerce results page after the shopper submits the search.
Themes & Universal Search FAQ
How FlatSearch.Pro works beyond its original Flatsome integration.
What does “theme-independent search surface” mean?
It means FlatSearch.Pro can provide its own search interface instead of requiring the active theme’s native autocomplete component.
What shortcode creates the universal search form?
Use:
[flat_search_pro_form]
What shortcode creates the universal search icon?
Use:
[flat_search_pro_icon]
Does universal mode require Flatsome JavaScript?
The FlatSearch-owned universal surface is designed not to depend on Flatsome’s native live-search JavaScript for the search UI itself.
Does that mean every WooCommerce theme is already certified?
No.
Custom themes and builders can still affect width, spacing, z-index, header positioning and mobile presentation.
The search surface is independent; visual compatibility still deserves normal testing.
Is Flatsome still supported?
Yes.
Flatsome remains the longest-tested and deepest theme integration while universal integration expands the product beyond Flatsome-only deployment.
Cache, Cloudflare & Performance FAQ
Understand browser cache, server cache and edge-cache behavior without confusing one layer for another.
What does Cloudflare Fast Search do?
It allows valid public search responses to be reused at Cloudflare where configured.
That can move repeated public searches closer to the shopper and reduce repeated origin work.
Does one person’s cached search help another visitor?
A valid shared public edge cache can be reused independently of a specific visitor’s browser, subject to the configured cache identity and expiration policy.
What is the difference between browser cache and Cloudflare cache?
- Browser cache: belongs to that browser/device.
- Shared/edge cache: can reuse public results across visitors when valid.
- Origin/Fast Index: builds the result when no suitable cached response exists.
Why can the first search after clearing cache be much slower?
A first request may be a Cloudflare MISS and require an origin fill.
Browser-visible cold latency can therefore include CDN/origin network time in addition to the internal FlatSearch search computation.
Does a 600 ms cold MISS mean Fast Index took 600 ms?
Not necessarily.
Internal FlatSearch execution and external CDN/origin-fill latency should be measured separately before diagnosing SQL or ranking performance.
Why should I test the same query twice?
The first request tells you about the cold path.
The repeat request tells you whether browser/shared/edge reuse is behaving correctly.
Is WP Rocket compatible?
FlatSearch.Pro can coexist with WP Rocket, but aggressive JavaScript delay or rewriting should be tested whenever those settings change.
What is Delay JS Search Protection?
It helps preserve FlatSearch.Pro interaction when a performance plugin delays frontend JavaScript execution.
What cache should I clear after an update?
Clear only the relevant layers:
- page/server cache when frontend assets changed,
- persistent object cache when required,
- Cloudflare where relevant,
- then test from Incognito to avoid stale browser assets.
How many dropdown results should I use?
Around 10–20 is a practical range for many stores. Viewport-aware images allow additional off-screen rows to remain visually inexpensive until they are actually viewed.
What does Voice Search do?
Voice Search adds microphone-based input where the shopper’s browser/device supports it.
What does Search Analytics show?
Analytics can help identify popular search terms, search demand, weak discovery areas and queries that deserve better catalogue or Guided Answer coverage.
What is a Debug Report?
It collects useful FlatSearch.Pro environment, module and readiness information for troubleshooting.
What is a HAR file?
A HAR is a browser network capture. It is useful for inspecting request timing, cache status, duplicate requests, cancellations and image behavior.
What is Clean Uninstall?
Clean Uninstall can remove FlatSearch.Pro options, caches and index-related plugin data when the plugin is deleted.
Troubleshooting FAQ
Diagnose the actual layer before changing search ranking or architecture.
Search shows “No products found” too early.
Check Fast Index readiness, first-letter behavior and active accuracy modules.
Clear relevant search cache and test again from Incognito.
Fast Index results do not match expected search results.
Rebuild Fast Index, clear relevant cache and verify Better Word Matching, Typo Fix, Price Search Words, multi-word matching and content-search settings.
I see several /fsp-search.js requests while typing.
The current architecture is intended to coalesce transient typing.
Check for stale frontend JavaScript, duplicate plugin versions, old page cache or another autocomplete system competing for the same input.
I see red cancelled FlatSearch requests in DevTools.
The current no-abort runtime should not deliberately cancel a started canonical FlatSearch request.
Purge stale frontend assets and confirm the current FlatSearch runtime is actually loaded.
Search is slower immediately after clearing all cache.
Check whether the search response is a Cloudflare MISS.
Cold edge-to-origin fill can be much slower than a warm edge HIT even when the internal search engine itself is healthy.
Search images seem to load too many requests.
Confirm the current viewport-aware image runtime is active.
Visible search rows should receive image priority while hidden off-screen rows remain deferred.
Search images are grey or broken.
Check Better Search Images and Small Image Guard, then inspect the actual thumbnail URL.
Also confirm another image optimization service is not rewriting an already valid thumbnail incorrectly.
Product Result Preload creates too many requests.
Check whether another plugin is preloading the same product pages or images.
Use the least aggressive preload behavior that still improves real navigation.
Search stopped working after changing WP Rocket settings.
Re-test JavaScript delay/defer first.
If an optimization setting directly causes the failure, validate that optimization before changing FlatSearch.Pro’s search algorithm.
The frontend still looks like the old version after updating FlatSearch.Pro.
Purge relevant page/server cache, persistent object cache where appropriate, Cloudflare where appropriate, and test from a fresh Incognito window.
WordPress reports a critical error.
Inspect the PHP error log or:
wp-content/debug.log
The exact fatal-error file and line are more useful than the generic “critical error” page.
When should I send a HAR to support?
Send a HAR when the issue involves:
- slow search timing,
- duplicate search requests,
- cancelled requests,
- Cloudflare HIT/MISS behavior,
- image loading,
- cold versus repeat search differences.
Which features should I start with?
Start with a stable core and add acceleration according to catalogue size and infrastructure.
Small / standard store
Start with Fast Index, Search Box Design, Better Search Images, Better Word Matching and Typo Fix.
Medium catalogue
Add Instant Result, Browser Quick Search, Repeated Search Cache and appropriate first-letter / multi-word behavior.
Large catalogue
Add persistent object cache and optional Cloudflare Fast Search after Fast Index accuracy is confirmed.
Content-heavy store
Add Page & Blog Search and Guided Answer Search where editorial content helps the purchase journey.
High-intent store
Add Quick Add and optimized result presentation where products can safely move directly from search to cart.
Non-Flatsome theme
Use the FlatSearch-owned universal form/icon surface and validate your theme’s header, mobile layout and stacking behavior.
Search should be easy for shoppers — and diagnosable for engineers.
Use the documentation for setup, the compatibility guide for infrastructure questions, and a Debug Report + HAR when deeper investigation is needed.