Salus sells "a pip install plus a few lines of code", and the homepage, product and integrations pages all send developers to docs.usesalus.ai. But the quickstart, integration and webhook pages each return only the title "Salus Cloud" to any reader that does not run JavaScript, and the docs have no sitemap.xml, robots.txt or llms.txt. Many link previews, lighter crawlers and AI coding and research assistants read pages without running JavaScript. So when a developer pastes the quickstart link into their assistant and asks it to add Salus to a LangGraph or Vapi agent, the assistant gets an empty page. In search, every docs page has the same title.
First action
Open the quickstart with JavaScript disabled, confirm it is empty, and switch the docs build to static or server-rendered output.
How to measure it
Indexed docs pages with unique titles
- Now
- –
- Target
- Every docs page
- By
- 30 days
Steps
Confirm the gap
Fetch the quickstart, integration and webhook pages with JavaScript off and list what is missing.
Founder & CEO 1 hour
Pre-render
Static export or server rendering for every docs route.
Founder & CEO 2 days
Title each page
A unique title and description per page instead of "Salus Cloud".
Founder & CEO 1 day
Add sitemap and robots
docs sitemap.xml and robots.txt, submitted in Search Console.
Head of Growth 2 hours
Publish llms.txt
An index plus one full-text file with the quickstart, protect, webhook and executor patterns and framework examples.
Founder & CEO 1 day
Assistant test
Ask three coding assistants to add Salus to a LangGraph agent from the docs URL; fix whatever they get wrong.
Founding SWE / MLE 1 day
Measure
Indexed pages, docs search impressions and docs-to-/pilot clicks.
Head of Growth monthly
Why it works
Pre-render or statically export the docs so each page ships its text in the HTML. Give every page its own title and description, and add a docs sitemap and robots.txt. Publish an llms.txt index plus one full-text file covering the quickstart, the salus.protect pattern, the webhook pattern (Vapi, Retell, HTTP), the executor pattern and each framework example. Then test it the way developers actually work: fetch each page with JavaScript off, and ask two or three coding assistants to integrate Salus starting from the docs URL alone.
For a developer tool, the docs are the product page for the person who does the install. When the docs are readable, each topic can rank on its own for framework-specific searches, and assistants write correct integration code instead of guessing. That shortens the path from first visit to first protected route, and it costs a build setting, not a rewrite.
Ready to use
ChecklistReadable docs launch list
[ ] Quickstart, integration and webhook pages show full text with JavaScript off [ ] Unique <title> and meta description per page [ ] docs.usesalus.ai/sitemap.xml and robots.txt [ ] llms.txt index and llms-full.txt [ ] Install command and salus.protect example in the first screen of the quickstart [ ] Search Console property for the docs subdomain [ ] Three coding assistants produce a working integration from the docs URL
Risks and how to handle them
The docs framework can't export static pages
Serve a pre-rendered HTML snapshot per route to non-JavaScript readers.
Public docs expose more than intended
Publish only the integration patterns the marketing pages already describe; keep account-specific content behind login.
Evidence
- Your websiteDocs (fetched twice on November 10, 2026): docs.usesalus.ai, /docs/cloud-quickstart, /docs/integration and /docs/cloud-custom each return only the page title "Salus Cloud" to a reader that does not run JavaScript; docs.usesalus.ai has no sitemap.xml, robots.txt or llms.txt (all 404). The homepage, product and integrations pages send developers to these docs ("Read the quickstart", "Python integration", "Webhook integration").Source
- Your websiteHomepage (checked November 10, 2026): title "Salus — Runtime authorization for AI agents", H1 "Agents that act, safely."; "53% of organizations have already had an agent exceed its permissions." with no source; "Measured results" of −70.6% policy failures and +40.4% compliant completions on τ²-bench and −20.5% agent-model spend per successful task on CarBench, with no link to a method, paper or repo; a Python sample ("from salus import Salus" … "salus.protect(...)" around a do_refund tool) with no install command, package or GitHub link; a 59-second airline-booking demo; no customer logos or testimonials.Source
- Your websiteIntegrations page: frameworks LangChain, LangGraph, CrewAI, AutoGen, PydanticAI, LlamaIndex and Google ADK; voice and realtime Vapi, Retell, LiveKit Agents and Pipecat; MCP, HTTP, computer use and custom tool loops; three patterns (SDK, webhook for Vapi, Retell and HTTP, executor). None has its own page; all links go to the docs.Source
- News coverageY Combinator: Salus is in the Winter 2026 batch with a team of 2 and the description "Guardrails to validate your agent's actions before they execute". Its launch post claimed 58% of blocked actions recovered and completed correctly, "up to 60% lower cost" on τ²-bench and a 52% average misalignment reduction on ODCV-Bench across 12 frontier models, with onboarding as a pip install plus a few lines of code.Source