Setting Up a Public Knowledge Hub That AI Assistants Can Use

Uploading company documents into Claude for your own team, for example in a project workspace, helps your staff but does not change what Claude tells the public. To help Claude and other assistants answer questions about your business, publish a public knowledge hub: well-organised pages with your company facts, product details, FAQs and help articles that crawlers can read.

Internal vs Public: An Important Difference

Many teams set up Claude with internal documents so employees get better answers about policies, products and processes. That is useful, but it stays inside your account. Someone outside your company asking Claude “which payroll software supports Belgian social security rules?” will not see your internal files. Public visibility depends on what is published openly on the web.

The good news: much of the work you did to organise internal knowledge can be reused for a public hub, after removing anything confidential.

What to Include in a Public Knowledge Hub

• Company fact page: name, what you do, founding year, locations, leadership, markets served.
• Product or service pages: one per offer, with features, limits, pricing approach and who it suits.
• FAQ: real buyer questions in their own words, with short direct answers.
• Help and documentation: setup guides, compatibility lists, troubleshooting steps.
• Policies: delivery, returns, warranty, data hosting, accessibility.
• Glossary: terms specific to your field explained simply.

How to Structure It

1. One topic per page. A page called “Does it work offline?” is easier to use than a long page covering twenty topics.
2. Clear URLs and titles. /help/export-invoices-to-csv/ says what the page is about.
3. Answer first. Start each article with the short answer, then the steps.
4. Link related articles so crawlers and readers can move between topics.
5. Date every article and review it when the product changes.

Make It Accessible to Crawlers

Many help centres are built on third-party platforms. Check that:

• Articles are public and do not require a login.
• The help centre is on a subdomain or folder of your main site, or clearly linked from it.
• robots.txt allows the crawlers you want, including search engines and AI crawlers.
• Articles are in an XML sitemap.
• Content is in HTML text, not only in videos or PDFs.

See technical SEO for AI crawlers for detail.

Example: A Small SaaS Company

A scheduling tool for clinics moves its internal sales FAQ into a public hub with pages such as “Does it send SMS reminders in France?”, “Can patients book without an account?” and “Where is data stored?”. When a clinic manager later asks an AI assistant whether a scheduling tool exists with those features, there is now clear public text that can support an answer.

Start Small

You do not need hundreds of articles on day one. Begin with the twenty questions your sales and support teams answer most often. Publish one clear page per question, then add more as new questions come in. A small hub that is accurate beats a large one that is out of date.

Keep Public and Internal Versions in Sync

When product details change, update both. Assign one owner for the public hub and add a review step to every product release. Outdated help articles are a common source of wrong AI answers.

For a broader look at preparing company information for AI, read optimizing corporate data for LLMs.

How Keboost Helps

Keboost tracks the questions customers ask about your products in Claude and other AI assistants, shows which answers are missing or wrong and helps create focused content to fill those gaps in your public hub. Run a free AI visibility check to find the first articles to write.