This page covers the practical steps for managing your Supercharger content index.
Checking Index Status
The current state of your index is always visible on the Dashboard. For a more detailed health check, go to Supercharger → Tools → Check Index Health.
The health check verifies:
- That all required database tables exist
- The total number of indexed posts
- Whether there are any pending or failed items
Adding or Removing Post Types
To change which post types are included in the index:
- Go to Supercharger → Settings → Content.
- Check or uncheck post types.
- Click Save Settings.
After saving:
- Newly added post types will be queued for indexing automatically.
- Removed post types will have their embeddings deleted from the database.
Re-indexing a Single Post
If a post’s embeddings are stale or incorrect:
- Open the post in the Gutenberg editor.
- Open the Supercharger sidebar.
- Click Regenerate.
Alternatively, from Supercharger → Tools, enter the post ID and click Re-index Post.
Full Re-index
A full re-index clears all existing embeddings and re-processes every post. Use this when:
- You switch to a different embedding model
- You suspect the index is corrupted
- You’ve made major content changes across the site
To run a full re-index:
- Go to Supercharger → Tools.
- Click Re-index All Posts.
- Confirm the action.
Warning
This will consume API credits proportional to your total content. A site with 1,000 posts will require 1,000+ API calls. Ensure you have sufficient API quota before proceeding.
Excluding Posts from the Index
Individual posts can be excluded from indexing and recommendations via the Supercharger sidebar in Gutenberg. Excluded posts will not:
- Generate or store embeddings
- Appear in other posts’ recommendation widgets
- Have any AI modules active on them
Handling Failed Indexing
Posts that fail to index are shown on the Dashboard and in the Logs. Common causes:
- API key error — Check your OpenAI API key in Settings.
- Rate limit — Your API plan’s rate limit was reached. Indexing will retry automatically on the next cron run.
- Post too short — Some AI providers reject requests with very little content. Very short posts may not index.
Failed posts are automatically retried on subsequent cron runs. You can also force a retry by triggering a cron run manually from Supercharger → Tools.