Existing-file audit
See missing, malformed, out-of-scope, duplicate, and unverified entries with evidence.
Crawl your real SaaS product, pricing, documentation, integration, trust, and resource pages. Audit the current file and get a grounded llms.txt plus a complete prompt for any coding agent.
Useful SaaS context is spread across product, use-case, pricing, documentation, integration, security, customer, and educational pages. The generator discovers and validates those pages before writing a description or exposing a URL.
See missing, malformed, out-of-scope, duplicate, and unverified entries with evidence.
Gemini must cite exact text from validated candidate IDs; deterministic code controls every URL.
Copy or download llms.txt, JSON evidence, and a Markdown implementation prompt.
Scope, failures, robots conflicts, truncation, and output validation remain visible.
Read the current llms.txt and bounded sitemap discovery sources. Missing files and unreadable responses remain distinct.
Classify canonical, index-eligible SaaS pages outside the model, then require exact quotes from immutable candidate IDs.
Verify quotes and claim overlap, then reject invented IDs, URLs, duplicates, unsafe text, invalid Markdown, and unsupported output.
llms.txt is an emerging proposal. It does not replace normal crawlability, indexability, internal links, accurate visible content, or structured data. Read the llms.txt proposal and Google's AI search guidance.
It creates a small Markdown map of validated product, pricing, documentation, integration, trust, customer-evidence, and resource pages so an agent that supports the proposal can find useful first-party context.
There is no ranking guarantee. llms.txt is an emerging proposal rather than a Google Search requirement. Crawlable pages, indexability, useful content, internal links, and accurate visible structured data remain the foundations.
No file is offered unless Gemini 2.5 Flash uses server-supplied candidate IDs and exact page quotes, and the result passes deterministic quote, claim-overlap, URL, duplicate, length, safety, and Markdown checks.
No. It reads authorized public pages and returns private files, evidence, and a repository-aware implementation prompt. You or your coding agent decide what to publish.
The result states exactly what was discovered and analyzed, marks the output partial, and tells the coding agent to compare authoritative repository routes before publication. It never calls a truncated inventory complete.
Blogged plans, writes, interlinks, reviews, and publishes product-aware SaaS content while keeping its public discovery surfaces current.
Start free