AI chatbots can be useful. They can answer common questions, help visitors find information, qualify leads, and provide support outside normal business hours.
But before adding one to a website, it’s worth asking a simpler question:
What problem are we trying to solve?
A chatbot isn't always the best answer.
Start With the Problem
If visitors can't find information, better content may be the solution. If they can't find the right page, improve navigation. If they aren't sure which service they need, a guided service finder may work better.
Other alternatives include:
- A well-organized FAQ
- Better service or product pages
- A searchable knowledge base
- Guided forms or service finders
- Online scheduling
- Click-to-call or contact options
If one of these solves the problem, there may be little reason to add another software platform.
If customers genuinely benefit from a conversational experience, then a chatbot may make sense.
Chatbots Have a Technical Cost
A chatbot may look like a small button, but behind that button is another application.
A recent measurement study found website chat widgets ranging from 6 KB to 502 KB. Some implementations also contacted as many as 17 third-party domains.
That can mean additional JavaScript, network requests, processing, and third-party dependencies.
The impact varies considerably by vendor and implementation, which is why it should be measured rather than assumed.
Think About Performance
Before installing a chatbot, establish a performance baseline. Then compare the website after it has been added.
Pay attention to:
- Page weight
- JavaScript execution
- Network requests
- Third-party domains
- Core Web Vitals
- Mobile performance
If possible, lazy-load the chatbot so its heavier resources aren't downloaded until someone actually chooses to use it.
Why make every visitor pay the performance cost of a feature most won't use?
Accessibility Matters
A chatbot also needs to work with keyboards and assistive technologies.
Test keyboard navigation, focus management, the Escape key, screen-reader announcements, button labels, and whether focus returns to the chat button when the window closes.
A chatbot may make information easier to access without actually being accessible itself.
What About SEO?
Adding a chatbot doesn't automatically hurt SEO.
The bigger concern is whether the implementation makes the website slower or more complicated.
Your important information should still exist directly on the website. Service details, FAQs, product information, and business information shouldn't depend on visitors asking an AI for the answer.
AI should complement a well-built website, not compensate for a poorly organized one.
Measure the Value
A chatbot should have a purpose and a way to measure whether it's working.
Is it generating qualified leads? Reducing support requests? Helping visitors find information? Improving conversions?
Compare those results with the technical cost of running the chatbot.
If the value is clear, the investment may be worthwhile. If few people use it and it adds significant complexity, there may be a better solution.
Use the Simplest Technology That Works
AI is another tool—not a requirement.
Start with the problem, consider the simpler solutions, and use a chatbot when conversation genuinely improves the experience.
The goal isn't to put AI on your website.
The goal is to make your website better with AI.
Sources
Chatbot.fr, “Chatbot site internet” — August 2026 measurement study examining the resource footprint and third-party network activity of website chat widgets.
HTTP Archive, Web Almanac — research and data concerning third-party web technologies, including chat and customer-success scripts.
Make Things Accessible, “Chatbots and Web Accessibility: Addressing Usability Issues and Embracing Inclusive Design” — discussion of accessibility and usability concerns associated with web chatbots and related widgets.
