How to Build a TradingView Stock Scanner: Filters, Watchlists & Alerts

A good stock scanner does one job: reduce a large market into a smaller list of names worth reviewing. It does not replace chart analysis, and it does not turn a set of indicators into a guaranteed signal.

TradingView is useful for screening because it combines market filters, watchlists, charts and alerts in one environment. The best way to use it is to build the scanner around the actual conditions your strategy needs rather than stacking every filter that looks useful.

1. Start with the market universe

Before adding indicators, define what you are willing to trade. A scanner that searches every listed security usually produces too much noise.

Useful universe filters can include:

• exchange or country;
• sector or industry;
• market capitalization;
• price range;
• average daily volume; and
• specific watchlists.

For example, a trader focused on liquid U.S. equities might begin with NYSE and Nasdaq names above a minimum price and minimum average volume. A swing trader may prefer a broader universe, while an options trader may additionally care about whether the underlying has an active options chain.

2. Add liquidity before technical conditions

Liquidity is one of the most important scanner filters because an attractive chart can still be difficult to trade if spreads are wide or volume is inconsistent.

Common liquidity filters include:

• minimum daily volume;
• minimum average volume over a lookback period;
• minimum dollar volume;
• minimum price; and
• market-cap constraints where appropriate.

A simple starting point for many large- and mid-cap equity strategies is to require meaningful average daily volume before applying any momentum or trend filter. The exact threshold should depend on the position size and instrument you trade.

3. Decide whether you are scanning for trend, momentum or reversal

The technical filters should match a specific setup type. Mixing trend-following and mean-reversion conditions in the same scan can create contradictory output.

Trend scanner

A trend-oriented scanner might look for:

• price above a medium-term moving average;
• a faster moving average above a slower one;
• positive relative strength or momentum; and
• volume consistent with normal participation.

Momentum scanner

A momentum scanner may emphasize:

• strong percentage change;
• relative volume;
• price near recent highs;
• RSI or another momentum measure above a threshold; and
• breakout conditions.

Mean-reversion scanner

A mean-reversion scanner may instead look for:

• large deviation from a moving average;
• short-term oversold or overbought readings;
• unusually large intraday moves; and
• evidence that price is returning toward a reference point.

The scanner should reflect one hypothesis at a time.

4. Use volume as confirmation, not decoration

Volume can help distinguish a meaningful move from one happening in a thin market. Depending on the strategy, useful filters include:

• current volume versus average volume;
• relative volume;
• unusual volume expansion; and
• minimum dollar volume.

A breakout on above-average participation may deserve more attention than the same percentage move on weak volume. That does not make the breakout valid by itself, but it gives the move more context.

5. Use VWAP correctly

VWAP can be useful as an intraday reference, especially for day-trading scans. It tells you where price is trading relative to the session's volume-weighted average.

What it does not tell you is whether institutions are definitely buying or selling.

A scanner can still use VWAP conditions effectively. Examples include:

• price above VWAP;
• price crossing above VWAP;
• price below VWAP after an extended move;
• distance from VWAP; and
• VWAP combined with a volume condition.

The output should then be checked on the chart to see whether price is actually accepting above or below that reference.

6. Build a simple TradingView momentum scanner

Here is a practical example designed to narrow the market to liquid names showing trend and momentum.

This is intentionally simple. The goal is not to make the scanner “smart.” The goal is to return a manageable set of candidates that can be reviewed quickly.

7. Do not over-filter

One of the most common scanner mistakes is continuing to add conditions until almost nothing qualifies.

For example, requiring all of the following at once—high relative volume, RSI above 70, price above VWAP, multiple moving-average alignment, a MACD crossover, a new high and a specific sector—may produce very few candidates and can encourage overfitting.

A better approach is:

1. identify the minimum conditions required by the strategy;
2. scan for those conditions;
3. review the resulting charts;
4. record what actually worked; and
5. only add another filter if the data shows that it improves the process.

8. Use watchlists to organize scanner output

Scanner results become more useful when they are separated into purpose-built watchlists.

Examples:

• high-relative-volume names;
• large-cap momentum;
• swing candidates;
• earnings names;
• options-active equities; and
• sector-specific lists.

This reduces the amount of scanning you have to repeat during the trading session and makes alerts easier to manage.

9. Add alerts only after the scan is useful

Alerts are most effective when the scanner has already narrowed the market. Otherwise, automation simply creates more noise.

A useful alert might monitor a watchlist for a condition such as:

• price crossing a defined level;
• price reclaiming VWAP;
• relative volume exceeding a threshold;
• a moving-average condition; or
• another strategy-specific trigger.

TradingView alerts can help you avoid staring at every chart continuously. They should notify you that a condition occurred, not replace the decision process.

10. Where Pine Script fits

Pine Script is useful when the condition you want cannot be expressed cleanly through built-in screeners or when you want to test a rule historically.

That may include:

• custom indicator logic;
• multi-condition alerts;
• strategy backtesting;
• time-of-day filters; and
• custom risk or trade-management rules.

The important distinction is that a Pine Script strategy and a stock screener solve different problems. A screener finds candidates. A strategy defines what to do with them.

11. Adding options and gamma data after the scan

For options traders, scanner output can become the starting universe for a second layer of research.

Options-positioning data can help answer questions such as:

• Is there meaningful open interest around nearby strikes?
• What does the estimated gamma backdrop look like?
• Are there expirations or strikes that deserve closer attention?
• Does the options market support or conflict with the underlying thesis?

This information should be treated as context rather than as a substitute for the scanner or chart setup.

Rawstocks uses GammaEdge as one source of options-market structure data. If you are evaluating the platform, our updated GammaEdge review explains the current features, swing-trading use cases and limitations.

Affiliate disclosure: Rawstocks may earn a commission if you purchase GammaEdge through our links. That does not change the price you pay or our assessment of the platform.

12. Validate scanner ideas before trusting them

A scanner can look logical and still produce poor trades. The final step is validation.

Track:

• how many candidates the scan produces;
• how often the intended setup actually appears;
• win rate and average win/loss if you trade it systematically;
• maximum adverse excursion;
• performance by market regime; and
• whether an added filter actually improves expectancy.

If you are turning scanner output into a defined trade process, our Expectancy Calculator and Position Size Calculator are useful for evaluating the risk side of the system.

Common scanner mistakes

• Using too many filters: a scanner should reduce noise, not eliminate every imperfect setup.
• Treating RSI or MACD as trade signals by themselves: indicators describe conditions; they do not define complete trades.
• Ignoring liquidity: a strong-looking setup can still be difficult to execute.
• Assuming VWAP reveals institutional intent: it is a volume-weighted reference, not an identity detector.
• Changing the scanner after a handful of misses: evaluate a meaningful sample first.
• Automating before validating: alerts amplify whatever logic you give them, good or bad.

Final takeaway

A professional stock scanner is not professional because it uses the most indicators. It is professional because it is built around a specific process.

Define the market universe, remove illiquid names, apply only the filters your setup actually needs, organize the results, add alerts where useful, and validate the output over time.

TradingView is effective because it allows those pieces to live in the same workflow. The edge, if one exists, comes from the rules you test and follow—not from the fact that the scanner found a ticker.