Chatbot WordPress Content Map: Which Pages, Posts and WooCommerce Products Your Bot Should Learn From, and Which to Leave Out (Free Page Sorter)
Chatbot WordPress guides usually stop once the plugin is installed and the bubble appears. The harder question comes next: what should the bot actually know? Your WordPress site already holds most of the answers, spread across pages, posts, WooCommerce products and policy pages. Feed it all in and the bot gets confused by tag archives and old blog posts. Feed it too little and it can’t answer basic questions. This guide shows how to sort your WordPress content into what to teach, what to link to and what to skip, with a free tool that sorts your sitemap URLs for you.
⚡ In short
- Start from your sitemap: it lists every page, post and product WordPress publishes.
- Teach the bot from a small set of fact pages: delivery, returns, contact, FAQ, prices, sizing, hours.
- Link to legal pages, categories and blog posts instead of copying them.
- Skip cart, checkout, account, tag and author pages. They add noise, not answers.

The problem
Why ‘feed it the whole site’ goes wrong
When people add an AI chatbot to a WordPress site, the first instinct is to give it everything. It feels thorough. In practice, a typical WordPress install publishes a lot of pages that aren’t useful to a bot at all, and some that actively mislead it.
Look at what WordPress creates on its own. Every tag gets an archive page. Every author gets one. Categories get listings, blog posts get paginated archives, and WooCommerce adds cart, checkout and account pages. Many sites still have the default “Sample Page” and “Hello world!” post from the day they were installed. None of these answer a customer’s question.
Then there’s content that changes. A WooCommerce product page shows today’s price and stock. If you copy that into the bot, it’ll keep quoting last month’s price long after you’ve changed it. Old blog posts may mention offers, delivery times or policies that no longer apply.
The result of feeding everything is a bot that sometimes answers from the wrong place: a 2023 festive sale post instead of your current returns page, or a tag archive that lists product names without any facts.
The better approach is a content map. You go through your URLs once and put each one in a bucket: teach, link, or skip. It takes about an hour for a small site, and it’s the difference between a bot that answers from your best pages and one that guesses. If you want a broader audit of documents beyond your website, our knowledge audit guide covers PDFs, price lists and WhatsApp notes too.
The method
Five steps from sitemap to bot knowledge
Open your sitemap and copy every page, post and product URL.
Teach, products, link, skip. The tool below does a first pass.
Rewrite vague pages so each fact is stated plainly, with numbers.
Copy the tidied facts into the bot’s knowledge and saved replies.
Ask real questions, and update the bot whenever a page changes.
Step 1
Find every URL your WordPress site publishes
You don’t need a plugin or a crawler to get your URL list. WordPress already publishes one.
Since version 5.5, WordPress creates a built-in sitemap at yoursite.com/wp-sitemap.xml. Open it in your browser and you’ll see links to sub-sitemaps for posts, pages, products (if WooCommerce is active), categories, tags and users. Click each one and copy the URLs.
If you use Yoast SEO or Rank Math, they replace the built-in sitemap with their own, usually at yoursite.com/sitemap_index.xml. It works the same way: an index that links to sitemaps for each content type.
Two other quick sources:
- Pages → All Pages in your WordPress dashboard shows every page, including drafts you might have forgotten.
- Products → All Products in WooCommerce lists every product with its status and stock, which helps you pick best sellers.
Don’t worry about getting every last URL. You’re looking for the pages that hold facts customers ask about, and those are almost always top-level pages: shipping, returns, contact, about, FAQ, size guide, pricing. Paste whatever you collect into the sorter below. It reads only the URL text, so slugs like /shipping-policy/ and /refund-and-returns/ are what it uses to decide. If your slugs are unclear, like /page-7/, the tool will ask you to check them by hand.
Free tool
Chatbot WordPress page sorter
Paste your sitemap URLs. The tool sorts them into teach, products, link and skip, and flags key pages you’re missing.
Paste your WordPress URLs, one per line. Copy them from your sitemap (yoursite.com/wp-sitemap.xml, or sitemap_index.xml if you use Yoast or Rank Math).
Runs only in your browser; nothing is sent or saved. The tool reads the URL text only; it doesn’t visit your pages.
Teach
Turn your fact pages into answers the bot can use
The pages in the "teach" bucket are where most customer questions get answered. But WordPress pages are written for reading, not for a bot to pick facts from. Before you copy them in, tidy each one.
Put the fact first
A shipping page that opens with "At Example Shop, customer satisfaction is our top priority" makes the bot work harder. Start with the answer: "We deliver across India in 3 to 6 working days. Delivery is free above ₹999." (Illustrative figures.)
Replace vague lines with numbers
"Delivery charges may apply" or "contact us for details" leaves the bot with nothing to say. Write the actual rule: the charge, the threshold, the areas you don't serve.
One fact, one place
If your FAQ says returns are accepted within 7 days and your returns page says 10, the bot will repeat whichever it finds. Fix the site first. Our consistency checker helps you spot mismatches between your channels.
Keep it short
Paste the facts, not the whole page. A tidy summary of five to ten lines per topic usually works better than three screens of text. Our guide on writing answers your bot can use shows the format in detail.
If the tool flagged missing pages, write them on your site first. A customer-facing delivery page is useful in its own right, and it gives the bot something to link to.
WordPress URL patterns
What to do with each kind of page
| URL looks like | What it is | What to do |
|---|---|---|
| /shipping-policy/, /delivery/ | Delivery facts | Teach |
| /refund-and-returns/ | WooCommerce's default returns page | Teach (check it isn't still the template) |
| /contact/, /about-us/, /faq/ | Fact pages | Teach |
| /product/blue-kurta/ | Single product | Teach best sellers' fixed facts; link for price and stock |
| /product-category/kurtas/, /shop/ | Listings | Link |
| /privacy-policy/, /terms-and-conditions/ | Legal text | Link, don't paraphrase |
| /2026/03/post-name/, /blog/post-name/ | Blog posts | Link when relevant; teach only evergreen how-tos |
| /tag/…, /author/…, /page/2/ | Archives | Skip |
| /cart/, /checkout/, /my-account/ | Shop machinery | Skip, and consider hiding chat on checkout |
| /sample-page/, /hello-world/ | WordPress defaults | Skip, and delete from your site |
WooCommerce
Products: teach the facts that don't change
Product pages are tricky because they mix two kinds of information. Some facts are stable: what the product is made of, how to wash it, what sizes it comes in, what's in the box, how to assemble it. Others change often: price, sale price, stock, delivery estimate.
Teach the stable facts for your best sellers. If you have 400 products, you don't need all 400 in the bot. Look at WooCommerce → Reports or your order history and pick the 10 to 30 products that sell most or get the most questions. For each, write a few lines: material, sizes, care, and anything customers often ask before buying.
For changing facts, have the bot send the product link instead. "You can see today's price and available sizes here" with a link is always correct; a copied price might not be. LiveChatBot's AI Agent answers from the knowledge you give it, so anything you paste stays as you wrote it until you update it.
The same goes for questions about a specific order. "Where is my order?" needs someone to look it up, so the bot should hand it to your team or collect a contact. Our after-sale support guide shows how to answer order-status questions without order lookups, and our page on WooCommerce live chat covers the store side of the setup.
Variations and size charts
If your size chart lives in an image, the bot can't read it. Type the measurements into a page or straight into the bot's knowledge as text, one size per line.
Before and after
Tidying a WordPress page for the bot
Installing
Installing your chatbot WordPress plugin or snippet once the content is ready
With your content map done, the installation part is quick. LiveChatBot has a WordPress plugin, which also works with WooCommerce stores, so you can add the chat widget without editing theme files. If you prefer a code snippet, or want more control over where the script loads, our guide on WordPress plugin or code snippet compares the four ways to add chat and includes a snippet generator.
Once the chat is live, use your map for one more decision: where the chat should show. Pages in your "skip" bucket are often ones where the bubble gets in the way. Many stores hide chat on the checkout payment step so nothing distracts from paying. LiveChatBot's "Where it shows" settings let you hide the chat on chosen pages, devices or countries; our guide on showing chat on specific pages walks through it.
If the chat doesn't appear after installing, a caching or optimisation plugin is a common cause. Our WordPress conflict finder helps you find the plugin responsible in five rounds.
Finally, test with real questions. Ask the bot your ten most common customer questions, exactly as customers phrase them. Each answer should come from a page in your "teach" bucket, or the bot should send a link from your "link" bucket. If it answers from the wrong place or makes something up, go back to the fact page and make it clearer.
Keeping in step
Update the bot whenever a WordPress page changes
Your content map isn't a one-off. Every time you edit a fact page in WordPress, the bot's copy of that fact needs the same edit. The easiest way to remember is to add it to your publishing routine: change the page, then change the bot, then ask the bot one question to confirm.
Some changes are easy to forget:
- Festive or monsoon delivery delays that you add to the shipping page for a few weeks.
- New payment options, like adding cash on delivery or EMI.
- Price changes on services or packages listed on a pricing page.
- New products that become best sellers and deserve a few lines in the bot.
- Old pages you delete, which the bot may still mention.
Once a quarter, re-run the sorter on your fresh sitemap. New pages will show up, and any you've removed will be gone. Compare the "teach" list with what the bot knows. Our change ripple guide has a tool that lists every place a changed fact might be repeated, including the bot, saved replies and welcome messages.
A tidy chatbot WordPress setup is mostly this habit. The plugin takes minutes; keeping the bot's facts the same as your pages is what makes customers trust its answers.
Checklist
WordPress content map
Getting started
Sort your sitemap today
Open yoursite.com/wp-sitemap.xml, copy the URLs into the sorter and look at the four buckets. Tidy your top three fact pages tonight, paste their facts into your bot, and install the plugin tomorrow.
LiveChatBot's free plan includes the WordPress plugin, the chat widget, a team inbox, the Android app, Flows, an AI Agent with a small free monthly allowance, and a free keyword bot that answers from saved replies, for two websites with 100 visitors per website each month. See pricing and start at livechatbot.in.
Frequently asked questions
What's the best way to set up a chatbot WordPress site owners can trust?
Install the chat plugin, then teach the bot only from tidy fact pages such as delivery, returns, contact and FAQ. Link to legal pages and blog posts instead of copying them, and update the bot whenever those pages change.
Should my chatbot read every WooCommerce product?
Usually not. Teach stable facts for your best sellers and have the bot link to product pages for price and stock, which change too often to copy.
Where do I find my WordPress sitemap?
WordPress 5.5 and later publishes one at yoursite.com/wp-sitemap.xml. Yoast SEO and Rank Math use yoursite.com/sitemap_index.xml instead.
Should the chat show on the checkout page?
Many stores hide it on the payment step so nothing distracts from paying. Keep it on cart and product pages, where questions come up before buying.
Does the page sorter visit my website?
No. It only reads the URL text you paste, runs entirely in your browser and nothing is sent or saved.
Keep reading
Related guides
Chatbot Web Testing Across Phones, Browsers and In-App Browsers: Check Your Bot Where Visitors Really Open It (Free Test Matrix Builder)
Chatbots in Artificial Intelligence: How Much AI Is Really Inside? A 6-Level Scale and a Free Behaviour Test
Chatbot UI Design for Pacing: How Fast Bot Messages Should Appear, How Many to Send and When to Stop (Free Pacing Calculator)
Give your WordPress bot the right pages
Install the LiveChatBot plugin, teach the AI Agent from your best fact pages, and let your team handle the rest. Start free on livechatbot.in.