What your website needs to say before a chatbot can answer for you
A chatbot that reads your website is only as good as the website it's reading. Before you turn one on, it's worth spending twenty minutes checking that your pages actually say what a visitor would need to hear. Here's what to look at, and what to add if it's missing.
Your pricing page should answer the questions people actually ask
"How much does it cost" is one of the most common questions any business chatbot gets. If your pricing page only lists a starting price with no detail — no explanation of what's included, no mention of setup fees, no answer for "what if I need more than the basic plan" — the bot has nothing to work with and will either guess or say it doesn't know. Write out the version of your pricing page you'd want a new customer to read, not the short version you're used to skimming past.
Your FAQ should be a real FAQ, not three questions from 2019
A lot of small business FAQ pages get written once at launch and never touched again. If yours has three or four questions and nothing about your current services, hours, or policies, that's the first thing to fix. Think about the last ten questions a customer actually emailed or called about — those are your FAQ, not the ones that seemed obvious a few years ago.
Your service pages should spell out what's actually included
"Full-service landscaping" tells a chatbot nothing useful. "Full-service landscaping including mowing, seasonal cleanup, and irrigation repair — we do not install fences or hardscaping" gives it something to answer with. The more specific your service descriptions, the fewer times the bot has to say "I'm not sure" to a question you could have answered on the page.
Your hours, location, and contact details should be current — and in one place
It sounds obvious, but out-of-date hours or an old address are some of the most common wrong answers a website chatbot gives, because most sites list this information once, on one page, and never revisit it. Confirm it's correct before launch, not after a visitor drives to a location that's closed.
Your policies should be written down, not just known internally
Return policy, cancellation policy, deposit requirements, service area limits — if the answer only lives in your head or your team's, a chatbot reading your website can't give it. Anything you'd tell a customer over the phone is worth a paragraph on your site, even a short one.
The bottom line
None of this is chatbot-specific work — it's the same content that makes your website useful to a human visitor who's deciding whether to trust you. A chatbot just makes the gaps visible faster, because every unanswered question becomes an "I'm not sure" instead of quietly going unnoticed. Do this pass before launch and you'll spend a lot less time fixing it after. For what to check once it's live, see what to check in the first week; for the setup mistakes this prevents, see 5 chatbot mistakes that are costing you leads.