Where the Numbers in This Knowledge Base Come From
This section contains many numbers. To verify them rather than take them on faith, we describe where each comes from, what is included in the denominator, and what these numbers do not prove.
Data Sources
| Group of Numbers | Source | How It Is Updated |
|---|---|---|
| Publications, checks, indexing | Working database of the platform: cascade node log | Continuously, as launches are executed |
| Indexability of sites | Own checks for the presence of a page in search | Background tasks, updated continuously |
| Weight transfer by the site | Sample reading the rendered DOM of live publications | As publications accumulate on the site |
| Domain Rating of sites | External link metrics service | Periodic synchronization |
| Positions, impressions, clicks | Client's Google Search Console | Daily snapshots, with a 2-3 day delay from Google |
| Portfolio growth aggregates | Calculation based on Pulse snapshots | Automatically, daily |
Rules We Adhere To
- The denominator is always named. A share without stating what it is calculated from is a useless number.
- Failures are included in the sample. Portfolio aggregates are calculated across all projects, not just selected ones.
- Growth is not presented as causation. The wording is "we record growth," not "we raised it": content, competitors, and algorithms change simultaneously.
- Small samples are not published. If there are few measurements, we write "not enough data yet" instead of a pretty percentage.
- Numbers have a date. Numbers in the articles carry the date they were calculated on and are reviewed when articles are updated.
What These Numbers Do Not Prove
They do not prove that your project will grow: the sample is not a forecast. They do not prove a causal relationship between publication and position. And they say nothing about a specific niche: in highly competitive topics, the distribution is different.
If You Found an Error
Write to support. An error in the numbers is more costly for us than an inconvenient number: an inconvenient one can be explained, an erroneous one cannot. Every statement about the platform's behavior in this knowledge base is verified against the code and data, not written from memory about the product.