Step 1
Find the rendered element and its real source
- 01
Inspect the browser DOM
Search Elements or page source for id="chatbot" and record the script URL and surrounding markup.
- 02
Search the codebase
Look for chatbot, the script hostname and unique configuration values in templates and components.
- 03
Check the tag manager
Review custom HTML tags, triggers, environments and published container versions.
- 04
Check the CMS
Inspect theme footers, global code injection, plugins and page-builder blocks.
Sources: 1
Step 2
Preserve evidence before removal
- the exact snippet and all configuration values
- screenshots of business hours, questions and routing
- the current release, tag-manager version or CMS revision
- owner, change ticket, planned cutover and rollback instruction
- retention and export decisions for existing conversations
Step 3
Disable it at the source, not with cosmetic CSS
Remove or disable the script in the authoritative template, tag or plugin. Hiding the button with CSS leaves network requests and code running and is not a clean retirement.
Avoid broad search-and-delete operations. A site can contain other legitimate scripts or elements named chatbot. Review each matched location before committing the change.
Step 4
Verify production and the replacement
- no old script in page source or rendered DOM
- no request to the old endpoint in the Network panel
- no empty launcher, overlay or JavaScript error
- new widget loads with the intended language and route
- real message and agent reply complete the round trip
- monitor landing pages and conversion paths after deployment