Skip to content

Give the assistant better information to work with.

Clear source material makes answers easier to check and maintain. Start with the questions visitors need answered most often.

What makes a website useful as chatbot knowledge?

Publish important facts in readable HTML, give policies clear conditions and dates, resolve conflicting versions and allow the relevant crawl. Map real visitor questions to source pages, then verify what the chatbot actually retrieved.

First-party product guidance. How we maintain these guides · Report a correction

Write down the questions that matter.

List common questions about services, eligibility, locations, hours, pricing, and next steps. For each question, identify the page that should support the answer.

If no page establishes the answer, decide whether to publish it or add a carefully approved saved answer. Do not expect the model to fill a gap in business policy.

Remove conflicting versions of the facts.

Check the main navigation, service pages, and footer for different phone numbers, hours, or service areas. Archive expired offers and revise outdated policy pages.

Put dates and conditions next to time-sensitive information. A price without its scope or exclusions can be easy to repeat incorrectly, even when the number itself appears on the page.

Make important information available as text.

Use descriptive headings and readable HTML for essential service information. Text that exists only inside an image, a login-only area, or a client-side interaction may not be available to a standard crawl.

Check robots.txt and the source list after indexing. If a needed page was excluded or could not be read, resolve that before judging the assistant’s answer quality.

Review sources and test the boundary.

Exclude pages that should not inform replies. Confirm the business details extracted by Sairo and add saved answers where exact wording is necessary.

Ask both expected questions and plausible questions that the website cannot answer. Review the response and outcome, then use the gap report to decide what to improve next.

Ask Sairo can help inspect a visitor question and prepare an answer correction after you establish the correct information. Keep the website page and confirmed facts aligned with that correction.

Keep a source inventory your team can maintain.

Give high-impact information an owner and a review trigger. An inventory can be a short shared document; the useful part is knowing which source wins when two pages disagree.

When a policy changes, review the published page, the indexed source, confirmed business details, and any saved answers that repeat it. Refreshing a page alone does not review those separately maintained records.

Example source review record
InformationAuthoritative sourceReview trigger
Service price and scopeCurrent service or pricing pageA price, inclusion, or tax treatment changes.
Opening hoursLocation or contact pageSeasonal hours, closures, or a move.
Eligibility or service areaCurrent eligibility or location pageA new region, condition, or exclusion.
Follow-up expectationsContact or support pageA change in staffing, channel, or response commitment.

Rewrite an ambiguous source

“Packages from 200” leaves the currency, scope, and conditions unclear. A useful source states the currency, what the starting package includes, and when an individual quote is required. Use your actual approved terms rather than copying this example into a pricing policy.

See what your website can answer.

Try a sample, review the result, and decide what comes next.