Skip to main content

Verify your setup

Work down this list after publishing. Each step isolates one layer, so the first one that fails tells you where the problem is.

1. The script loaded​

Open your published URL and the browser console.

You should see one large green line:

[wf-algolia] Script initialized with App ID: YOUR_APP_ID at 2026-08-04T09:12:44.031Z

Then type window.WfAlgolia and press Enter. You should get an object.

If you get undefined, the script never ran. In order of likelihood: the tag is in Head instead of Footer, a Content Security Policy is blocking cdn.jsdelivr.net, or type="module" is missing so the browser rejected the file on its first import.

window.WfAlgolia.version is not a reliable version check

It returns a hard-coded 1.0.0 regardless of which build is actually loaded. Use it to confirm the object exists, not to identify the release. To check the real version, look at the src URL on your script tag.

2. The credentials work​

  1. Open DevTools → Network.
  2. Filter by algolia.net.
  3. Trigger a search.

A 200 means your App ID and key are good. A 401 or 403 means they are not — recheck and , and confirm the key you pasted is the Search-Only key with the search ACL.

No request at all means the script never got as far as querying. Go back to step 1, then check that your search input actually carries wf-algolia-element="search-input".

3. The required attributes are present​

Every solution page opens with a Required card. A missing attribute from that card is the single most common cause of "nothing happens".

4. Read the console warnings​

The script warns rather than throwing when an element it expects is missing, so the page keeps working and the warning is the only signal. Every message is prefixed [wf-algolia].

Initialization failures are the exception: they are caught and logged as [wf-algolia] Initialization failed: followed by the underlying error.

The full list is in Common issues.

5. Preview versus published​

WF-Algolia runs in both. If it works in Preview but not on the published site:

  • Confirm custom code is enabled on the published domain, not just the staging one.
  • If you have set a CSP, allow both https://cdn.jsdelivr.net and https://*.algolia.net.

Things to check in Algolia, not in Webflow​

Some symptoms are configuration on Algolia's side, and no attribute will fix them.

SymptomWhere to look
Index name not foundDashboard → Indices
401 / 403 on every queryDashboard → API Keys → check the ACL
A filter renders but never narrows resultsDashboard → Configuration → Facets — the field must be declared for faceting
Filter search box does nothingThe facet must be searchable, not filter-only
Sorting returns nothingDashboard → Replicas — the replica must exist and be named exactly as in your option value
Recommendations are emptyDashboard → Recommend — the model has to be trained before it returns anything
A numeric range never filtersThe field must be stored as a number, not a string

Still stuck​

Go to Common issues.