The widget reads its configuration at runtime, so dashboard changes reach your site without a redeploy and without changing your snippet. When a change doesn't appear, it's nearly always caching.
Hard-refresh first
Your browser has cached the widget script.
- Windows/Linux — Ctrl+F5, or Ctrl+Shift+R
- Mac — Cmd+Shift+R
Or test in a private window, which bypasses your cache entirely. If it looks right there, it's a local caching issue and your visitors are fine.
Check your CDN
If Cloudflare, Fastly, or similar sits in front of your site, it may be caching the script. Purge the cache for widget.js.
Confirm you saved
Obvious, but common: check the setting still shows your new value after reloading the dashboard page. If it reverted, the save didn't complete — look for a validation error on the form.
Confirm you're editing the right site
If you have several agents, check the site switcher. Editing the wrong site's config is easy to do and looks exactly like a caching problem.
Content changes
New or edited articles are searchable once their embeddings are generated, which takes a few seconds. If an article is findable by its exact title but not by a paraphrase, its embedding isn't ready yet — or failed. See Content isn't searchable.
Also confirm the article is published. Unpublished content is excluded from both search and the help center.
Help center changes
Help center pages are served with caching. A hard refresh usually resolves it; give it a minute if not.
Still not updating?
Get in touch with the setting you changed, when you changed it, and the URL you're testing.