This page covers the most common issues encountered when using Supercharger and how to resolve them.
AI Content Is Not Appearing on Posts
Check that the module is enabled.
Go to Supercharger → Modules and confirm the module you expect to see is toggled on.
Check that the post type is included.
Go to Supercharger → Settings → Content and verify that the post type is selected.
Check that the post has been processed.
Open the post in the Gutenberg editor and look at the Supercharger sidebar. If it shows “Pending” or “Not indexed,” the post hasn’t been processed yet. Click Regenerate or wait for the next cron run.
Check the Logs.
Go to Supercharger → Tools → Recent Activity and look for errors related to the post or module. An API error will usually explain why generation failed.
API Key Error / Invalid API Key
- Go to Supercharger → Settings → API.
- Double-check that the key is entered correctly with no leading or trailing spaces.
- Verify the key is active in your AI provider’s dashboard.
- If the key was recently created, wait a few minutes — new keys sometimes take time to become active.
- Test the key by saving settings; Supercharger will validate the key on save.
Recommendations Not Showing
Verify the vector index is populated.
Go to the Dashboard and check that a significant number of posts are listed as Indexed. If the count is 0 or very low, indexing may not have run.
Check that the OpenAI API key is configured.
Semantic recommendations require an OpenAI API key for embeddings. Go to Supercharger → Settings → API and confirm the OpenAI key is present.
Check the similarity threshold.
If the threshold is too high, no posts will pass the minimum score. Try lowering it in the AI Recommendations module settings.
Check that enough posts are indexed.
If your site has fewer than 5–10 indexed posts, there may not be enough content to find meaningful recommendations.
Indexing Is Stuck or Not Progressing
Check WordPress cron.
On sites with low traffic, WordPress cron may not fire regularly. Trigger a manual cron run from Supercharger → Tools → Trigger Indexing Cron and see if progress is made.
Check for API rate limits.
If you’re rate-limited by your AI provider, indexing will pause and retry. Check the Logs for rate limit errors. You may need to upgrade your API plan for faster indexing.
Set up a real server cron job.
See [Performance & Best Practices](08-performance.md) for instructions on replacing WordPress cron with a true server cron job.
Module Appears on Wrong Posts or Post Types
Go to the module’s settings and confirm that the Post Types setting is correctly configured. Some modules only apply to certain post types by default.
The Supercharger Sidebar Is Not Visible in Gutenberg
- Make sure you’re editing a post (not a page, unless pages are a supported post type for the module).
- Check that the Supercharger sidebar isn’t collapsed. Click the icon in the Gutenberg toolbar.
- If the sidebar doesn’t appear at all, try deactivating and reactivating the plugin.
- Check your browser console for JavaScript errors that might indicate a conflict with another plugin.
A Module Appears Broken or Unstyled
- Clear your browser cache and reload.
- Go to Supercharger → Tools → Clear Cache and reload.
- If you’re using a caching plugin (WP Rocket, W3 Total Cache, etc.), clear its cache as well.
- Check for CSS conflicts with your theme by temporarily switching to a default WordPress theme (Twenty Twenty-Four) and seeing if the issue persists.
Pro Modules Are Locked / Not Available
- Verify that the Pro plugin is installed and activated (not just the free version).
- Go to Supercharger → Settings → License and confirm the license key is entered and shows as active.
- If the license was recently purchased, try clicking Re-verify License.
- Contact support if the license still shows as invalid.
Contacting Support
If the issue isn’t resolved by the steps above:
- Go to Supercharger → Tools → Recent Activity and note any relevant error messages.
- Check the system status on the Dashboard.
- Visit the Supercharger support page and submit a ticket with:
- A description of the issue
- Your WordPress and PHP versions
- The relevant log entries
- Steps to reproduce the problem