Skip to content

Crawl bigger documentation sites, and see exactly what made it in

The Crawled Pages dialog for the web source Help Centre — Billing, with 61 pages indexed, 2 skipped and 1 failed, each row showing its status and reason, and the highlighted reason HTTP error (404) of the failed page.The Crawled Pages dialog for the web source Help Centre — Billing, with 61 pages indexed, 2 skipped and 1 failed, each row showing its status and reason, and the highlighted reason HTTP error (404) of the failed page.

When the assistant answers from your documentation, you need to know which pages it actually has. Web sources now read more kinds of documentation site, cover larger ones, and show you every page the crawler found and what happened to it.

  • AI-friendly documentation sites. When a site publishes AI-friendly Markdown versions of its pages, StrikeUp reads those instead of the cluttered web page, and a page that duplicates another is skipped rather than stored twice.
  • Up to 500 pages per source. Set the page limit as high as 500, so a large help centre fits in one web source.
  • Every page, with its result. View Pages lists each address the crawler found, whether it reached the knowledge base, and why not when it did not: a duplicate, too little content, an error or the page limit.
  • Refresh one page. Re-crawl this page fetches a single page again without re-crawling the whole site.
The "Crawled Pages" dialog for the web source "Help Centre — Billing", summarised as "61 indexed · 2 skipped · 1 failed", with the filters All, Indexed, Skipped, Failed and Excluded. The table lists each page, with a checkbox, with its title and address, status, size and crawl time; pages such as "Invoices" and "Update your card" are "Indexed", "Print view" is "Skipped" as a duplicate and "Contact billing" for too little content. The reason "HTTP error" of the failed page "2019 pricing" is highlighted. Each row can be re-crawled on its own.The "Crawled Pages" dialog for the web source "Help Centre — Billing", summarised as "61 indexed · 2 skipped · 1 failed", with the filters All, Indexed, Skipped, Failed and Excluded. The table lists each page, with a checkbox, with its title and address, status, size and crawl time; pages such as "Invoices" and "Update your card" are "Indexed", "Print view" is "Skipped" as a duplicate and "Contact billing" for too little content. The reason "HTTP error" of the failed page "2019 pricing" is highlighted. Each row can be re-crawled on its own.
See every page a crawl found, whether it reached the knowledge base, and why not.
What this screenshot shows
Screen
Crawled Pages (/admin/knowledge-base)
Highlighted
“”, pages-table, failed page. none
Also visible
Summary 61 indexed · 2 skipped · 1 failed; Reasons: Duplicate of another page, Too little content, HTTP error
Purpose
hero of the web sources release note: the crawled pages list

A page that silently failed is a question the assistant cannot answer. Seeing every page with its reason tells you what to fix on your site or in the source’s filters, and refreshing one updated page takes seconds instead of a full crawl.

  1. Open ConfigureKnowledge Base and add a web source with your documentation’s address, or edit an existing one to raise its page limit.
  2. When the crawl has run, select View Pages on the web source and filter for skipped or failed pages.
  3. After you change a page on your site, select Re-crawl this page on its row.

The details are in Check crawled pages.

For every workspace with the knowledge base. Web sources accept public http and https addresses only. Crawls do not repeat on their own: sync a source, or refresh single pages, after your site changes. At the default speed of 20 pages a minute, a 500-page crawl takes about 25 minutes.