Skip to main content

TradingView Compliance Checklist

Publication Type

  • Public Open-Source: Fully compliant with all TradingView rules
  • Public Invite-Only: Compliant + vendor requirements
  • Private: For testing/drafts only

📝 Title Compliance

Required Checks

  • English only - No non-English words or phrases
  • ASCII characters only - No emoji, special characters, or Unicode
  • Proper capitalization - No ALL CAPS except abbreviations (RSI, MACD, EMA, etc.)
  • Descriptive and clear - Hints at script's purpose/functionality
  • No misleading claims - No "90% win rate" or similar unsubstantiated claims
  • No advertisements - No website references, social media handles, contact info

Examples

Good: "MACD RSI Divergence Detector with Multi-Timeframe Analysis" ❌ Bad: "🚀 BEST MACD INDICATOR - 90% WIN RATE!!! 💰"


📄 Description Compliance

Structure Requirements

  • Self-contained - Complete explanation without relying on external links
  • English first - If using other languages, English explanation comes first
  • Original content - Explains how script is original and unique
  • Clear functionality - Details what it does and how it works
  • Usage instructions - How to use the script effectively
  • Technical details - Underlying concepts and calculations

Content Quality

  • No unsubstantiated claims - All performance claims are documented
  • Honest limitations - Script shortcomings are mentioned
  • Proper attribution - Credits given for any reused open-source code
  • Clear language - Accessible to traders who don't read Pine Script
  • Professional tone - No excessive emoji, maintains readability

Open-Source Specific

  • Detailed explanations - Compensates for users who can't read Pine
  • Code documentation - Major functions and logic explained
  • Parameter guidance - Input meanings and recommended values

Closed-Source Specific

  • Unique value justification - Explains why code protection is needed
  • Sufficient detail - Enough info for users to understand capabilities
  • No reproduction claims - Doesn't claim to replicate open-source scripts

📊 Chart Compliance

Visual Requirements

  • Clean chart - Only necessary visuals, remove extra scripts/drawings
  • Script visible - Current script outputs are clearly displayed
  • Standard chart type - No Heikin Ashi, Renko, etc. for strategies/signals
  • Default settings - Script uses default parameters, not customized
  • Complete information - Symbol, timeframe, and script name visible
  • Status lines enabled - Chart and script titles/information shown

Chart Type Restrictions (for Strategies/Signals)

  • Standard candlesticks - Not using synthetic price types
  • Regular timeframes - No unusual or custom time intervals
  • Real price data - Actual OHLC values, not calculated/modified

⚙️ Strategy Compliance (if applicable)

Realistic Settings

  • Reasonable initial capital - Realistic starting amount for average trader
  • Realistic commission - Approximates real-world trading costs
  • Realistic slippage - Accounts for market impact
  • Sustainable risk - ≤5-10% risk per trade typically
  • Sufficient trades - Ideally 100+ trades in backtest
  • No warnings - Strategy Tester shows no caution warnings

Technical Requirements

  • No lookahead bias - No request.security() calls with future data
  • Proper timeframes - Uses appropriate timeframe for strategy type
  • Default properties - Uses settings defined in strategy() declaration
  • Documented settings - Strategy properties explained in description

🔄 Code Reuse Compliance

Attribution Requirements

  • Original author credited - Name mentioned in description
  • Significant improvements - Not just style changes or minor tweaks
  • Open-source publication - Required unless explicit permission or public domain
  • Public domain exceptions - Only for TradingView built-ins or public libraries

Originality Assessment

  • Unique approach - Not rehashing existing indicators
  • Value addition - Improves or combines concepts meaningfully
  • Personal expertise - Reflects author's interests/knowledge
  • Community benefit - Adds value to TradingView ecosystem

🚨 Alert System Compliance

Functionality

  • No misleading signals - Alerts represent actual script logic
  • Proper timing - No future-looking or repainting alerts
  • Clear conditions - Alert triggers are well-documented
  • Testing verified - Alert behavior confirmed in testing

📋 Final Pre-Publication Review

Technical Validation

  • Pine syntax valid - Script compiles without errors
  • Performance optimized - No unnecessary loops or heavy calculations
  • Version current - Using Pine Script v5 or v6
  • Input validation - Proper minval/maxval/options parameters

Content Review

  • Grammar checked - Professional writing quality
  • Links functional - Any internal TradingView links work properly
  • Images relevant - Chart snapshots support description points
  • Formatting correct - TradingView markup properly applied
  • License appropriate - Mozilla Public License 2.0 for open-source
  • Terms understood - Familiar with TradingView publishing rules
  • Vendor requirements - Additional rules for invite-only scripts (if applicable)

📤 Publication Process

Pre-Publication

  • Private draft created - Test publication as private first
  • Content verified - All elements appear correctly
  • Errors fixed - Any issues resolved before public release
  • 15-minute rule understood - Public scripts only editable for 15 minutes

Post-Publication

  • URL documented - Publication link saved for records
  • Archive created - Description and version archived locally
  • Monitoring setup - Watching for moderator feedback
  • Community engagement - Ready to respond to user questions

⚡ Common Pitfalls to Avoid

Don't: Use non-English titles ❌ Don't: Make unsubstantiated performance claims
Don't: Include advertising or contact info in public scripts ❌ Don't: Rehash existing indicators without significant improvement ❌ Don't: Use non-standard charts for strategies ❌ Don't: Publish cluttered charts with multiple scripts ❌ Don't: Rely on external links for script understanding ❌ Don't: Forget to credit reused open-source code ❌ Don't: Rush public publication (use private drafts first)

Do: Focus on originality and community value ✅ Do: Provide comprehensive, self-contained descriptions ✅ Do: Use clean, professional chart presentations ✅ Do: Test thoroughly with private publications first ✅ Do: Follow realistic strategy parameters ✅ Do: Engage positively with community feedback


Last Updated: 2024-07-08 Review Required: Before each public publication