AI summary or FAQ generation fails with an error
Fix RankReady summary and FAQ generation errors: check the active provider's key, provider credit, DataForSEO for FAQs, and outbound request blocks.
Last updated September 27, 2026
The most common reason a generation fails is simple: the active AI provider has no valid key, or the key you pasted belongs to a different provider than the one selected. AI Summaries and the FAQ Generator are the only features that need a key. Open Settings, choose your provider, paste its matching key, and save.
Check the key and the active provider first
RankReady is provider-agnostic. It uses whichever provider you set as active, not a fixed one. A failure here almost always means one of three things:
- No key is saved for the active provider.
- The key is wrong, expired, or was revoked at the provider.
- The key is valid but belongs to a different provider than the one selected. An OpenAI key will not work if Anthropic Claude is the active provider.
Go to Settings, confirm which provider is active (OpenAI, Anthropic Claude, Google Gemini, or DeepSeek), and make sure the key in that field was issued by that same provider. Save, then try generating again. If the block previously said a key was needed, that message should be gone once a valid key is in place.
The provider account is out of credit or rate-limited
The request goes from your site to the provider using your own account. If that account has run out of credit, hit a spending cap, or is being rate-limited, the provider rejects the call and generation fails. Open your provider dashboard and check the account balance and usage limits. Add credit if needed, wait a short while if you are being rate-limited, then try again. You can also switch to a different provider in Settings and use a key you know is funded.
DataForSEO is not the cause of a failed FAQ
A common wrong guess. The FAQ Generator uses real People Also Ask questions from DataForSEO when you have connected it, and falls back to the model’s own question phrasing when you have not. Missing DataForSEO credentials make the questions less grounded; they do not make generation fail. The only credential a hand-run FAQ needs is the key for your active AI provider, exactly as for a summary.
DataForSEO is a hard requirement in one place only: RankReady Pro’s automatic FAQ generation on publish, which stays idle unless both an AI key and DataForSEO credentials are saved. If that is what is not running, check both.
If DataForSEO is connected and you see a credentials or authentication error from it specifically, the login and password pair is wrong or the account is out of balance. Re-paste both in Settings. DataForSEO sends only the focus keyword, never your article text.
A server timeout or a security plugin is blocking the request
Because the call travels from your server out to the provider, anything that blocks outbound requests will stop generation. A firewall, a security plugin, or a strict host can block the connection, and a slow response can hit a server timeout. If the key is correct and the account is funded, check any security or firewall plugin for a rule blocking outbound HTTP, and ask your host whether external API calls are allowed. Raising the PHP execution time on the server can also help with timeouts.
Very long content can exceed a provider limit
A very long post can push past the provider’s input limit and cause the call to fail. To test whether length is the cause, run generation on a short post. If the short post succeeds and the long one fails, length is the issue. Trim the content or generate on a shorter draft to confirm.
Verify the fix
After making a change, generate a summary or FAQ on a single post and confirm the output appears on that post. The generate control should complete without an error, and the block should no longer say a key is needed. Note that Article schema only appears once a summary exists on the post, so generating a summary is also what makes that schema output.
Related reading
- Do you need an AI API key for RankReady?
- Which AI provider to choose, and what it costs
- API key will not save in WordPress