Automatic re-crawling handles most of it
If your platform re-crawls your site on a schedule, routine content changes can be picked up without any action from you. QaribuBot uses the refresh interval configured for your current plan; the live pricing page shows the applicable schedule. See How we learn your pages for credits, automatic recrawls, and manual runs.
Trigger a re-crawl after major changes
For a big update — new pricing, a rebranded site, a major policy shift, a full redesign — don't wait for the next scheduled crawl if your platform lets you trigger one manually. The gap between a major change going live and the bot catching up is exactly when it's most likely to confidently state something that's no longer true, which is worse than simply being slow to update.
This is a small habit worth building into your launch checklist for any significant site update: alongside checking your analytics tracking still works and your forms still submit, add 'trigger a chatbot re-crawl' to the list.
FAQ snippets need manual updates
Anything you added as a manual FAQ entry won't update itself, since it's not tied to a live page the crawler re-reads — if a policy in a snippet changes, go back and edit that entry directly, or it'll keep repeating the old version indefinitely. That lives on Knowledge in QaribuBot.
It's worth keeping a mental (or literal) list of what you've added manually, precisely because these entries are the ones that won't self-correct the way crawled content does.
A simple quarterly check
Beyond the routine and post-launch updates, it's worth doing a broader review every few months: read through your manual FAQ entries and confirm they're all still accurate, and spot-check a few common questions to make sure the bot's answers still match reality. This catches the slow drift that individual updates sometimes miss.
