Search a website with AI
The information you need is somewhere between product pages, help articles and documentation. With CraCha you read selected website content and then ask questions about it in your account. Here’s when that helps and how to start small.
When is a website chat worth it?
When you repeatedly need to pull information together from several pages of a website – for example when you research product details for a consultation or regularly work with extensive help documentation. For a single passage you already know, the browser’s search is often enough.
CraCha is a research tool. You don’t currently build a publicly embedded support bot with it, and it doesn’t automatically search the whole internet.
Why not just use an AI search?
An AI search such as Google’s AI Mode, ChatGPT or Perplexity goes out to the web for every question and works with the results a search engine delivers. For a quick question that’s fine. But what sits deep inside a website, or isn’t listed on Google at all, rarely shows up.
CraCha reads the website beforehand, page by page, following its links and sitemap itself. It answers your questions from that website only, with a link to the source. That pays off when it has to be exact or you keep coming back to the same website. For a detailed comparison, see the article CraCha vs. ChatGPT and Perplexity.
Two typical use cases
- Search a client website: for agencies and marketing teams who need to get up to speed on a client’s website quickly.
- Search documentation: for developers who want to question large docs precisely.
More ideas – from help centers to university websites – are on the Examples page.
From the website to your first verifiable answer
- Define a task. Write down a concrete question whose answer you expect on the website. Choose a public section you’re allowed to read.
- Create and confirm your account. Open the confirmation link in your email. If the message is missing, check your spam folder too.
- Start small. Start a crawl in the dashboard – that is, reading pages. Give it a name and begin with no more than 20 pages. Use a suitable subsection instead of the whole website if that fits.
- Wait for the processing. Open your knowledge base only once it’s ready. Unreachable or blocked pages may be missing.
- Ask and verify. Open the knowledge base via “Ask”. Read the linked original pages and check whether they really support the statements.
Three sample questions for product documentation
Phrasing aids, not recorded product results. Replace the placeholders with terms from your website.
- What prerequisites does the documentation list for installing [product]?
- How do [option A] and [option B] differ according to the pages read?
- Which limitations are mentioned for [feature]? Link the matching sources.
If the answer stays unclear, ask about a single aspect. If the relevant page is missing from the knowledge base, no rephrased question can replace that source.
Make the free credits last the whole way
Every page read and every answer uses credits; you get 100 credits free to start. For your first test, read only a few pages so enough is left for questions. Reading again also uses credits.
See costs and FAQKnow the limits
A source link is no guarantee that an answer is correct. Compare important statements with the original and check how current it is. CraCha works with the state it read; changes to the source only appear after it is read again.
Login areas, paywalls and PDF uploads are not part of this process. Which public pages are reachable depends, among other things, on links and technical access restrictions. Read the privacy policy about how data is processed before you use content.
Test a question from your everyday work
You need a suitable public website and a concrete research question. No credit card is required to get started.
Start for free