For multi-page marketing sites or docs where every route already exists in a standard sitemap.xml, Slash can fetch and index it directly instead of scanning individual pages. This is the easiest way to make an entire site searchable with no per-page setup.
1<slash-launcher api-key="YOUR_API_KEY" sitemap="/sitemap.xml"></slash-launcher>Slash fetches the sitemap once, caches it client-side, and derives a label for each <url> entry from its path segment — /docs/theming becomes "Theming", for example. Override this per-URL by publishing a parallel slash-sitemap.json alongside your sitemap with friendlier labels and categories.
slash-sitemap.json
12345678910{ "https://example.com/docs/theming": { "label": "Theming", "category": "Guides" }, "https://example.com/pricing": { "label": "Pricing", "category": "Pages" }}- Works well for static sites and docs where pages rarely change shape
- Refetched on an interval (default 1 hour) so new pages appear without a redeploy
- Best combined with Auto-Discovery for app shells where some routes aren't in the sitemap