WPIntell

Source evidence

API key not recognized

WP Search with Algolia · support · 2026-03-25T18:28:00+00:00

mixedsentiment
mediumseverity
0.84relevance
3replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

3 / 32 rows with source links

9.4% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

29 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
marcoronit resolved
We are an academic library. We have installed WP Search with Algolia in our library’s WordPress website a few days ago, to enable AI-based search in our website. We’ve entered the Search API key, but get this message and can’t proceed: It looks like your search API key is wrong. Ensure that the key you entered has only the search capability and nothing else. Also ensure that the key has no limited time validity. Algolia’s support confirmed that we have entered the correct Search API key in the WP Search with Algolia integration config. We’d appreciate any help. This topic was modified 2 months ago by marcoronit . The page I need help with: [ log in to see the link] Hi @marcoronit We’re monitoring this overall issue at https://github.com/WebDevStudios/wp-search-with-algolia/issues/537 and are doing some extra review and testing/confirmation before we push out a change for everyone. Hoping to get this finished up as soon as possible. If you’re not wary of editing code yourself, I can point you to where the main change is going to be at, in the meantime, before we do the full release to everyone. Hi Michael, Thanks for your reply. We prefer not to mess with the code 🙂 We’ll follow the GitHub thread and wait for the fixed version release. We pushed out 2.11.2 yesterday which should fix this issue. Please upgrade when you have the moment.

Comments

3 shown
Michael Beckwith 2026-03-25T18:47:00+00:00

Hi @marcoronit We’re monitoring this overall issue at https://github.com/WebDevStudios/wp-search-with-algolia/issues/537 and are doing some extra review and testing/confirmation before we push out a change for everyone. Hoping to get this finished up as soon as possible. If you’re not wary of editing code yourself, I can point you to where the main change is going to be at, in the meantime, before we do the full release to everyone.

marcoronit 2026-03-25T19:22:00+00:00

Hi Michael, Thanks for your reply. We prefer not to mess with the code 🙂 We’ll follow the GitHub thread and wait for the fixed version release.

Michael Beckwith 2026-03-27T18:54:00+00:00

We pushed out 2.11.2 yesterday which should fix this issue. Please upgrade when you have the moment.