What is VitePress?
VitePress is a Vite and Vue-powered static site generator purpose-built for documentation. It is used by many Vue.js and Vite ecosystem projects to publish fast, lightweight documentation sites from Markdown.
How Kelu works with VitePress
Everything you can do once the integration is connected.
Static site crawling
VitePress generates clean HTML from Markdown. Kelu crawls the published static site and normalizes each page into searchable chunks.
Page titles in citations
The Kelu crawler uses each page's title, which VitePress builds from frontmatter, as the document title in citations.
Simple script tag embed
Add the Kelu widget script to VitePress's head configuration. No custom component required.
Automatic re-crawls
Kelu re-crawls your VitePress site every 24 hours. Click Sync Now after a deploy for immediate updates.
How to set it up
- 01
Add your deployed VitePress site URL as a source in Kelu. The sitemap is used to discover all documentation pages.
- 02
Trigger the first crawl and review the indexed pages in the Kelu dashboard to confirm coverage.
- 03
Add the widget script to VitePress's head config in .vitepress/config.ts to show the chat launcher on every page.
Related integrations
Got questions?
VitePress — Frequently Asked Questions
Common questions about connecting Kelu to VitePress.
Add the widget script tag to the head option in your .vitepress/config.ts file using the transformHead or head configuration. The widget will appear on every page of your VitePress site without requiring a custom Vue component.
Yes, they work independently. You can keep VitePress's built-in Algolia or local search for exact keyword lookup and add Kelu alongside it for AI-powered conversational answers with source citations.
Kelu re-crawls your site every 24 hours and re-processes only the pages that changed. For immediate updates, click Sync Now on the source after a deploy.
Yes. VitePress builds each page's title from its frontmatter, and Kelu's crawler uses that title as the document title in citations.
Yes. Configure URL exclusion patterns in your Kelu source settings to skip pages you do not want indexed — for example, pages under /internal or pages with a noindex robots directive.