Rejection Block in SMC Trading Explained
A candle with a massive wick tells you something. Price tried to go somewhere and got violently rejected. That wick is not noise. It's institutional aggression. And the zone it creates is called a rejection block.
In this guide:
- What a rejection block is
- How it differs from an order block
- How to identify valid rejection blocks
- How to trade them
What is a Rejection Block?
A rejection block is the wick portion of a candle that shows aggressive institutional rejection from a price level. The wick represents where price was pushed away rapidly.
Bullish Rejection Block: A candle with a long LOWER wick (price dropped down but got aggressively bought back up). The lower wick zone = support.
Bearish Rejection Block: A candle with a long UPPER wick (price pushed up but got aggressively sold back down). The upper wick zone = resistance.
The Logic:
When a wick is disproportionately long compared to the body, it means one side (buyers or sellers) overwhelmed the other within that single candle. That zone of rejection often holds when retested.
Rejection Block vs Order Block
- The entire candle body is the zone
- Based on the last opposite candle before a strong move
- Represents where orders were PLACED
Rejection Block:
- Only the wick portion is the zone
- Based on aggressive rejection within a single candle
- Represents where price was REJECTED
Order blocks are about accumulation (orders placed). Rejection blocks are about aggression (orders pushed price away from a level fast).
How to Identify Valid Rejection Blocks
Rule 1: The wick must be disproportionate
The wick should be at least 2x the size of the candle body. If the body is 10 pips and the wick is 5 pips, that's not a rejection block. If the body is 10 pips and the wick is 25 pips, that's strong rejection.
Rule 2: Must occur at a significant level
Rejection blocks are strongest when they form at:
- Liquidity pools (after a sweep)
- Key premium/discount arrays (at an OB or FVG)
- Previous day/week high or low
- Session high or low
A random wick in the middle of nowhere is less reliable.
Rule 3: Align with structure
A bullish rejection block (long lower wick) should form in a bullish structural context. A bearish rejection block should form in bearish context.
Rule 4: Higher timeframe carries more weight
A rejection block on the daily chart is far more significant than one on M5. H1 and above are most reliable.
How to Trade Rejection Blocks
Step 1: Identify the rejection candle
Find a candle with a wick at least 2x the body size at a significant level.
Step 2: Mark the wick zone
For a bullish rejection block: Mark from the candle body low to the wick tip (the lower wick zone).
For a bearish rejection block: Mark from the candle body high to the wick tip (the upper wick zone).
Step 3: Wait for price to return
When price retraces back into the wick zone, that's your potential entry.
Step 4: Enter at the midpoint
Use the consequent encroachment (50% of the wick) as your entry level.
- Stop loss: Beyond the wick tip
- Target: Next liquidity pool or structure level
When to Use Rejection Blocks
Best Use Case: Entry refinement on lower timeframes
Your higher timeframe shows a bullish OB. Price enters the OB zone. On the lower timeframe, you see a rejection block (long lower wick) form inside the OB. That rejection block gives you a precise entry within the broader zone.
This is how you get tight stops within larger zones. The OB gives you the area. The rejection block gives you the exact level.
Second Use Case: After liquidity sweeps
After price sweeps liquidity, it often forms a rejection block candle (wick into the liquidity then snaps back). That rejection block marks the reversal point. Enter on the retest of the wick zone.
Conclusion
Rejection blocks are simpler than they sound. Long wick = aggressive rejection. Mark the wick zone. When price comes back to it, enter at the 50%. Stop beyond the tip.
They work best as refinement tools within larger setups (inside OBs, at liquidity levels, at premium/discount arrays). Use them to sharpen your entries, not as standalone signals.