WordPress Chatbot Trained on Pages: A Page-by-Page Plan for Contact, Pricing, Shipping, Services and Terms (Free Seven-Step Timeline)
WordPress chatbot trained on pages is easiest when you take it one page type at a time. Each page on your site holds a different kind of fact, and each needs a different edit before a bot can use it. This guide walks through seven page types in a sensible order, shows what to pull from each and what to ignore, and ends with a timeline you can follow over one week.
⚡ In short
- Do not feed every page at once. Work through page types in order of how many questions they answer.
- Start with contact, pricing and shipping or booking pages. They answer most chats.
- Take five short answers from each page. Leave out menus, slogans and sidebars.
- Follow the one-week timeline, then add more from real chats.

The idea
Why work by page type, not by site
A site has dozens of pages, but they fall into a handful of types. A contact page holds hours and addresses. A pricing page holds numbers. A policy page holds rules. Each type needs the same kind of editing every time.
Working by page type has three benefits. You learn the pattern once and repeat it. You can put the pages in order of value, so the bot is useful after day two instead of day twenty. And you avoid the trap of loading everything, including slogans, menus and sidebar widgets that mean nothing to a bot.
Everything in this plan assumes you write short answers by hand. LiveChatBot’s AI Agent replies from the knowledge you give it. It has no PDF or file upload, so short written answers are the route, and a WordPress chatbot trained on pages ends up only as good as those answers.
Open each page in a browser, read it like a customer, then write answers in a plain document before adding them.
A tip on pace
Do not rush all seven page types in a single sitting. Tired editing creates mistakes, and a wrong number in a bot answer is repeated to every visitor who asks. One page type a day, with a quick test at the end, gives better answers than a weekend marathon.
Pages 1 to 3
Start with contact, pricing and shipping or booking
Contact and about page
Pull: opening hours, address, phone, email, languages spoken, areas served. Leave out: the founder story, team photos and the mission statement.
Pricing or services page
Pull: the price of each item, what is included, what costs extra, how you take payment. Be careful with “from” prices. Write “starts at ₹X for Y”.
Shipping, delivery or booking page
Pull: times, charges, areas, how to book or cancel, and what happens if something goes wrong. Put each number in the answer. “Delivery takes 2 to 3 days” beats “quick delivery”.
These three pages answer the bulk of chats on most small sites. If you do nothing else, do these. A bot trained only on these three page types is already useful, and you can switch it on while you carry on with the rest. Keep an eye on the first few real chats, because they show which of your pages caused confusion and which answers need a second pass.
Pages 4 to 5
WordPress chatbot trained on pages: returns, products and services next
Returns and refunds page
Pull: the time limit, the condition of items, who pays for return shipping, how refunds are paid and how long they take. Name exceptions in the same answer: “Sale items cannot be returned.”
Product and service pages
Do not copy all of them. Pick your top ten by traffic. For each, write a two-line answer: what it is, who it suits, the price. Product pages are full of marketing language, so strip adjectives and keep specifications, sizes, materials and prices.
For a WooCommerce shop, the same plugin works on shop pages, so the bot can sit where shoppers are. See the WordPress live chat plugin and WooCommerce live chat guides.
Pages 6 to 7
Finish with terms, privacy and the FAQ page
Terms and privacy pages
Be selective. Pull only what visitors really ask: whether you share data, how to delete it, how long you keep it. For anything legal or detailed, send people to the page itself rather than paraphrasing it. A bot should never reword a legal clause on its own.
Your existing FAQ page
Rewrite each entry as a short fact with a number. Our guide on training your AI chatbot shows how, and the AI Agent page explains how replies are built from your knowledge.
What to skip
Skip pages that change often or are not facts: the blog index, news pages, events past their date, testimonials and landing pages for old campaigns.
Try it
Your one-week page-by-page timeline
Follow the days in order. Each step takes about an hour on a small site.
Write answers for hours, address, phone, email and areas. Add them to the AI Agent.
One answer per item with price, inclusions and extras. Check every number against today.
Times, charges, areas, cancellation. Test the bot with five delivery questions.
Time limit, conditions, refund timing, exceptions in the same answer.
Two-line answers: what it is, who it suits, price. No marketing adjectives.
Only the questions customers really ask. Link to the page for legal detail.
Ten questions: five direct, three reworded, two unknown. Fix guesses, set a handover.
After launch
Keep a WordPress chatbot trained on pages in step with your site
Pages change quietly, and small edits are the ones people forget to copy across. A new price goes live and the bot keeps quoting the old one. Build two habits.
A change rule. Whenever you edit a price, rule or time on a page, update the matching answer the same day. Write it on your to-do list next to the page edit.
A monthly review. Read the chats where the bot could not answer. Add an answer for each. The gaps show you which pages are unclear, which is a free hint to improve the page itself.
Set opening hours and the away form so visitors can leave contact details when no one is online, and install the Android app so nobody misses a chat. If a visitor asks something outside your answers, the keyword bot and saved replies give a safe fallback, and unanswered chats can be turned into tickets so nothing is lost. The bot and your team then work together: the bot handles the repeats and people handle the rest. Try it free at livechatbot.in.
Frequently asked questions
Which pages should a WordPress chatbot trained on pages learn first?
Contact, pricing or services, and shipping or booking. They answer the most chats on most small sites.
Does the chatbot crawl my pages by itself?
You add the knowledge yourself as short written answers. There is no PDF or file upload for training.
How many answers per page?
About five. If a page yields more, it probably covers several topics and should be split by subject.
Should the bot explain my terms and privacy policy?
Only the simple questions customers ask. For legal detail, link to the page instead of paraphrasing.
What if the bot does not know an answer?
It should say so and hand over to your team or collect an email. Test this before launch.
Keep reading
Related guides
WordPress Chatbot Trained on Content: Turn Your Blog Posts Into Bot Answers Without Copying Opinions, Old Prices or Fluff (Free Before-and-After Examples)
WordPress Chatbot With Knowledge Base: Three Ways to Feed It, and Which One Fits Your Site (Free Weighted Scorecard)
WordPress Chatbot for FAQ Pages: Mine Your Real Questions First, Then Write Answers a Bot Can Use (Free Copy-Ready Answer Shapes)
Train it one page at a time
Follow the week plan and have a useful bot by Friday. Free to start on livechatbot.in.