onesignal.com llms.txt
In short
onesignal.com serves a 3.1 KB llms.txt with 9 H2 sections and 1 link, graded C on the llmstxt.org structure (4 of 6 checks). It lacks a blockquote summary and a linked H2 section. The home page does not link it, so an agent that does not guess paths will not find it. An llms-full.txt is served too.
llms.txt 3.1 KB, 86 lines
> Full documentation index, SDK/API links, and AI usage guidelines: [llms-full.txt](https://onesignal.com/llms-full.txt)
# OneSignal
OneSignal is a lifecycle customer engagement platform. It helps product, marketing, and engineering teams drive activation, retention, and revenue through orchestrated messaging across mobile push, web push, email, SMS/RCS, in-app messaging, and iOS Live Activities[…]delivering personalized, real-time experiences from onboarding to re-engagement at global scale.
## Scale (onesignal.com homepage)
* **1 in 4** […] App publishers use OneSignal
* **1.3 trillion** […] Messages sent a year
* **1.5 billion** […] MAU powered by OneSignal
* **200k** […] Apps powered by OneSignal
## Product
### Messaging Channels
* Mobile push: https://onesignal.com/mobile-push
* Web push: https://onesignal.com/web-push
* Email: https://onesignal.com/email
* SMS & RCS: https://onesignal.com/rcs
* In-app messaging: https://onesignal.com/in-app
* Live Activities: https://onesignal.com/live-activities
### Lifecycle & Automation
* Journeys (automation): https://onesignal.com/journeys
* Event-based messaging & triggers (Journeys): https://documentation.onesignal.com/docs/en/journeys-overview
* User segmentation: https://documentation.onesignal.com/docs/en/segmentation
### Personalization & Data
* User profiles & data: https://documentation.onesignal.com/docs/en/users
* Tags & dynamic content: https://documentation.onesignal.com/docs/en/add-user-data-tags
### Analytics & Optimization
* Message analytics: https://documentation.onesignal.com/docs/en/analytics-overview
* Outcomes tracking: https://documentation.onesignal.com/docs/en/custom-outcomes
* A/B testing: https://documentation.onesignal.com/docs/en/ab-testing
## Use Cases
* User activation & onboarding
* Lifecycle messaging & retention
* Churn prevention & re-engagement
* Transactional notifications
* Promotions & announcements
* Personalization at scale
## Why OneSignal
* Unified platform across mobile push, web push, email, SMS/RCS, and in-app messaging
* Real-time delivery at global scale
* Built for both developers and marketers
* Flexible APIs and SDKs for fast integration
* Designed to drive measurable lifecycle outcomes
## Developers
* Documentation: https://documentation.onesignal.com/
* API Reference: https://documentation.onesignal.com/reference
* SDKs & setup guides: https://documentation.onesignal.com/docs/en/developers
* Quickstarts: https://documentation.onesignal.com/docs/en/quickstart-guide
## Customers & Industries
OneSignal is used by mobile apps, SaaS companies, e-commerce platforms, media companies, and marketplaces to improve engagement and retention.
## Pricing
First 70 of 86 lines. 5 spans shown as […] because the words or characters in them are rejected by this site's own style rules; the live file has them.
Parse graded C, 4 of 6
file: https://onesignal.com/llms.txt
OneSignal
No blockquote summary.
9 sections, 1 link, no Optional section.
Ora's cached score: 63, grade C, scanned 26 August 2026.
The parse
onesignal.com lists 1 link: 1 point at onesignal.com or a relative path, 0 point elsewhere. The hosts it links most: onesignal.com (1).
| H2 section | Links |
|---|---|
| Scale (onesignal.com homepage) | 0 |
| Product | 0 |
| Use Cases | 0 |
| Why OneSignal | 0 |
| Developers | 0 |
| Customers & Industries | 0 |
| Pricing | 0 |
| Resources | 0 |
| Company | 0 |
Grade against the llmstxt.org structure
The file passes 4 of 6 checks and fails 2: has a blockquote summary under the h1; has at least one h2 section that lists links. The grade is the count of passed checks: six is A, five is B, four is C, three is D, fewer is F. It measures structure only. Whether any agent reads the file is a separate question, covered on the llms.txt reference.
| Check | Result | Detail |
|---|---|---|
| Starts with an H1 naming the site or project | Pass | H1: OneSignal |
| Has a blockquote summary under the H1 | Fail | No blockquote summary before the first H2. |
| Has at least one H2 section that lists links | Fail | 9 H2 sections, 0 with links. |
| At least 80 percent of links point at the same site | Pass | 1 of 1 links stay on onesignal.com (100 percent). |
| Under 100 KB | Pass | 3140 bytes as served. |
| Plain markdown, no HTML | Pass | No HTML document markers in the body. |
Ora's cached score
Ora's cached report for onesignal.com gives it 63 of 100, grade C, scanned on 26 August 2026. Its Access layer, which holds the read-layer checks below, scored 42 of 61 check points. Read from GET ora.ai/api/score/onesignal.com on 5 November 2026. The score is Ora's, not this site's, and the structure grade above is a different measure: it grades the llms.txt file against the llmstxt.org proposal, while Ora's score covers the whole site. Ora's report for onesignal.com has every layer.
| Ora check (Access layer) | Result | Points |
|---|---|---|
| Sitemap exists | Pass | 2 of 2 |
| Content without JavaScript | Pass | 2 of 3 |
| Not blocked by bot detection | Pass | 2 of 2 |
| Markdown URL fallback | Fail | 0 of 2 |
| llms.txt exists | Pass | 1 of 1 |
| llms.txt formatting | Partial | 1 of 2 |
| JSON-LD structured data | Partial | 1 of 4 |
| Metadata completeness | Pass | 2 of 2 |
| llms.txt links resolve | Fail | 0 of 2 |
| Markdown alternate link | Fail | 0 of 1 |
| Redirect hygiene | Pass | 1 of 1 |
| Page token budget | Pass | 1 of 1 |
| Code fence validity | Pass | 1 of 1 |
| Content behind auth | Pass | 2 of 2 |
| OpenAPI spec published | Fail | 0 of 7 |
| Markdown agent docs | Pass | 1 of 1 |
| Markdown negotiation with Vary | Pass | 1 of 1 |
| Markdown for agent user agents | Fail | 0 of 1 |
| Agent crawler reachability | Pass | 2 of 2 |
Linking and the companion file
The home page of onesignal.com does not link the file in its HTML. Ora's lab found (2026-10-19) that 86 percent of llms.txt fetches by agents arrived through a link, so an unlinked file is mostly a file nobody opens. An llms-full.txt is served at the same root.
How it compares
At 3.1 KB the file is larger than 17 percent of the 2,529 plain-text llms.txt files in this edition, and its 1 link put it ahead of 10 percent of them on link count. The home page declares a Craft CMS generator. Size bucket: 2 to 10 KB. Tranco rank 1,034. Category: Communication & Support.
Live file: https://onesignal.com/llms.txt. Read 4 November 2026. If the file has since changed or gone, the live URL is the authority; this page records what the crawl read on that date.
Sources
- onesignal.com llms.txt https://onesignal.com/llms.txt, read 4 November 2026
- llms.txt proposal (llmstxt.org) https://llmstxt.org/, read 4 November 2026
- Tranco list 746WX (crawl universe) https://tranco-list.eu/list/746WX, read 4 November 2026
- Ora: AgentReady launch post (the 86 percent finding) https://ora.ai/blog/agentready-launch, read 4 November 2026
- Ora llms.txt (GET /api/score/{domain} looks up a cached score) https://ora.ai/llms.txt, read 5 November 2026
Last reviewed 5 November 2026