Simple answers about every search feature.

FlatSearch.Pro is a search plugin made for Flatsome + WooCommerce stores. It improves the normal Flatsome search box with faster results, smarter matching, better images, cleaner design, and helpful answer cards.

No. Your Flatsome theme stays the same. FlatSearch.Pro improves the existing Flatsome search experience.

No. The plugin uses simple On / Off switches. You can turn on one feature, test it, then turn on the next feature.

Yes. Each module can be turned on or off. The plugin is built so one disabled feature should not break the other features.

Yes. It is made for WooCommerce product search, product images, product prices, product result pages, stock status, and product discovery.

Fast Index Engine builds a ready-made product search list. Instead of asking WooCommerce to search slowly every time, the search box can use a faster route like /?fsp&q=keyword.

Kid-simple: It is like preparing the product book before the shopper asks.

Cloudflare Fast Search lets Cloudflare remember public search answers. When shoppers search the same word again, Cloudflare can answer faster instead of asking WordPress again.

You only need this if your site uses Cloudflare.

It remembers recent search answers in the visitor’s browser. If the same visitor searches again, results can show faster.

It keeps a small ready-to-use product list so search can show results faster without checking the full shop again and again.

It prepares popular searches early, so the first dropdown results can appear faster when shoppers start typing.

It helps product pages open faster after a shopper interacts with a search result. The safer mode warms product page HTML without waking all product page images.

No. They help different layers:

• Fast Index Engine: faster search route.
• Cloudflare Fast Search: CDN cache for repeat public searches.
• Browser Quick Search: visitor browser memory.
• Memory Cache Boost: server memory such as Redis or object cache.
• Product Result Preload: prepares product page HTML.

For most stores, turn on Fast Index Engine first. Then test. Add Cloudflare Fast Search if your site uses Cloudflare. Add preload only if product pages benefit from it.

It helps search understand more than one word. For example, “red apple” should prefer products that match both “red” and “apple”.

It also helps product families match better, such as “glenlivet” and “The Glenlivet”.

Typo Fix helps shoppers when they spell a product name wrongly. For example, “civas” can still find “Chivas”.

It lets results start from the first letter, like “i” for iPhone or “a” for apple.

For big stores, this should work best with Fast Index Engine because one-letter searching can be heavy without an index.

They let shoppers type simple price words such as “under 500”, “above 100”, or “between 20 and 50”.

Example: phone under 500

It lets the live search dropdown also show matching page and blog post titles.

Product results should stay first when product matches exist. Page and blog results should help, not replace good product results.

Yes. The goal is simple: all search modules should apply whether Fast Index Engine is on, Cloudflare Fast Search is on, or the site is using default Flatsome search.

It adds the FlatSearch.Pro look for the search box, result rows, prices, popular searches, recent searches, View More button, and mobile search popup.

It picks the small product photo for each search result, like a tiny picture card. This helps the dropdown avoid loading big product photos.

It is the safety checker for search pictures. If a picture is too big, broken, or unsafe, it swaps it to a smaller safe picture or a simple placeholder.

No. They are related, but different:

• Better Search Images chooses the right small photo.
• Small Image Guard checks if the photo is safe.

Only use it if your site supports Cloudflare Image Resizing. Normal stores should keep it off and use WooCommerce or WordPress thumbnail images.

It dims the page behind the desktop search box so shoppers can focus on the search results.

They show helpful search ideas before typing and remember recent searches, so shoppers have easy suggestions.

It helps the phone keyboard open when the mobile search popup opens. Use it only if your mobile search needs it.

It stops unrelated plugin tasks from joining the search request when they are not needed, so the search can stay lighter.

It keeps the full search results page tidy: available products first, lower price first, and unavailable products lower down.

It controls how many live search results appear while shoppers type. A smaller number feels faster. A larger number shows more choices.

Recommended: 10 to 20.

It controls how many recent searches appear. Use 0 to hide recent searches, or choose a small number like 3, 5, or 8.

Guided Answer Search shows store-made answer cards inside live search. Each card can explain a topic, show product choices, and let shoppers add selected products to cart.

No. It is AI-style, but not a live AI agent. You write and approve every card, so the answers stay safe, accurate, and controlled by your store.

You can use them for many store types:

• Drink store: cocktail recipe or gift guide.
• Beauty store: skincare routine.
• Electronics store: gaming setup or laptop guide.
• Fashion store: outfit guide or size guide.
• Home store: starter kit or care guide.

Normal answer pages can explain something. Guided Answer Search can explain something and connect the answer to products shoppers can buy.

Yes. You can edit the frontend title and bottom link title. For example, a cocktail store can use “Try Popular Cocktail Recipes” and “All Popular Cocktail →”.

Yes. Shoppers can tick related products and add selected products to cart.

Voice Search adds a microphone button to the search box. If the shopper’s browser supports voice input, they can speak instead of typing.

Some speed plugins delay JavaScript. This protection helps the search box still work when shoppers click or type.

It shows quick FlatSearch.Pro status in the WordPress admin bar, so you can check if search features are active.

Analytics helps you understand what shoppers search for, what gets clicked, and which searches may need better products or answer cards.

A Debug Report is a safe support report. It shows plugin version, active modules, search route, Fast Index status, cache status, and environment details.

Clean Uninstall removes plugin data when you delete the plugin. Leave it off if you may reinstall the plugin later.

It should use /?fsp&q=keyword. Fast Index builds the answer. Cloudflare can cache repeat public searches.

It should still use /?fsp&q=keyword, but the answer comes from your website server instead of Cloudflare cache.

It should use the default Flatsome live search route, usually admin-ajax.php. The default bridge should still apply important modules.

Search results, scripts, and helper data can be saved by Redis, page cache, Cloudflare, or the browser. Clearing cache makes sure shoppers get the newest behavior.

Clear Object Cache or Redis, purge page cache, purge Cloudflare, and test in Incognito. If needed, clear browser localStorage too.

Check Search From First Letter, Page & Blog Search, and Fast Search Starter. The plugin should not force an empty answer before the safe search bridge has a chance to respond.

Rebuild the product list, clear cache, and test again. Fast Index should apply the same important modules: Better Word Matching, Typo Fix, Page & Blog Search, Price Search Words, and Search From First Letter.

Check whether it is a first-time uncached request or a repeated cached request. A cold origin request can be slower than a Cloudflare HIT. Repeat the same search and compare.

Turn on Better Search Images and Small Image Guard. Then clear cache. If WordPress never generated thumbnails for those images, regenerate thumbnails.

Better Search Images should use WooCommerce or WordPress thumbnail sizes. Keep Advanced Cloudflare Image Resizing off unless your site supports it.

Use safe HTML-only preload. It should warm product page HTML without inserting the HTML into the page and without loading product page images.

Check the PHP error log or wp-content/debug.log. If the fatal error mentions FlatSearch.Pro, send the exact line to support. If it mentions another plugin, FlatSearch.Pro may only have triggered a cached error page.