Re-indexing and Updates
When and how to force re-indexing of sources to keep your agent up to date.
Simple Agent keeps your agent updated automatically, but there are situations where you need to trigger a manual re-index.
Automatic updates
By default, each source has an update cycle:
| Source type | Default frequency |
|---|---|
| URL / Site | Every 7 days |
| Sitemap | Every 3 days |
| No automatic update (static) | |
| Direct text | No automatic update (static) |
Automatic updates run in the background — your agent does not go offline during the process.
When to trigger a manual re-index
Re-index manually when:
- You updated your site content and don't want to wait 7 days
- You corrected an error in a PDF and uploaded a new version
- The agent is giving outdated responses
- You added new pages to the sitemap
How to re-index
- In the agent panel → Training tab
- Click the three-dot menu next to the source
- Select Re-index now
The status changes to Indexing... and returns to Active when complete. For large sites (100+ pages), this can take 2–10 minutes.
Via API
POST /v1/sources/{source_id}/reindex
curl -X POST https://simple-agent.me/api/v1/sources/src_xxxx/reindex \
-H "Authorization: Bearer af_live_xxxx"
Response:
{
"id": "src_xxxx",
"status": "indexing",
"started_at": "2026-05-14T10:30:00Z"
}
To check status:
GET /v1/sources/{source_id}
# Response when complete:
{
"id": "src_xxxx",
"status": "active",
"chunks_count": 342,
"last_indexed_at": "2026-05-14T10:32:18Z"
}
Automatic re-index via webhook
If you have a content publishing pipeline (CMS, GitHub Actions, etc.), you can trigger re-indexing via webhook after each publish:
# In your deploy pipeline
curl -X POST https://simple-agent.me/api/v1/sources/src_xxxx/reindex \
-H "Authorization: Bearer af_live_xxxx"
This ensures the agent is always in sync with your published content.
Delete and recreate vs. re-index
Use re-index when:
- The content was updated at the same URL
- You want to keep the chunk history
Delete and recreate when:
- The site structure changed drastically
- You want a full cleanup of old embeddings
- You changed the source type (e.g., replaced a PDF with a URL)
Re-indexing limits
| Plan | Manual re-indexes/month |
|---|---|
| Starter | 10 per agent |
| Growth | 50 per agent |
| Agency | Unlimited |
Scheduled automatic re-indexes do not count toward this limit.
Monitor quality after re-indexing
After re-indexing, go to the Playground and test the same questions that revealed outdated responses. If the problem persists, use View chunks to confirm the correct content was indexed.
If the new content doesn't appear, check:
- Whether the page blocks crawlers via
robots.txtor anoindexmeta tag - Whether the content is generated via JavaScript (our crawler uses headless Chromium, but some SPAs with late-loading content may need adjustment)