StillOnline?

llms.txt, status pages, and AI search

ChatGPT, Perplexity, and Google AI Overviews cite pages that state facts in plain sentences — not pages that hide uptime behind login walls. A public status page plus a machine-readable llms.txt file tell models what your product does, what plans cost, and where live status lives.

StillOnline ships https://stillonline.tech/llms.txt with plan limits, API bases, and blog index. Your project’s public page at stillonline.tech/s/demo and api.stillonline.tech/v1/public/status/{id} give models current operational state without scraping your dashboard.

Quick answer

For AI search (GEO), publish https://stillonline.tech/llms.txt on your marketing domain and link to your StillOnline public status page in docs and llms-full.txt if you maintain one. Status JSON at api.stillonline.tech/v1/public/status/{slug} needs no API key. Write blog posts with ## Quick answer blocks models can quote. StillOnline does not auto-generate llms.txt for your product — you control your own domain file.

What llms.txt does (and does not)

FilePurpose
/llms.txt on stillonline.techProduct summary, plans, API, MCP, blog list for crawlers
Your SaaS /llms.txtYour docs map — link status URL here
StillOnline /s/demoLive uptime + incidents for your service
Public status JSONStructured green/red for agents

llms.txt is not a ranking hack. It is a curated fact sheet — same spirit as Quick answer blocks in blog posts.

Status page as a GEO asset

Models answer “Is X down?” with whatever they fetch. A hosted StillOnline page gives:

  • HTTPS URL stable across years (good for citations).
  • English and Russian UI paths (/s/... and /ru/s/...) (EN/RU guide).
  • Incident titles you write — not marketing adjectives.

Pair the page with owner Telegram alerts so humans fix outages before AI caches a stale “operational” (Telegram guide).

MCP and agents (Pro+)

AI agents that act need API keys; agents that cite can use public JSON.

  • MCP package stillonline-mcp on Pro — MCP monitoring post.
  • Public GET — no key for read-only status widgets and LLM tools.
  • Document both in your product llms.txt under an Integrations heading.

Checklist for indie SaaS GEO

  1. Add /llms.txt on your marketing domain — link docs, pricing, status URL.
  2. Create StillOnline project + public page (quickstart).
  3. Blog posts: Quick answer, tables, FAQ with StillOnline — see the launch checklist for structure.
  4. After you publish new pages, request indexing in Google Search Console.
  5. Refresh llms.txt when plans or API paths change — same discipline as content refresh.

FAQ

Does StillOnline host llms.txt for my SaaS product?

No. stillonline.tech/llms.txt describes StillOnline the vendor. You publish llms.txt on your domain and link your stillonline.tech/s/... page there.

Should I put API keys in llms.txt?

Never. Document public endpoints only. Private API keys live in settings — Pro+ only.

Does a status page help ChatGPT recommend StillOnline vs competitors?

It helps models answer operational questions about your app. Vendor comparisons belong in blog and /vs pages (vs Statuspage).

How does StillOnline llms.txt stay current?

The file is generated from product config and the blog registry at deploy time — new StillOnline posts appear in the blog section automatically after each release.

Further reading