Diagnose the right layer. Fix the right problem.
Get technical help for WooCommerce search relevance, Fast Index, frontend transport, images, caching, Cloudflare, universal search integration, Quick Add and Guided Answer Search.
The fastest support request tells us exactly what you searched, what you expected, what actually happened, and which layer handled the request.
Start with the symptom.
Different symptoms belong to different parts of the search architecture. Choosing the closest category makes investigation faster.
Search is slow
Fast Index latency, Cloudflare HIT/MISS, cold origin, object cache, browser timing or image-loading delay.
Results are wrong
Better Word Matching, Priority Typo Fix, multi-word matching, price intent, first-letter discovery or missing products.
Results do not display
Search surface, settled-query transport, stale JavaScript, modal/dropdown state or competing autocomplete code.
Images are missing or slow
Better Search Images, Small Image Guard, viewport image admission, WooCommerce thumbnails or CDN rewriting.
Quick Add / Guided Answer
Search-to-cart actions, guided products, answer aliases, result cards or special WooCommerce product behavior.
Theme / plugin compatibility
Flatsome, universal search surface, page builders, WP Rocket, LiteSpeed, Cloudflare, Redis/Object Cache or custom JavaScript.
View More / full results
Result-page behavior, sorting, stock handling, cleanup mode and handoff from autocomplete to WooCommerce results.
Settings / Fast Index
Settings not saving, index rebuild problems, module controls, Tools & Reports or diagnostics.
License / billing
Freemius activation, plan, trial, renewal, invoice, cancellation or refund-related questions.
Give us a reproducible test.
A concise technical report is usually more useful than a long description without the failing query or evidence.
- FlatSearch.Pro version
- Exact search query or failing action
- Expected result
- Actual result
- Affected page or product URL
- Screenshot for visual problems
- Debug Report for technical issues
- Incognito HAR for performance/network issues
Contact FlatSearch.Pro
Technical support, bugs, compatibility, sales and license questions.
Identify the failing layer before changing settings.
Search relevance, browser transport, cache state, origin execution and product images are separate systems.
Search Meaning
Does the expected product rank and appear?
Browser Transport
Did one canonical settled query execute correctly?
Cache Layer
Browser reuse, shared cache or Cloudflare HIT/MISS.
Origin / Fast Index
Inspect uncached server-search execution.
Images & UI
Verify visible thumbnails and final dropdown presentation.
Send the smallest set of evidence that proves the problem.
| Problem | Please send | What we inspect | Priority |
|---|---|---|---|
| Search takes too long | Incognito HAR, exact query, Debug Report, Fast Index status and Cloudflare HIT/MISS where applicable. | Browser scheduling → canonical request → CDN → origin → response → images. | High |
| Wrong result ordering | Exact query, expected product URL, screenshot and active accuracy modules. | Better Word Matching, typo logic, multi-word matching, price intent and Fast Index data. | High |
| Result does not display | Query, HAR, screenshot/video and browser console error if present. | Canonical transport, stale-response protection, frontend rendering and competing autocomplete scripts. | High |
| Product missing | Query, expected product URL and Fast Index status. | Indexed product data, search eligibility and active relevance modules. | High |
| Image missing / slow | Product URL, screenshot, relevant image request and image/CDN configuration. | Thumbnail source, search URL policy, CDN transform and viewport admission. | Medium |
| Universal search layout | Theme name, screenshot, placement and relevant custom CSS/JS. | Theme leakage, form markup, modal behavior and frontend presentation. | Medium |
| Quick Add | Product URL/type, screenshot and console/network error where present. | Product eligibility, cart endpoint and conditional Quick Add runtime. | Medium |
| Guided Answer | Card title, trigger alias, selected products and frontend screenshot. | Stored card configuration, trigger matching and connected commerce actions. | Medium |
| License / billing | Purchase email, plan name and relevant Freemius order/license reference. | Subscription, license and activation record. | Account |
Debug Report tells us the configuration. HAR tells us what happened.
Create a Debug Report
Open FlatSearch.Pro’s Tools & Reports area and generate the available diagnostic report.
- FlatSearch.Pro version
- Active modules
- Fast Index state
- Relevant cache state
- WooCommerce / WordPress environment
- Search architecture diagnostics
Record an Incognito HAR
Open a new Incognito/private browser window, open DevTools → Network, reproduce the issue once, then export the HAR.
- Search request timing
- Canonical search endpoint
- Cloudflare HIT/MISS
- Response status
- Duplicate requests
- Cancelled requests
- Product image timing
Try targeted fixes — not a full-site reset.
Broad cache purges and module changes can destroy evidence. Start with the smallest action relevant to the symptom.
Test Incognito first
This helps separate a current production problem from stale browser cache or local search state.
Rebuild Fast Index only when relevant
Rebuild when product/search data appears stale or incomplete—not automatically for every frontend issue.
Check HIT / MISS before purging
For Cloudflare performance problems, capture the current state before destroying the cache evidence.
Check optimization exclusions
If search fails only after JavaScript optimization, test the relevant WP Rocket/LiteSpeed/delay setting instead of disabling all optimization permanently.
Inspect the actual image request
Determine whether the source thumbnail, Cloudflare transform or search-image policy owns the failure before regenerating every thumbnail.
Change one variable at a time
Module-by-module testing is useful only after a reproducible baseline exists.
Compare the same search path with the same cache state.
FlatSearch.Pro has measured production references that help us distinguish normal cold-cache behavior from a regression.
Flatsome is the deepest-tested integration — not the only search surface.
Flatsome
Support can investigate Flatsome header search, mobile search, result presentation and relevant theme-specific behavior.
Other WooCommerce themes
FlatSearch.Pro provides its own search form and icon so deployments do not have to depend on a theme’s native autocomplete engine.
Custom integrations
Bespoke headers, builders, unusual product types and custom JavaScript may require presentation-level compatibility work.
What FlatSearch.Pro support covers.
FlatSearch.Pro product support
- Fast Index setup and search retrieval
- Better Word Matching and accuracy modules
- Priority Typo Fix
- Price Search Words
- Page & Blog Search
- FlatSearch universal search interface
- Flatsome search integration
- Search images and viewport admission
- Browser/shared cache behavior
- Cloudflare Fast Search integration
- Redis / object-cache integration
- Quick Add
- Guided Answer Search
- Debug Reports and HAR investigation
- Licensing / Freemius questions
Custom development / unrelated systems
- Redesigning an entire theme unrelated to search
- Building unrelated WooCommerce functionality
- Repairing a broken hosting environment
- Malware or compromised-site cleanup
- Repairing unrelated third-party plugin defects
- Writing the store’s full product catalogue
- Permanent website administration
- Bespoke integrations not included in FlatSearch.Pro
From report to resolution.
Reproduce
We establish the exact query, action and environment needed to reproduce the problem.
Classify
Determine whether the failing owner is relevance, transport, cache, origin, images, frontend or third-party integration.
Correct
Apply the smallest safe fix or configuration change needed for the identified layer.
Revalidate
Confirm desktop, mobile and relevant cold/warm search behavior without introducing a regression elsewhere.
Need help before or after purchase?
Before purchase
Ask about plans, current capabilities, architecture, compatibility, deployment requirements or the live production demo.
License activation
Get help with activation, website limits, account matching or Freemius license status.
Billing
Ask about trial status, renewal, invoice, upgrade, downgrade, cancellation or refund policy.
Common troubleshooting questions.
What is the fastest way to get technical support?
Send the FlatSearch.Pro version, exact failing query/action, expected result and actual result.
Add a Debug Report for plugin/configuration problems and an Incognito HAR for timing, cache, request or image problems.
Should I clear every cache before contacting support?
Not always.
For performance issues, the existing HAR and cache headers can be valuable evidence. Capture the failing state first, then purge only the layer relevant to the test.
What if search works in Incognito but not in my normal browser?
That strongly suggests browser-side state, stale assets or another browser-specific factor.
Capture the normal-browser and Incognito difference before broadly changing server search settings.
What if Cloudflare shows an old search result?
First inspect whether the request is a HIT, MISS and its cache age.
If the edge is clearly serving stale public search data, purge the relevant cache and repeat the exact same query.
Why can the first search be slower than the second?
A first request can be a cold browser/cache/Cloudflare/origin path.
A repeat query can use browser reuse, shared cache or a Cloudflare HIT, so cold and warm requests should be evaluated separately.
Why do I see /fsp-search.js in DevTools?
It is part of the current canonical FlatSearch.Pro search transport.
A normal settled query should not create an unnecessary network request storm for every intermediate character.
I see a cancelled search request. Is that expected?
The current FlatSearch.Pro no-abort coordination does not deliberately cancel a started canonical search request.
Send an Incognito HAR so we can identify whether stale assets, another script or browser/navigation behavior owns the cancellation.
My result text appears but product images are slow. Is search itself slow?
Not necessarily.
Result retrieval and thumbnail delivery are separate layers. Current viewport-aware image admission prioritizes visible product images and defers hidden rows.
What if only the universal search form has a layout problem?
Send the theme name, screenshot and relevant custom CSS/JS information.
A search-surface presentation issue can usually be investigated without changing Fast Index ranking or cache semantics.
Is FlatSearch.Pro only supported on Flatsome?
No.
Flatsome remains the deepest-tested theme integration. FlatSearch.Pro also provides its own theme-independent WooCommerce search form and search icon surface.
Do I need Cloudflare or Redis before asking for support?
No.
Cloudflare and persistent object caching are optional acceleration layers. Core FlatSearch.Pro search does not require either one to return results correctly.
Can support recommend the best configuration for my store?
Yes. Tell us your WooCommerce catalogue size, theme, hosting environment, page-cache setup, object-cache status, Cloudflare status and the search problem you are trying to solve.
Should I send my WordPress administrator password?
No. Do not send permanent passwords through the support form.
If temporary access becomes necessary, support can request an appropriate temporary-access workflow.
Show us the failing query and the failing layer.
With a reproducible query, Debug Report and the right HAR capture, we can investigate search behavior without guessing or changing unrelated modules.