Knowledge Base Page Limits in Talkmio: Pages by Plan

Knowledge base page limits decide how much of your business Mio can remember at the same time, so it helps to understand them before you add your whole website. Every Talkmio plan includes a number of knowledge base pages, and Mio answers only from the content stored in that space. A small shop with a handful of policies fits easily into the Free plan. A company with a large catalogue, a help centre and many PDF manuals needs to plan. This guide explains the limits for each plan as the live pricing page shows them, how the knowledge base works, how to count what you have and how to choose the sources that matter most when space is tight.

Talkmio is an AI live chat for websites. Its assistant, Mio, reads your website, FAQ and uploaded documents and answers only from that content, in the visitor’s language. When it cannot answer, the chat goes to your team. The knowledge base is where that content lives, and the plan decides how large it can be.

Knowledge Base Page Limits by Plan

The pricing page at talkmio.com/pricing is always the final word, and plans can change. At the time of writing, it shows these limits for knowledge base pages, next to other limits that matter when you size a plan.

Plan	Knowledge base pages	AI answers per month	Operators	Websites
Free	20	50	1	1
Pro	200	1000	3	3
Ultimate	1000	5000	10	10
Enterprise 50	5000	20000	50	50
Enterprise 100	10000	50000	100	100
Enterprise 500	50000	200000	500	500

The documentation says that the plan limits how many pages Mio can keep. Your current usage and the limits appear in Settings, then Subscription, so you can see how close you are before a problem appears. Paid plans offer a 14-day trial, and yearly billing gives two months free.

What Counts as a Page

The knowledge base accepts several kinds of source, and each one adds content that Mio can use. Under Mio AI, then Knowledge base, you can add your website, single pages, question and answer pairs, free text and files. When you add your website, Mio reads every public page on the same domain and respects robots.txt. Files can be PDF, DOCX, TXT, MD, CSV or HTML, up to 15 MB each. Sources can be re-read on demand with the Re-read option, so that changes on your site reach Mio without rebuilding anything.

The documentation speaks of pages, so think in pages rather than in files or words. A website crawl can create many pages from one source, because each public page is a page. A long PDF is stored as content from one file. If you are unsure how a particular source is counted, check the usage figure on the Subscription page before and after you add it. This takes a minute and shows the real effect, which is better than a guess.

How to Count Your Pages Before You Add Them

You can estimate your need in about fifteen minutes. First, list the content that customers actually ask about. Second, count the public pages that carry that content. Third, add the files you plan to upload. A simple method is to open your sitemap, which many sites publish at /sitemap.xml, and count the entries. The general idea of a sitemap is simple: it is a list of the pages you want search engines to find. The same list shows how many pages Mio would read from your domain.

Open your sitemap and count the pages.
Mark the pages that customers never ask about, such as old news, tag archives and login pages.
Add the number of Q&A pairs and files you plan to write.
Compare the total with the limit on the pricing page.

If the total is higher than your plan allows, do not rush to upgrade. Many sites have a lot of pages that Mio does not need.

Which Sources to Add First

When space is limited, order matters. Start with the pages that answer the questions you receive most often, then widen. A reliable order is the following.

Policies: delivery, returns, warranty, payment, privacy and opening hours.
Prices and plans: the pages that state what things cost and what is included.
Frequently asked questions: they are already written as questions and answers.
Product or service pages: the main ones, not every variation.
Manuals and guides: as files, if customers ask how to use something.

Our guide to training an AI chatbot on your website content shows this order in more detail, and the article on what not to include in a knowledge base explains which content to leave out.

Question and Answer Pairs Save Space

A question and answer pair is the most compact way to give Mio a fact. If your website explains a return policy in a long page full of marketing text, one clear pair, written in the way customers ask, can answer the question better and takes less room. Pairs are also the right place to fix a weak answer that you see in Try Mio: write the question as the customer wrote it, and give the answer you want. Our guide to AI chatbot instructions explains how to guide Mio when a fact is missing.

Do not duplicate. If the same policy appears in the website crawl, in a PDF and in a pair, you spend three pages on one fact, and you risk conflicting wording when one source changes. Keep one source of truth for each topic, and delete the others.

Keeping the Knowledge Base Lean

A lean knowledge base is not only cheaper; it also gives better answers, because Mio has fewer contradictory pieces to choose from. Review the list every quarter. Remove pages about discontinued products, finished campaigns and old prices. Re-read sources after you change the website. Use the business instructions to tell Mio what to do when it is not sure, for example to hand the chat to the team rather than guess. Our guide to keeping an AI chatbot knowledge base up to date offers a routine.

If you only need a part of a large website, add single pages instead of the whole domain. This is common for shops with thousands of product pages: add the policy pages, the category overview and a CSV with the price list, and leave the rest to the product search on your site.

Signs That You Need a Bigger Limit

Upgrade when the content is useful, not merely because it exists. Signs that a larger plan is justified include frequent chats that Mio hands over because the answer is on a page that you could not add, a support team that keeps asking for another manual to be added, or a second website with its own content. The plan also changes other things, such as operators, websites and AI answers, so look at the whole table. The Free plan has no card and no time limit, which makes it a good place to learn what Mio needs. The pricing page lists every plan side by side.

If the limit is close and the answer quality is already good, a cleanup is cheaper than an upgrade. If the limit is close and you keep cutting useful content, upgrade.

A Worked Example

Take an online shop with 140 public pages: 90 product pages, 30 blog posts, 12 policy and help pages and 8 service pages. It also has two PDF manuals and a CSV price list. On the Free plan, with 20 pages, the shop cannot add the whole domain. A sensible Free setup would add the 12 policy and help pages, write six question and answer pairs for the most common questions and upload the price list, staying close to the limit. On Pro, with 200 pages, the shop could add the whole domain and the files, but it would be wiser to leave out the blog and keep the room for growth. This is the reasoning to repeat for your own site: choose by the questions customers ask, not by the number of pages.

Limits, Answers and Cost Together

Knowledge base page limits are only one of the numbers on the plan card, and the others interact with them. A bigger knowledge base does not increase the number of AI answers you get each month, and more AI answers do not help if the content is missing. Think of three dials: how much Mio knows, how many questions it can answer in a month and how many people on your team can step in. A shop with a small catalogue and many visitors needs answers more than pages. A company with a huge help centre and few visitors needs pages more than answers. The knowledge base idea is old, but the practical question is always the same: what do your customers ask, and where is the answer written?

Look at your last fifty customer questions and sort them by topic. You will usually find that ten to twenty topics cover most of them. Those topics, written well, often fit comfortably inside the Free or Pro limit. Pages you add beyond that give smaller and smaller gains, and they raise the risk that two pages say slightly different things.

Checking the Result After You Add Sources

After every large addition, run a short test. Open Try Mio and ask the ten questions you receive most. Check that each answer is correct, that it uses the right pieces and that nothing outdated appears. Then ask five questions that are not in your content, and make sure that Mio says it is not sure and hands the chat to your team instead of inventing an answer. Our guide on testing an AI chatbot before launch offers a full list of tests. Keep the questions in a document, and repeat them every time you change a source, so that you notice a regression the same day.

Knowledge Base Page Limits for Agencies and Several Sites

If you manage chat for several websites, remember that each website has its own content to teach. Plans include a number of websites, and knowledge base page limits apply to the content that Mio keeps for your account. An agency that supports five small client sites on a plan with a few hundred pages needs to budget carefully: three clients with large shops can use everything. Give each site a short list of must-have sources, and agree with the client which pages are the single source of truth.

When a client wants everything added, show them the usage figure and the question list. Most clients are persuaded when they see that twenty well-written pages answer the questions that customers really ask, and that the remaining pages mostly repeat the same facts. Knowledge base page limits, in other words, are a useful excuse to tidy the content, and tidy content also helps search engines and human readers.

Finally, record your decisions. Keep a short note for each site with the sources added, the date and the reason. Six months later, when someone asks why a page is missing, you will know whether it was a deliberate choice or an oversight, and you will not spend an hour guessing.

Frequently Asked Questions

How many knowledge base pages does each plan include?

According to the pricing page, Free includes 20 pages, Pro 200, Ultimate 1000, Enterprise 50 includes 5000, Enterprise 100 includes 10000 and Enterprise 500 includes 50000. Plans and limits can change, so always check talkmio.com/pricing for the current numbers before you decide.

Where can I see how many pages I have used?

Open Settings, then Subscription. The page shows your current plan and your usage next to the limits, so you can see how close you are to the ceiling before you add a large source such as a full website, and decide whether to upgrade.

Does adding my website use all my pages?

Mio reads every public page on the same domain and respects robots.txt, so a large site can use many pages. If your plan is small, add single pages, question and answer pairs or files instead of the whole domain.

What file types can I upload?

You can upload PDF, DOCX, TXT, MD, CSV and HTML files up to 15 MB each. Sources can also be re-read on demand with the Re-read option, so an updated file or page reaches Mio without any rebuild of the assistant.

Should I upgrade or clean up first?

Clean up first if the limit is close and answer quality is already good. Remove outdated and duplicate pages and keep one source for each topic. Upgrade only if you keep having to remove content that customers really ask about every week.

The Bottom Line

Knowledge base page limits are a planning tool, not an obstacle: count your pages, add policies and prices first, use question and answer pairs for compact facts and keep the list lean. Check the pricing page for the current numbers and your usage on the Subscription page. Start free with Talkmio, add your most important pages and see how far 20 of them take Mio.

Knowledge Base Page Limits: How Many Pages Does Mio Need?