Page limits

How many pages each plan's knowledge can hold, what counts as a page, what happens when you reach the limit and how to make room without losing answers.

Last updated October 21, 2026

On this page

Every plan includes a number of pages: how many entries your workspace's knowledge can hold at once. This page explains what counts, where to see your usage and what to do when you reach the limit.

Limits by plan

Plan	Pages in your knowledge
Free	100
Starter	1,000
Pro	5,000
Business	25,000
Agency	100,000
Trial (14 days)	1,000

The limit is for the whole workspace, not per site. A Pro workspace with three sites can split its 5,000 pages between them in any way.

What counts as a page

In your knowledge	Counts as
A web page from a website or sitemap source	1 page
An uploaded file, however long	1 page
A text snippet, however long	1 page
A Q&A pair	Nothing: Q&A pairs have their own cap of 2,000 per site
A skipped, excluded or failed page	Nothing

Only entries that are In knowledge count. Pages that ASDK skipped as duplicates or as too short, pages you excluded and pages it couldn't read don't use your limit.

See your usage

Sites shows a line such as "1 of 3 sites · 1,240 of 5,000 pages on the Pro plan".
Knowledge shows the same page count for the workspace, plus how many pages and Q&A pairs the selected site has.

When you reach the limit

ASDK never deletes your knowledge because of the limit. What changes:

Pages already in your knowledge stay. They keep being read again on schedule and stay up to date.
New pages are skipped. They appear on the source's Pages list as Skipped with "Page limit of your plan reached: the Free plan includes 100 pages. Upgrade your plan, or remove or exclude pages you don't need." The source card says the same.
Agents keep answering from everything that is in your knowledge.

So the risk of a full knowledge isn't lost content: it is that a new product page or a new help article doesn't reach your agents.

Make room

Before you upgrade, check whether everything in your knowledge earns its place. Many sites have hundreds of pages that never answer a visitor's question.

Open a website source with Pages. Typical candidates: tag and category archives, author pages, old news, paginated lists, print versions, search results, job ads that closed long ago, and the same content in several languages when visitors use one.

Exclude whole sections with patterns

Choose Edit on the source and add paths to Skip pages under, such as /tag, /author or /**/print. Saving reads the source again and removes the skipped pages. See Exclude pages.

Exclude single pages

On the Pages list, choose Exclude on a page. It leaves your knowledge and ASDK won't read it again.

Cap a source

Set Most pages to read on a source, so a large section such as a blog can't take the room you need for product pages.

Remove on a page frees its place only until the next sync, which adds it back if it is still on your site. Use Exclude to keep it out.

Choose what to read first

When a workspace is close to its limit, the order of sources matters: pages are added as they are read, and the first ones fill the room. To make sure the important pages get in:

Add a sitemap of your key pages, or a website source that starts at your products or help section.
Keep large, low-value sections such as an archive blog out with Skip pages under.
Put facts that must always be right in Q&A pairs, which don't count toward the page limit.

Upgrade for more pages

If your site needs more room, a bigger plan raises the limit right away, and the skipped pages are added at the next sync, or immediately with Read again. During early access, billing is coming soon: to change plans, write to hello@asdk.com from your account's email with your Workspace ID. See Plans and limits.