luckpandaChatbot readiness checker: can an AI agent answer from your website?
Enter your website address. The checker reads your home page and up to six key pages, scores how well a chatbot could answer your visitors from them, and tells you what to add.
Build a support agent from your site
Your own AI agent answers questions like this on your website, day and night, from your own pages and documents, and passes the hard ones to you. Paste your address to see it learn your site. No account needed.
What the chatbot readiness checker tells you
A website is ready for a chatbot when an AI agent can find, in plain text it is allowed to read, the answers your visitors ask for: how to reach you, what things cost, your FAQ, your shipping and refund terms, your hours and who you are. This checker reads your home page and up to six linked pages, scores those signals out of 100 and gives a fix for each gap.
- Enter your home pageType your website address. The home page works best, because the checker finds your other key pages through its links.
- Let it readIt loads the page and your robots.txt, then up to six linked pages that look like Contact, Pricing, FAQ, Policies, About and Hours.
- Read the score and the checksEach of the ten checks has a labelled seal: OK, Review or Missing. Anything that is not OK has a one-line fix.
- Look at the visitor questionsSix questions your visitors are likely to ask, each marked Covered, Partly or Missing on your current pages.
- Fix the gaps and check againAdd the missing pages or text, publish them and run the check again. The score moves as soon as the pages change.
What a chatbot needs from your website
An AI agent answers from what your pages say. If a fact is not written down where it can read it, it cannot answer, and a good agent will say so instead of guessing.
| What it needs | Why visitors ask | What the checker looks for |
|---|---|---|
| Crawl access | Nothing else matters if the bot may not read your pages. | Your robots.txt allows LuckPandaBot, the crawler that builds LuckPanda agents. |
| Readable text | A bot reads text. Words inside images, sliders and videos are invisible to it. | At least 150 words of readable text on the page you entered. |
| Contact details | “How do I reach a person?” comes up in almost every chat. | An email address or phone number in the text of the pages read. |
| Prices | Buyers ask what it costs before they ask anything else. | A pricing page, or prices or the word “price” in the text. |
| FAQ or help page | An FAQ is the quickest source of ready answers for a bot. | A linked page whose address looks like an FAQ, help center or knowledge base. |
| Policies | Shipping, returns, refunds and cancellations decide many purchases. | A linked shipping, returns, refund or terms page. |
| Hours | “Are you open now?” and “When will someone reply?” | Days with times, or phrases such as “opening hours” or “business hours”. |
| About | Visitors want to know who they are dealing with and where you are. | An About page, or phrases such as “about us” or “who we are”. |
| Enough text overall | A few lines cannot answer the long tail of questions. | At least 1,500 words across the home page and the pages read. |
How the score is made
Ten checks, each with a weight. The weights add up to 100. A check marked OK earns its full weight, Review earns half, and Missing earns nothing.
| Check | Weight | OK | Review | Missing |
|---|---|---|---|---|
| Your page loads | 10 | The address answers | – | It does not load (the score is then 0) |
| Crawl access | 15 | robots.txt allows LuckPandaBot, or there is no robots.txt | – | robots.txt blocks it |
| Readable text | 15 | At least 150 words | Between 40 and 149 words | Under 40 words |
| Contact details | 12 | Email or phone found | A contact page, but no email or phone in its text | Neither |
| Prices | 10 | Pricing page or prices in the text | No prices found | – |
| FAQ or help page | 12 | An FAQ or help page | No FAQ page, but five or more questions in the text | Neither |
| Policies | 8 | A policies page | Policies only mentioned in passing | Neither |
| Hours | 5 | Hours written as text | No hours found | – |
| About | 5 | About page or “about us” text | Not found | – |
| Enough text overall | 8 | At least 1,500 words | Between 500 and 1,499 words | Under 500 words |
Under 50 means a chatbot would struggle, 50 to 79 covers the basics, and 80 or more gives a chatbot plenty to answer from.
The checker is a quick look, not a full crawl. It reads the page you enter and up to six pages linked from it, one for each kind of page above. It reads the HTML your server sends, the way most crawlers do, so text that only appears after JavaScript runs in a browser may not count. It skips menus, headers, footers and forms, so facts that live only in your footer are not counted. Pages behind a login are never read.
How to fix each gap
Most gaps take one short page or one paragraph to close. Write the facts as plain text, in the body of a page, and link that page from your home page.
- Crawl access: in robots.txt, remove the Disallow rule that applies to LuckPandaBot or to every crawler (User-agent: *). If you must keep it, upload your pages as documents to your agent instead.
- Readable text: replace text baked into banners with real text, and add a short paragraph that says what you do, for whom and where.
- Contact details: put your email and phone in the body of your Contact page, not only in the footer or a form.
- Prices: publish prices, a starting price or how a quote works. “From [amount]” is better than nothing.
- FAQ: write the ten questions your team answers most, each with a two or three sentence answer.
- Policies: give shipping, returns, refunds and cancellations their own pages with plain addresses, such as /shipping or /returns.
- Hours: write the days, the times and the time zone, and say what happens outside them.
- About: who you are, where you work, how long you have done it and who you serve.
- Enough text: expand thin service and product pages. Each one should answer what it is, who it is for, what it costs and how to get it.
Contact us Email: [support email] Phone: [phone number] We answer [days], [opening time] to [closing time] ([time zone]). Address: [street], [city], [country] We reply to emails within [reply time].
Opening hours ([time zone]) Monday to Friday: [9:00] to [18:00] Saturday: [10:00] to [14:00] Sunday and public holidays: closed Outside these hours, leave a message and we reply the next working day.
Do you deliver to [country or region]? Yes. We deliver to [regions] in [delivery time]. Delivery costs [amount], and it is free on orders over [amount]. You get a tracking link by email when your order ships.
The visitor questions panel
Under the checks, an AI model reads the beginning of each page we read and lists the six questions your visitors are most likely to ask. It then marks each one Covered, Partly or Missing, judging from your text alone.
The questions depend on your site: a shop gets questions about delivery and returns, a clinic about booking and prices, a software company about plans and setup. Treat the list as a to-do list. Every Missing question is one your chatbot would have to hand to a person, and one a visitor might leave over.
| Question | Result | What to add |
|---|---|---|
| How much does a bike service cost? | Missing | A price list or “from [amount]” for each service |
| Can I book a repair online? | Partly | How to book, and how soon the next slot usually is |
| Do you repair electric bikes? | Covered | Nothing |
| How long does a repair take? | Missing | Typical turnaround per kind of repair |
| Where are you and when are you open? | Covered | Nothing |
| Do you offer a warranty on repairs? | Missing | A short warranty paragraph on the services page |
An illustrative result for a made-up bike repair shop, not a real site.
The panel uses the free tools’ shared AI allowance. When that is used up for the day, the score and the checks still appear and the questions are skipped. Run the check again later to see them.
What to publish first, by type of business
Visitors ask different first questions in different businesses. Make sure the pages behind them exist and are linked from your home page.
| Business | First questions visitors ask | Pages to have |
|---|---|---|
| Online store | Delivery time and cost, returns, sizes, order tracking | Shipping, Returns, Size guide, FAQ, Contact |
| Clinic, salon or studio | Prices, booking, first visit, location, hours | Services with prices, Book, Hours and location, FAQ |
| Restaurant or café | Hours, booking a table, menu, dietary options | Menu as text, Hours, Reservations, Contact |
| Software company | Plans, trial, integrations, security, cancelling | Pricing, FAQ, Docs or help center, Terms |
| Agency or consultant | What you do, for whom, how much, how to start | Services, Case studies, Pricing or “how we quote”, Contact |
| School or course provider | Fees, schedule, eligibility, refunds | Courses, Fees, Schedule, Refund policy, FAQ |
| Hotel or rental | Availability, check-in times, cancellation, parking | Rooms, House rules, Cancellation policy, Location |
Common mistakes
- Contact details and hours only in the footer. Many chatbot crawlers, ours included, skip footers and menus because they repeat on every page.
- Prices only in a PDF brochure or an image. Write them on a page, or add the PDF to your agent as a document.
- An FAQ that loads only after a click runs JavaScript. If the answers are not in the HTML the server sends, crawlers do not see them.
- A staging robots.txt with “Disallow: /” copied to the live site. It blocks every crawler that respects it.
- Policy pages that exist but are not linked anywhere. If nothing links to a page, crawlers rarely find it.
- Page addresses that say nothing, such as /page-12. Plain addresses such as /pricing or /returns are easier for any bot to recognize.
- Answers that say “contact us for details” to every question. A chatbot can only repeat that.
How an AI support agent uses these pages
A support agent built from your site answers from the same pages this checker reads. The better they answer, the fewer chats it has to pass to you.
A visitor on a home goods store’s website, late at night
The first answer comes from the returns page. The second question has no answer on the site, so the agent says so and passes the chat on. Add one line to your shipping page and the next visitor gets the answer straight away, at any hour.
A LuckPanda agent learns from up to 50 pages of your website, plus documents (PDF, DOCX, TXT, Markdown or CSV), text you write and question-and-answer pairs. So a gap this checker finds can be closed on your website or directly in the agent.
Turn your website into a support agent
Paste your address and watch an AI agent learn your pages. Ask it the questions above and see what it answers.
See the AI customer service agentQuestions people ask
What makes a website ready for a chatbot?
A chatbot answers from your pages, so they need to say, in plain text, what visitors ask: how to contact you, what things cost, your FAQ, your shipping, returns and refund terms, your hours and who you are. Crawlers also need to be allowed to read the pages in your robots.txt.
Is this a general website checker?
No. It checks one thing: whether a chatbot could answer your customers from your site. It does not test security, broken links or search rankings. To see which AI crawlers your site allows, use the AI bot checker, and to see how answer engines read a page, use the AI visibility checker.
Does the checker read my whole website?
No. It reads the page you enter and up to six pages linked from it, one for each kind of key page: contact, pricing, FAQ, policies, about and hours. An agent you build reads much more: up to 50 pages, plus any documents you add.
Why does it say my contact details are missing when they are on my site?
The checker skips menus, headers and footers, as many chatbot crawlers do, because they repeat on every page. If your email and phone appear only in the footer, write them in the body of your Contact page as well.
Can a chatbot answer questions my website does not cover?
It should not. A well-built agent answers from your sources only, says when it does not know and passes the chat to a person. You can fill gaps without changing the site by adding documents, text or question-and-answer pairs to the agent.
Is the checker free?
Yes. You do not need an account. Each network can run a limited number of checks a day, and the visitor questions panel uses a shared daily AI allowance.
Related pages
- AI bot checkerSee which AI crawlers your robots.txt allows or blocks, from GPTBot to PerplexityBot, and why.
- AI visibility checkerCheck what ChatGPT, Claude and Perplexity can read on your page, and how an AI would describe you.
- AI answer generatorAsk any question and get a clear answer from general knowledge, one web page or text you paste.
- Return policy generatorDraft a store return policy with your window, shipping and exchange rules, plus a FAQ your chatbot can answer from.
- Canned responses libraryOver 70 copy-ready canned responses for customer service, by situation, with a tab that rewrites your own reply.
- AI customer service agentAnswers from your help pages and live order data, says when it does not know, and hands the chat to a person.
Build it with your AI agent
Give an agent your site and it can create the chatbot, read your pages and test it through LuckPanda's API and MCP. It prepares the work; going live stays with you.
Use LuckPanda's MCP server (https://luckpanda.app/mcp) to build a website chatbot for me. Ask for my website address, call chatbot_create_from_website with it, wait until the pages are learned (chatbot_source_list), then run a few test questions with chatbot_test_message and show me the answers. Do not put it live: I will do that myself.
Instructions for AI agents
Needs a LuckPanda agent key (Settings › Developers) with the chatbot.manage grant. MCP endpoint: https://luckpanda.app/mcp (Streamable HTTP, bearer key).
chatbot_create_from_website{ url }: creates a draft chatbot named after the site and starts reading it.chatbot_source_list: pages learned, failed or skipped, with a reason for each.chatbot_test_message: asks the bot a question as the owner. Test chats never email anyone.- Going live (
chatbot_updatewith status live) is a person's action; an agent gets APPROVAL_REQUIRED.
Try it on your website
Paste your address and watch the chatbot learn your pages. No account and no card.
This page in other languages