TradingView SMC indicators: compare the features you need

Compare published tools by scope

The table distinguishes features described by the authors from requirements you would need to implement in a custom script. It does not rank signal accuracy, execution speed or repaint behavior. "Not listed" means the cited publication does not establish that feature, not that every version lacks it.

• The fit assessments are editorial inferences from each tool's scope, not results of a chart benchmark.
• LuxAlgo's separate Price Action Concepts publication is invite-only and describes additional tools, including order blocks with volume data and liquidity grabs. Do not transfer its access rules or features to the free SMC publication.
• For a narrow task, inspect a focused tool first. A larger feature list is useful only if its definitions match your workflow.

Define what each SMC label means

SMC terminology does not specify one universal algorithm. Two indicators can label different candles while using the same event name. Compare their definitions before interpreting disagreements as bugs. Candle patterns alone cannot identify the participants behind a move.

Install a candidate and check its alert controls

In TradingView, open Indicators and search for the exact script title and author. Add the intended publication to the chart, then inspect its Inputs and the Condition menu in Create Alert. Similar titles can belong to different authors or access types.

• Start with one feature enabled. Record the script version, symbol, exchange, timeframe, session and inputs so that later comparisons use the same settings.
• For a bar-close workflow, confirm that both the signal logic and alert configuration wait for confirmation. A visible label does not imply that a matching alert is available.
• TradingView alerts run from a saved copy of the script and its settings. Recreate an alert after changing the script or inputs when you want those changes reflected.
• A webhook transports an alert to an external service. Order placement requires a separate execution system and its own validation.

Check timing and missing drawings before trusting a chart

Separate signal confirmation, historical plotting and drawing retention. They produce different effects on a chart and need different checks. Neither a large all-in-one script nor a small custom script is inherently free of repainting.

• Pivot confirmation: record the detection bar as well as the candle receiving the label. Right-side confirmation uses later bars, so a label positioned at the pivot was not necessarily available there in real time.
• Higher-timeframe data: closing the chart bar does not confirm an open higher-timeframe bar. TradingView documents combining a one-bar offset in the requested expression with barmerge.lookahead_on for confirmed higher-timeframe values. The requested timeframe must be higher than the chart timeframe; lookahead_on without the offset can leak future values.
• Retention: Pine allows up to 500 line IDs, 500 box IDs and 500 label IDs per script, with lower display counts by default. These are separate limits. Old drawings may disappear through garbage collection or deliberate script deletion; absence alone does not prove a signal repainted.
• Architecture: separate scripts can isolate settings and displays but add configuration work. One script can share state across features. Neither arrangement guarantees lower latency, and line count is not a performance measurement.

Use a repeatable comparison worksheet

The following is a proposed evaluation procedure; no comparative chart test has been run for this page. Use the same market, date range and inputs for each candidate, then keep the observations rather than assigning an unsupported "best" score.

• Bar Replay can help inspect historical event order. It does not replace recording realtime intrabar behavior and alerts.
• Keep the candidate that matches your definitions and timing requirements. If neither does, write down the mismatch before requesting a custom implementation.

Specify a custom combination before generating code

A useful custom SMC brief defines how modules interact. For example, require a confirmed structure break, select only gaps formed after that break, and alert once on a later qualifying retest. This is an implementation specification, not evidence of a profitable setup.

• Specify the event order and expiry: decide whether a gap must form on the break bar or later, and how long the setup remains eligible.
• Define conflicts: state what happens if the same candle reaches both a retest level and an invalidation level. OHLC bars may not establish the intrabar order.
• Define outputs: include event name, symbol, timeframe, reference price and confirmation time in any custom alert requirement.
• Review the generated source, compile it, and compare its behavior against the worksheet before relying on its alerts. Syntax validation does not verify trading logic.