Well-known llms aliases for agent compatibility
Serve `/.well-known/llms.txt` and `/.well-known/llms-full.txt` alongside the root files so agents that follow the well-known convention can discover your corpus without guessing.
Why this can grow a startup
Agent clients do not all start from the same place. Some check the site root. Others look for a well-known path first. Shipping both removes an avoidable discovery failure and makes the machine-readable layer more durable if your docs stack or proxy setup changes later.
Source-backed example
Mintlify hosts `llms.txt` and `llms-full.txt` at both the site root and the `/.well-known/` paths for compatibility with tools that follow the well-known convention.
Source-reported evidence
Source: Mintlify Docs · Browse Mintlify Docs tactics
Mintlify serves both llms files at the root and at `/.well-known/` compatibility paths
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
Source discovered: May 27, 2026
When to use it
Use this when SEO, AI Search, Website is relevant to ai discovery, crawlability, technical seo and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to SEO and AI Search, using evidence from Mintlify Docs as context—not as a promised result.
- Record a baseline for: Qualified search visitors who complete the intended next action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Turn isolated search tactics into a crawlable visibility system tied to demand and proof.
SOURCE HUB
More tactics from Mintlify Docs
Explore related GrowthDex examples and evidence connected to Mintlify Docs.
Open Mintlify Docs source hub