This page is a draft outline and is not indexed yet. Monitoring for VitePress sites already works.
VitePress docs monitoring
Draft. This outline will be expanded with verified, platform-specific detail.
How VitePress sites typically break
- Sidebar config in
.vitepress/configdecides reachability; unlisted pages become orphans. TODO(verify) - Heading anchors are generated from heading text with optional custom ids. TODO(verify):
{#custom-id}support cleanUrlstoggles/pagevs/page.htmland needs matching server configuration (verified 2026-09-17).
What the VitePress build catches, and what it misses
- Builds fail on dead internal links by default;
ignoreDeadLinksrelaxes this (verified 2026-09-17). - Misses external links, anchors from other sites, sitemap drift and orphans.
Setting up redirects on VitePress
- Host-level redirects (
vercel.json, Netlify_redirects); VitePressrewritesmap source directories to URLs ('source/:page': 'destination/:page') but are not HTTP redirects (verified 2026-09-17).
How PathIntact monitors a VitePress site
- Detection via the
VitePressgenerator meta tag andVPclass names (verified 2026-09-17 against vitepress.dev); static reading; Vercel redirect snippet by default.
Check a VitePress site now
Free 50-page crawl with broken links, anchors, orphans and sitemap problems.
Guides
Last updated 2026-09-16. VitePress is a trademark of its owner; PathIntact is not affiliated.