How to Read Market Structure: HH, HL, LH and LL
Learn how connected swing highs and lows describe trend, transition and invalidation—and why confirmation matters more than prediction.
A practical framework for reading swing structure without treating a single label as a trade signal. This article explains the reasoning framework used by Trading.Red and the limitations a reader should keep in view.
Start with the sequence, not one point
Market structure is a way of describing how price moves from one meaningful swing to the next. A higher high (HH) exceeds the previous confirmed swing high. A higher low (HL) holds above the previous confirmed swing low. Lower highs (LH) and lower lows (LL) describe the opposite sequence. One label alone is weak evidence; the connected sequence is what gives the label context.
A rising sequence usually contains HH and HL points, while a falling sequence usually contains LH and LL points. Real charts are untidy. A temporary lower low can appear inside a broader rising structure, and a short rally can form inside a longer decline. That is why Trading.Red calculates each horizon independently instead of copying one score across every timeframe.
Confirmed swings versus developing swings
A swing is confirmed only after candles on both sides show that price actually turned. The most recent candle cannot confirm itself because future bars do not exist yet. Any label close to the live edge of a chart should therefore be treated as developing until enough later data arrives.
This distinction prevents look-ahead bias. A chart that marks every local move immediately may look impressively accurate in hindsight but would have produced many changing labels in real time. Trading.Red separates observed structure from a watch level so the interface can say what has happened and what would need to happen next.
Continuation and protection levels
In a bullish sequence, the continuation area is normally associated with the prior confirmed swing high. A decisive close beyond that area can support continuation, but it is not proof that price must keep rising. The structure-protection area is associated with the latest meaningful higher low. Losing it weakens or invalidates the current sequence.
For bearish structure, the logic is mirrored: continuation is evaluated near the prior confirmed low, while the relevant lower high acts as structure protection. These are analytical reference areas, not executable broker orders, guarantees or personalized recommendations.
A three-step reading routine
First, identify the active sequence and its timeframe. Second, locate the next confirmation area and the point that would invalidate the interpretation. Third, check whether volume, volatility and the broader market agree with the structure. If those layers conflict, the honest conclusion is uncertainty—not a forced bullish or bearish call.
The scanner ranks proximity and setup quality, not certainty. A candidate can be close to a structural event and still fail. Gaps, earnings, thin liquidity and market-wide shocks can move price through a level before any planned response is possible.
Common mistakes
Do not connect every candle wick as a swing. Do not compare a daily swing with an intraday label as if they belong to the same sequence. Do not move the invalidation point after the structure has failed merely to preserve the original view. And do not interpret a high model score as a historical win rate unless the screen explicitly labels it as a calibrated probability.
Worked example: confirmation versus anticipation
- A prior HH and HL are already confirmed.
- Price approaches the old high but the current candle remains open.
- The next completed bars determine whether a new HH exists.
Reading: The chart may show a continuation watch level, but it should not label a new HH until later candles confirm the turn. This avoids hindsight being presented as live knowledge.
Key takeaway
A technical label is a compressed description of market data, not knowledge of the future. Use the label to organize questions: which timeframe produced it, what confirmed it, which observation would invalidate it, and what data might be missing?