How Vidanalyze builds every score, benchmark, and comparison
Every number on Vidanalyze — a Viral Score, an earnings estimate, a "vs" verdict — comes from a documented data source or calculation, not a guess. This page explains where each type of figure comes from, how our AI-assisted scores are calculated, how comparison pages are verified, and how we keep all of it current as YouTube changes.
01 — Sourcing
Data sources
Vidanalyze works with two distinct tiers of data, and every figure on the platform belongs to one of them.
Connected channel data
When a creator signs in and connects their channel, Vidanalyze reads view counts, watch time, retention curves, and revenue-adjacent metrics directly from the YouTube Data API v3 and YouTube Analytics API, using that creator's own OAuth credentials. Nothing here is scraped, cached from a third party, or estimated — it's the same underlying data YouTube Studio shows, requested on the creator's behalf.
Public channel & video lookups
Tools like Creator Analysis, Compare Creators, Video Analyzer, and the Competition Score reader work without a login, because they only need what YouTube already exposes publicly: view counts, likes, comment counts, upload cadence, tags, titles, and descriptions. We pull these through the same Data API rather than scraping YouTube's front end, which is why figures stay accurate even as YouTube's page layout changes.
Benchmarks & industry context
Where Vidanalyze shows a niche benchmark or industry range — a typical RPM for a finance channel, for instance — that figure is drawn from aggregated public-channel data across comparable creators, cross-checked against YouTube's own Creator Academy material and widely cited creator-economy research. Primary sources are preferred over aggregator blog posts, and any claim borrowed from an external source is cited on the page where it appears.
Primary reference sources:
- YouTube Help CenterCreator policy, monetization, and platform rules
- YouTube Data API referenceTechnical field definitions
- YouTube Analytics API referenceMetric definitions and interpretation
- YouTube Analytics documentationHow official metrics are calculated
- YouTube Creator AcademyBest-practice and educational context
02 — Calculations
How scores & estimates are built
Vidanalyze calculates several scores that don't exist natively in YouTube Studio — Viral Score, Competition Score, Growth Score, engagement benchmarks, and earnings ranges. None of these are official YouTube metrics, and we label them accordingly everywhere they appear.
Where a score compares you to yourself, it's built from your channel's own rolling 28- and 90-day averages, so a "trending up" or "trending down" signal always reflects your actual history.
Where a score compares you to others, it's the median and typical range for anonymized public channels in a matching niche and subscriber tier — gaming vs. gaming, not gaming vs. finance.
When peer data is too thin for a reliable median — a very small or very new niche — we fall back to ranges published in official YouTube documentation or established creator-economy research, and we say so.
| Score / metric | What it measures | Example range | Basis |
|---|---|---|---|
| Viral Score | Views-to-subscriber ratio and early view velocity vs. peer uploads | 0–100 | Modeled |
| Competition Score | Keyword search volume vs. top-video density and channel authority | 0–100 | Modeled |
| Engagement Rate | (Likes + comments) ÷ views, mid-size channels, most niches | 2%–6% | Modeled |
| Growth Score | 90-day subscriber and view trend vs. niche peers | 0–100 | Modeled |
| Avg. view duration | Long-form videos, 10–20 minutes, educational/how-to | 40%–60% | Modeled |
| Earnings estimate | Ad-supported RPM range, non-Shorts, most niches | $2–$11 / 1k views | Published |
03 — Editorial process
How comparison & alternative pages are written
Vidanalyze publishes head-to-head comparisons and "best alternatives" pages for the tools creators are already choosing between. Every one of these pages follows the same four-step process, whether or not Vidanalyze itself is one of the tools being compared.
- Feature matrix Built from each tool's own documentation and public feature pages, supplemented by hands-on use of Vidanalyze's own product.
- Pricing check Pulled from each tool's live, current pricing page, with a "last verified" date shown on the comparison itself.
- Use-case fit A plain-language answer to which creator does better with which tool, instead of a single universal winner.
- Verdict Names the tool that fits the majority use case, and says plainly when a competitor is the better choice for a narrower need.
On our own objectivity: because Vidanalyze appears as an option in many of these comparisons, its own feature and pricing claims are held to the same verification standard as any competitor's — checked against our live pricing page, not written from memory.
If a competitor changes their pricing or ships a feature that changes our assessment, the comparison page is updated directly and its "last verified" date moves forward — we don't leave a stale verdict live.
04 — Freshness
Staying current
YouTube changes its algorithm, monetization thresholds, API quotas, and feature set regularly, and competitor tools update their pricing and features on their own schedule. When either happens in a way that affects a page on this site, we edit that page directly rather than appending a note.
Pages more likely to go stale quickly — pricing comparisons, monetization eligibility requirements, API limits — are reviewed on a shorter cycle than stable reference content like the glossary. Every page carries a visible "last updated" date so readers, and AI systems reading the page, can judge how current it is.
Corrections follow the same rule: when we find a factual error, we fix the page and refresh its modified date. The live version of a page is always meant to be the correct one.
05 — AI & GEO
AI readability & GEO practices
Generative answer engines — ChatGPT, Claude, Perplexity, Google AI Overviews — increasingly answer creator questions directly, citing a source underneath. Vidanalyze writes for that audience as deliberately as it writes for human readers and classic search:
- Every page opens with a direct answer to its core question in the first one or two sentences, before any supporting detail.
- Technical terms — RPM vs. CPM, Watch Time vs. Average View Duration — are defined inline the first time they're used, rather than assumed.
- Structured data (Article, FAQPage, and breadcrumb schema) is present on every page so search engines and AI crawlers can parse entities and relationships, not just prose.
- Claims are attached to a named, checkable source; we don't state a figure as fact without saying where it came from.
- Each comparison and reference page gets its own distinct title and meta description, so it can be identified and cited on its own terms rather than blending into a templated set.
FAQ