Technical indicators transform price, volume or related data into measurements that can become explicit trading conditions. A useful rule names the input, calculation, comparison and evaluation time. Trend, momentum, volatility and volume indicators answer different questions; none is a complete strategy or universally best. The same indicator can produce different alerts when checked intrabar instead of at bar close.[1]
Choose the indicator guide for the condition you need
Scroll horizontally to read every column.
| Guide | Question to specify |
|---|---|
| Moving-average crossover rules | Which averages, which price source and what exactly counts as a cross? |
| RSI rules | Is the condition a level, a crossing event or a defined divergence? |
| Bollinger Bands rules | Is the rule measuring position within the bands, band width or a break? |
| VWAP rules | Which volume source and reset anchor define the average? |
| Stochastic oscillator rules | Which oscillator settings and comparison are evaluated? |
| ADX rules | How is the ADX condition defined within the wider rule specification? |
| MACD crossover workflow | Which MACD event produces the intended alert? |
| Supertrend direction values (v5 guide) | What do the selected script version's direction values mean? |
| ATR and rule definitions | How is the volatility measurement used in the rule? |
Start with the measurement your rule needs, then open its guide. The library is organised by the work each indicator does, not by a ranking of expected trading performance.
What do the four indicator families measure?
| Family and measurement | Possible measurable conditions | Timing and repainting checks |
|---|---|---|
| Trend: smoothed price level or relationship between averages | Price above an average; faster average crossing a slower one; slope over a fixed lookback | Current-bar prices can move the average and undo a cross; a higher-timeframe average may remain unfinished |
| Momentum / oscillators: changes in price strength, such as RSI, or relationships such as MACD | Value above a chosen level; crossing a level or signal line; explicitly confirmed divergence | Intrabar readings change; a pivot-based divergence may become knowable only after later bars |
| Volatility: dispersion or movement magnitude, such as band width or ATR | Width greater than its earlier value; a stated price distance based on a volatility input | Current high, low and close can change the measurement; completed-bar values arrive later than an intrabar estimate |
| Volume / volume-weighted price: activity or price weighted by the selected feed's volume | Volume above a defined baseline; close crossing a specifically anchored VWAP | Volume accumulates within the bar; feed meaning, anchor resets and incomplete higher-timeframe values matter |
The table lists specification examples, not entry recommendations. Indicator categories overlap: MACD compares moving averages but is commonly classed as momentum; VWAP is volume-weighted yet also used as a price reference.[2][3][4][5]
How do trend measurements become exact rules?
A moving average smooths its selected input. A simple moving average gives equal weight to the observations in its window; exponential and linearly weighted averages give more weight to recent observations. Different weighting and lookback choices produce different measurements.[2]
SMA = sum of the selected N prices / N
Illustrative, not a recommendation. Three completed closes of 100, 102 and 104 price units have an SMA of (100 + 102 + 104)/3 = 102. If the next close is 106, the rolling three-close SMA becomes (102 + 104 + 106)/3 = 104.
A short average crossing a long average is a change in their relationship, not proof of a new trend. The familiar example comparing 50-day and 200-day averages still needs the average type, price source, feed and daily-bar definition. Those periods are an example to specify, not settings recommended here.
Cross above: A now > B now AND A previously ≤ B previously
Above: A now > B now
With A/B at 99/100 on the previous observation and 101/100 now, both definitions are true. If the next observation is 102/100, “above” remains true but no new crossing occurred. Decide whether a sustained state permits one request, repeated requests or a wait for reset.
Record the same distinction for the moving-average crossover and MACD crossover workflows. MACD's line is the difference between its selected fast and slow averages; the histogram is MACD minus its signal line.[5]
How should RSI, divergence and oscillator conditions be written?
J. Welles Wilder Jr.'s RSI compares smoothed positive and negative price changes on a scale from 0 to 100. TradingView's RSI explanation describes the familiar 70 and 30 reference levels, but one reading does not establish a price reversal.[3] “Above 70” and “crosses back below 70” are different rules.
Specify the source, lookback, comparison, equality case and evaluation time in the RSI rule definition. For a Stochastic condition, also record the exact oscillator configuration. TradingView's execution-model example demonstrates that its Stochastic value changes as the current bar's close, high and low change.[6]
Divergence needs a selection rule. “Price makes a lower low while RSI makes a higher low” leaves open which lows to compare and when they are confirmed. Write the pivot or lookback definition, alignment, minimum separation and confirmation time before treating the pattern as machine-readable.
A mark drawn beneath an earlier bar may use information from later bars. Waiting for today's chart bar to close does not make such a mark available at the earlier time. Review pivot confirmation and backdated plots alongside any divergence rule.[1]
What do volatility bands and volume add?
John Bollinger describes Bollinger Bands as a relative definition of high and low. He explicitly cautions that touching a band is not, on its own, a buy or sell signal. Price can continue along a band during a trend.[7]
A band rule must therefore state whether it measures an outside close, a return inside, or a change in width. Width measures dispersion; it does not determine the direction of the next move. ATR provides another movement measure used in rule definitions, including an ATR-based stop level in a TradingView strategies FAQ example.[8]
VWAP weights the selected price input by volume from a stated anchor. TradingView's built-in indicator allows different reset periods; a session reset and a weekly reset produce different averages.[4]
VWAP = sum(priceᵢ × volumeᵢ) / sum(volumeᵢ), from the chosen anchor
Illustratively, selected prices of 100 and 104 with volume weights of 3 and 1 give VWAP = (100 × 3 + 104 × 1)/(3 + 1) = 101. Name the price source and what “volume” represents. MetaQuotes distinguishes Forex tick volume, counted as price changes, from actual traded volume on stock symbols.[9]
Do not assume a Forex or CFD feed describes market-wide traded volume. Record its supplied series and missing-data behaviour before using the VWAP condition. Intrabar volume and a developing VWAP are not their final bar-close values.
Where do Fibonacci retracements fit?
Fibonacci retracements are a way to define reference levels from a selected price swing. The CFTC glossary describes the use of Fibonacci ratios in percentage retracements.[10] The chosen endpoints remain part of the rule: different swings create different levels.
Preserve the intended support-or-resistance hypothesis as a testable comparison, not as a fact about where price must turn. Specify the anchors, ratio, inclusive boundary and reaction condition. A touch, a close beyond the level and a return across it are three different events. See Fibonacci drawing alerts and moved anchors.
How do you turn an indicator into a complete condition?
- Name the data. Save provider, symbol, chart type, timeframe, timezone and selected price or volume source.
- Freeze the calculation. Record indicator version, inputs, smoothing, lookback and any reset anchor.
- Write the event or state. Define the comparison, equality case and previous observation used by a crossing.
- Name the evaluation time. Choose the intended intrabar or completed-bar observation, including confirmation for every higher-timeframe input.
- Define repetition and conflicts. State what happens if a condition stays true, repeats or conflicts with another condition.
- Record expected cases. Include a pass, fail, equality boundary, temporary intrabar cross and delayed confirmation before implementation.
Use the measurable-condition worksheet, then the complete rule specification to add size, exits, sessions and exceptions. A precise indicator condition can still be a poor trading rule.
What changes when the condition becomes an alert?
As of 25 September 2026, TradingView documents realtime alert operation and a saved copy of the script, inputs and chart context when an alert is created. Later chart edits do not rewrite that running copy.[11] Replace affected alerts when their intended configuration changes and remove unintended duplicates.
For PineConnector, follow the documented converter path for supported scripts, or the documented manual integration. A detected indicator condition is different from a strategy's simulated fill.[12] Before creating an executable test alert, verify that every account sharing the chosen License ID is a demo account.
Choose your own symbol, size and rules. Verify the alert, PineConnector processing, EA request, broker acceptance, deal and resulting position separately. A script marker is not proof of delivery; a stop activating is not proof of a completed close. Keep broker reconciliation separate from indicator research.
What are the common mistakes?
- Counting related indicators as independent confirmation. Two transformations of the same price series can repeat the same information. Bollinger explicitly cautions against combining directly related indicators as though each adds a separate dimension.[7]
- Treating bar close as a cure for every repainting issue. Higher-timeframe inputs, delayed pivots and historical execution settings need their own checks.[1]
- Optimising the description after seeing results. Record the original rule and evaluate changes separately through the backtesting workflow.
- Stopping at the signal. Indicators do not specify risk, position ownership, exits or the handling of uncertain broker outcomes.
Frequently asked questions
What is the best technical indicator for trading?
No technical indicator is universally best. Choose a measurement that matches a defined question, such as price trend, momentum, dispersion or volume-weighted price. Then specify timing, costs and the full trading rule, and test the claim. An indicator's popularity does not establish positive expectancy.
Can technical indicators be used for automated trading?
Technical indicators can supply inputs to explicit alert or strategy conditions. Automation also requires defined entries, exits, sizing, sessions and exception handling. In a TradingView-to-MetaTrader workflow, verify the alert and broker result separately; the indicator's plotted signal does not establish that a trade occurred.
Do technical indicators repaint after bar close?
Some indicator values can change after the chart bar closes because their inputs include unfinished higher-timeframe data, delayed confirmation or revised history. Ordinary intrabar changes also differ from backdated plots or future-information leakage. Check the specific script and every input's availability instead of relying on a general label.
Should I combine several technical indicators?
Several indicators can describe different aspects of the same data, but more indicators do not automatically provide independent evidence. Define the job of each input and test whether removing it changes the rule's behaviour in a useful, repeatable way. Closely related calculations can produce redundant confirmations.
Reviewed 25 September 2026. Facts were checked against the linked sources on that date. Nothing in this article was tested on a trading account and no code was compiled.
Related reading
- Pine Script library
- Backtesting library
- Trading metrics library
- From discretionary to automated trading
Sources
- TradingView – Repainting, accessed 25 September 2026.
- MetaQuotes – Moving Average, accessed 25 September 2026.
- TradingView – Relative Strength Index, accessed 25 September 2026.
- TradingView – Volume Weighted Average Price, accessed 25 September 2026.
- TradingView – MACD indicator, accessed 25 September 2026.
- TradingView – Execution model, accessed 25 September 2026.
- John Bollinger – Bollinger Band Rules, accessed 25 September 2026.
- TradingView – Strategies FAQ: stop-loss example using ATR, accessed 25 September 2026.
- MetaQuotes – Volumes, accessed 25 September 2026.
- CFTC – Glossary: Fibonacci Numbers, accessed 25 September 2026.
- TradingView – Alerts, accessed 25 September 2026.
- PineConnector – Pine Script converter, accessed 25 September 2026.
PineConnector executes the instructions you send it. It does not select trades, manage money, or hold funds. Trading carries risk, and past performance of any strategy does not indicate future results.