Fact-Checking Policy — How YTKits Reviews Claims and Estimates
Our Commitment to Accuracy
At YTKits, we believe that accurate information is essential for creators to make informed decisions about their channels. This policy explains how we verify information, source our data, and handle corrections.
How We Verify Information
Primary Sources
All YTKits articles prioritize:
- Official YouTube Documentation: We link directly to YouTube's official guides, API documentation, and Creator Academy resources whenever discussing platform features or requirements.
- Personal observations: When an article discusses the author's channel, it identifies the experience as a personal observation rather than an industry result.
- Public reports: When public creator reports or third-party research are used, the article should explain their limitations and avoid presenting mixed reports as a controlled dataset.
What We Avoid
We do not:
- Present unverified claims as facts without clear qualification
- Use research from unrelated fields (e.g., UX design research) to support creator claims
- Publish statistics without explaining our methodology or data source
- Make promises about guaranteed results or channel growth
Personal Experience vs. Universal Claims
Many YTKits articles are written from personal experience running YouTube channels. We make a clear distinction between:
- "I observed..." — Personal testing on my own channel(s), which may not apply universally
- "YouTube's documentation states..." — Official platform information
- "Research shows..." — Published studies or data from multiple sources
We never present personal observations as universal guarantees. Your results may differ based on niche, audience, geography, and countless other factors.
Handling Corrections & Updates
Mistakes happen. When we discover inaccurate information, we:
- Correct the article — Update the content with accurate information immediately
- Update the date — Mark the article with the corrected date so readers know it was reviewed
- Document significant changes — Major corrections are noted in our Corrections page
- Acknowledge the source — Credit the person or source who pointed out the error
YouTube API & Data Verification
Tools like the YTKits Revenue Estimator use publicly available YouTube API data. We verify:
- Category data comes from YouTube's official category list via the Data API
- RPM/CPM ranges used by YTKits are adjustable scenario assumptions assembled from public reports, not official YouTube benchmarks or measured market averages
- Estimates are labeled as estimates — We never claim to predict exact earnings
Transparency About Limitations
We're transparent about what we don't know:
- YouTube's exact algorithm recommendations (not publicly disclosed)
- Proprietary advertiser demand data (varies by geography and time)
- Personal channel metrics we keep private (for privacy reasons)
- Future changes to YouTube's policies or features
When we discuss these topics, we clearly note that we're making informed observations based on available data, not absolute facts.
Affiliate Disclosures
YTKits mentions YouTube features, tools, and third-party services. We do not receive commission for recommending these services. We recommend tools and strategies based on genuine usefulness to creators, not financial incentive.
How to Report Inaccurate Information
Found an error? We appreciate the feedback. Please contact us with:
- The specific article and section with the inaccuracy
- What the correct information is
- A source or reference for the correction
Reports are reviewed as resources permit. Significant corrections are noted on the Corrections page.
Sources & References
Where an article relies on external factual claims, it should link close to the relevant statement or include a sources section. Sources may include:
- Official YouTube documentation
- Published research and reports
- Third-party studies and analyses
Policy Updates
This policy is updated as needed to reflect our fact-checking practices. Changes are documented with update dates so you know what we've modified.